Synopsys Interview Experience for R&D Senior Engineer 1
Interview Experience
Recently I had gone through four rounds of Synopsys Interviews for RD Senior Engineer 1Round 1: Output-based questions:C++ int j = 0;for(int i = n; i 1; i = i/...
Full Details
Recently I had gone through four rounds of Synopsys Interviews for R&D Senior Engineer 1
Round 1 Output-based questions: C++ int j = 0 ; for ( int i = n ; i > 1 ; i = i / 2 ) j ++ ; int add ( int & a , int & b ) { int c = a + b ;
return c ; } int main () { int int1 , int2 , sum ; sum = add ( int1 , int2 ); } C++ int a = 10 ; int & r = a ; int b = 25 ; r = b ; r ++ ; cout << r << endl << a << endl << b << endl ; void printArray ( int A []) { // write code here } int main () { int Arr [ 5 ] = { 2 , 4 , 6 , 8 , 10 }; printArray ( Arr );
return 0 ; } C++ void ChangeArray ( int A [], int n ) { for ( int i = 0 ; i < n ; i ++ ) A [ i ] ++ ; } int main () { int Arr [ 5 ] = { 2 , 4 , 6 , 8 , 10 }; ChangeArray ( Arr , 5 ); for ( int i = 0 ; i < 5 ; i ++ ) cout << Arr [ i ] << " " ;
return 0 ; } C++ void func ( int n ) { cout << n ; func ( n -1 ); } int main () { func ( 3 );
return 0 ; } int func ( int n ) { static int x = 0 ; if ( n <= 0 )
return 0 ; x ++ ;
return func ( n -1 ) + x ; } main () { func ( 5 ); } C++ void foo ( int n , int sum ) { if ( n == 0 )
return ; int k = n % 10 ; int j = n / 10 ; sum = sum + k ; foo ( j , sum ); cout << k << ", " ; } int main () { int a = 2048 , sum = 0 ; foo ( a , sum ); cout << sum << endl ; } C++ int j = 0 ; for ( int i = n ; i > 1 ; i = i / 2 ) j ++ ; int i = n ; 8 int j = 0 ; while ( i > 1 ) { j ++ ; i = i / 2 ; } C++ void printArray ( int A []) { // write code here int len = sizeof ( A ) / sizeof ( A [ 0 ]); for ( int i = 0 ; i < len ; i ++ ) { printf ( "%d " , A [ i ]); } } int main () { int Arr [ 5 ] = { 2 , 4 , 6 , 8 , 10 }; printArray ( Arr );
return 0 ; } C++ int func ( int n ) { static int x = 0 ; if ( n <= 0 )
return 0 ; x ++ ;
return func ( n -1 ) + x ; } main () { func ( 5 ); } C++ void foo ( int n , int sum ) { if ( n == 0 )
return ; int k = n % 10 ; int j = n / 10 ; sum = sum + k ; foo ( j , sum ); cout << k << ", " ; } int main () { int a = 2048 , sum = 0 ; foo ( a , sum ); cout << sum << endl ; } Build Binary search tree using preorder and inorder traversal Virtual function questions in C++
Round 2 Design Queue using stacks Next Greater element and previous smaller element Declare 2d array in C++ What each declaration means below const char* p; // pointer itself is constant char * const p; // value is consstant const char * const p; // both are constants Design your own vector class and difference between vector and array.
Round 3 Second largest element in a BST. Cycle in a directed and undirected graph Basic C++ questions related to virtual functions and constructors.
Round 4 Find the next number in the series 3, 5, 8, 13, 22 3 * 2 = 6 - 1 5 5 * 2 = 10 - 2 8 8 * 2 = 16 - 3 13 13 * 2 = 26- 4 22 22 * 2 = 44- 5 39 Convert string number to integer like atoi and ensure proper test cases are covered Why looking for a change and few other behavioral questions. All Practice Problems for Synopsys !
About This Question
This is a candidate experience report from a synopsys interview for a swe role (senior level) during the phone screen round reported in 2025.
It covers the following topics: Trees, Strings, Binary Tree, Binary Search, Graph, Stack Queue, Graphs, Queue, Arrays, Matrix .
Difficulty rating: Easy
More Synopsys Interview Questions
About Synopsys Interview Reports
This question was reported by a candidate who interviewed at Synopsys. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Synopsys are the higher-signal extractions to take from this report.
For broader preparation context, the Synopsys interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Synopsys reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Synopsys Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Synopsys reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.