Three candidates describe Société Générale software engineer interviews that mix Java and OOP fundamentals, coding, a managerial or leadership conversation, and an HR or culture-fit discussion. All three report receiving offers.
$98K
Avg. Base Comp
$112K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates who interviewed for Société Générale software engineer roles describe a process that tests fundamentals and communication about equally. All three report receiving offers, but their processes differed, so treat the details below as examples, not a fixed format.
Technical content centers on Java, object-oriented programming and core data structures. One candidate was asked to design a simple cache for a trading application, which led into concurrent collections, multithreading, Spring, microservices, SOLID, testing, and database indexing and normalization. Another faced a SQL question on finding the second largest value, array coding, polymorphism, DBMS basics, and garbage collection. A third reports easier coding tasks, such as finding vowels in a string and computing a square root in C++, plus inheritance, polymorphism, encapsulation, and a request to draw a use case diagram for a project.
The non-coding rounds matter. Candidates describe a communication-focused opening conversation, a managerial discussion of resume projects and decisions, an HR review, and in one case a final chat with senior leadership. Prepare to explain what you built, why you chose that design, and how you would describe technical ideas to non-technical colleagues. Two candidates mention an aptitude or online screening stage, so brush up on logical reasoning and medium-level coding too.
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 Société Générale process.
The interview process with Société Générale was demanding and fairly lengthy. I started with an initial conversation round focused on communication and cultural fit — essentially seeing if I could work effectively with the team and translate between technical and business contexts. It felt less like a grilling and more like a natural chat to assess whether we'd get along day-to-day.
The technical rounds came next, and they were substantial. I worked through coding problems, including a challenge to design a simple cache system for a trading application, which required me to think about concurrency and explain how concurrent collections would behave in that context. Beyond that, the interviewers dug into core data structures and algorithms, Java fundamentals, multithreading patterns, and Spring framework knowledge. There were also questions on microservices architecture and design patterns — SOLID principles came up, along with testing approaches and database design concepts like indexing and normalization.
The final round was a conversation with senior leadership, again focused on whether there was chemistry and whether they could see me contributing to their team long-term. Overall, the process tested technical depth across multiple areas while also heavily weighting communication and cultural alignment. I came away with an offer, though the bar was genuinely high across both technical and interpersonal dimensions.
Prep tip from this candidate
Brush up on concurrent collections and multithreading specifics — the cache system design question was a real differentiator, so understand how to implement thread-safe caching and explain trade-offs. Also prepare examples of how you've communicated complex technical ideas to non-technical stakeholders, since the 'getting to know you' rounds were explicitly evaluating that soft skill.
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 Société Générale
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Merge Sorted Lists | |
| Merge N Sorted Lists | |
| Your Strengths and Weaknesses | |
| Employee Salaries | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Maximum Profit | |
| Bagging vs Boosting | |
| String Shift | |
| Prime to N | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Size of Joins | |
| Total Spent on Products | |
| Google Maps Improvement | |
| Rectangle Overlap | |
| P-value to a Layman | |
| Cumulative Distribution | |
| Top 3 Users | |
| Over-Budget Projects | |
| Slacking Employees Salaries | |
| Hurdles In Data Projects |
Synthesized from candidate reports. Individual experiences may vary.
Two candidates report an early screening stage. One describes multiple-choice reasoning questions plus medium-difficulty coding, including a SQL question about the second largest value. The other describes logical reasoning multiple-choice questions. Not every candidate mentions this stage, so it may vary.
Candidates report coding problems alongside questions on Java, OOP concepts such as polymorphism, and DBMS fundamentals. Examples include array problems, string and math tasks, garbage collection, and, in one account, designing a simple cache for a trading application with discussion of concurrent collections, multithreading, Spring, microservices, and SOLID.
Candidates describe conversational rounds focused on communication, resume projects, decisions made, and scenario-style management questions. One candidate had this as an early chat about cultural fit and translating between technical and business contexts. Expect to explain your own work clearly and in depth.
Candidates report a closing discussion. One describes an HR round reviewing earlier responses, particularly from a psychotechnical assessment. Another describes a resume and motivation walkthrough that included drawing a use case diagram. A third describes a senior leadership chat about chemistry and long-term contribution.
