Three candidates describe Synchrony software engineer interviews that mix Java and Spring Boot fundamentals, resume deep-dives, Python pair programming and HR conversations, with each reporting a no-offer outcome.
$113K
Avg. Base Comp
$140K
Avg. Total Comp
3 rounds
Typical Rounds
Not reported
Process Length
Candidates who describe Synchrony software engineer interviews report three rounds, though the content depends on the language of the role. The two Java accounts point to fundamentals and framework detail more than hard algorithms. One candidate described a single day with a director conversation, a Java coding round and a Spring Boot round, followed by HR. Another described an aptitude test, a Java technical interview and an HR round.
The coding was light: one candidate was asked to reverse a string without built-in functions. The harder part was recall. That candidate was asked about Spring Boot database configuration, including the hibernate.dialect property, while the other was expected to explain polymorphism, encapsulation and the collections framework, including lists and arrays. For a Java role, practice giving short, clear explanations of these ideas alongside coding.
The director conversation in one report drew heavily on the candidate's resume, including a technical challenge they had handled. Be ready to walk through a project and explain your own decisions.
A third candidate, interviewing for a Senior Python Developer role, described pair programming on two Python problems, including handling an API response, then an HR discussion of salary, role expectations and work location, then a technical round presenting a topic of their choice. That candidate heard positive feedback after each round but was rejected without reasons after about a week of silence.
All three reported no offer, so treat these as individual accounts.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Synchrony Financial process.
I interviewed at Synchrony Financial for a Software Engineer role, and the whole process happened in a single day with three rounds back-to-back. The first round was a conversation with the director of engineering, pretty straightforward—we talked about my background and experience, then he pivoted to technical questions based on things I'd mentioned on my resume. He asked me about a technical challenge I'd faced and wanted to understand how I'd handled it. The second round dug deeper into Java fundamentals. They gave me a coding problem to reverse a string without using built-in functions, which tested basic algorithmic thinking but nothing too complex. What surprised me was the third round's focus on Spring Boot specifics—they asked detailed questions about database configuration, including things like the hibernate.dialect property in application configuration. It felt less like testing core engineering skills and more like checking whether I'd memorized particular framework details. The HR round wrapped things up with fairly standard behavioral questions. Overall, the interviews weren't difficult in terms of conceptual depth, but they seemed to reward very specific technical knowledge rather than problem-solving ability. The process moved quickly—all three rounds finished the same day—but the emphasis on narrow, framework-specific trivia made it feel like there wasn't much room for demonstrating broader engineering thinking.
Prep tip from this candidate
Be ready for Spring Boot-specific questions around database configuration and Hibernate properties—they test those as discrete facts rather than conceptual understanding. Also prepare to explain technical challenges from your resume in detail, as the director's interview heavily pulls from that.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Synchrony Financial
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Merge Sorted Lists | |
| String Shift | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Total Spent on Products | |
| P-value to a Layman | |
| Maximum Profit | |
| Prime to N | |
| Cumulative Distribution | |
| Top 3 Users | |
| Over-Budget Projects | |
| Google Maps Improvement | |
| Hurdles In Data Projects | |
| Over 100 Dollars | |
| Minimum Change | |
| Find the Missing Number | |
| Scrambled Tickets | |
| Rectangle Overlap | |
| Project Pairs | |
| Sum to N |
Synthesized from candidate reports. Individual experiences may vary.
One Java candidate reports an aptitude test before any technical or HR conversation and advises treating it as a real gate. Another reports opening with a conversation with the director of engineering about their background, followed by technical questions drawn from their resume, including a technical challenge they had handled.
One Java candidate was asked to reverse a string without built-in functions. Another Java candidate had coding questions plus conceptual ones on polymorphism, encapsulation, and the collections framework, including lists and arrays. The Python candidate describes pair programming on two problems, including handling an API response, while explaining their approach aloud.
One Java candidate describes a Spring Boot round with detailed questions on database configuration, including the hibernate.dialect property, and felt it rewarded memorized framework details. The Python candidate's third round was a technical interview in which they presented a topic of their choice.
One Java candidate describes HR questions on self-introduction, strengths and weaknesses, and another describes fairly standard behavioral questions. The Python candidate describes an HR discussion of salary, role expectations and where they were willing to work, which they found basic and not deeply probing.
