S&P Global software engineer candidates report two to four technical and fit-focused rounds built around SQL, Java or another core language, OOP and data structures, plus detailed questions on their own projects.
$120K
Avg. Base Comp
$140K
Avg. Total Comp
2-5 rounds
Typical Rounds
30 days
Process Length
Candidates describe S&P Global software engineer interviews as fundamentals-heavy, with the exact loop varying by team and level. SQL, core-language knowledge, OOP and data structures appear in most reports, from campus-style hiring to experienced-hire loops.
Several candidates describe a campus-style path: an online assessment with aptitude and a coding question, a group discussion, two technical interviews, and an HR or managerial finish. Others report shorter loops of two to four rounds. One mentions a take-home assignment and another a live design task for a stock trading platform.
The technical questions are practical rather than exotic. Reported examples include Two Sum, reversing a linked list, finding a loop in a linked list, HashMap internals, SQL joins and subqueries, a hierarchy-style employer-employee query, and a median-salary-by-department query. OOP comes up often, including inheritance, overriding, SOLID and design patterns. One candidate said a take-home was judged as much on unit tests and SOLID design as on working code.
Project depth matters too. Several candidates were asked to explain what they built and why, and one was asked to open their GitHub profile. Stack-specific questions depend on the role, with Java multithreading, React state, Python output questions and C# concurrency all reported.
The last round is usually about fit and expectations. Timing is uneven. One senior candidate reported about a month from first interview to offer, including a two-week hold after two rounds. Another was told a role was on hold after being selected. Outcomes are mixed.
Synthesized from 22 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 S&P Global process.
As usual, there are 3 rounds of interviews, two technical and the last one HR or you can say a salary negotiation round. The interviewers are very clear in their requirements so they asked relevant questions about the job's profile. So overall interview was good, and salary negotiation was on my term. Onboarding was very smooth, HR is reachable and responsive over email.
2 technical rounds, 1 manager round with additional HR discussion. Had medium difficulty questions and tricky concepts being tested.
Questions asked: Given three relation database tables of employee, salary, and departments, ask to calculate median salary history for each department with SQL.
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 S&P Global
Find the names of all employees who joined before their manager
| Question | |
|---|---|
| Hurdles In Data Projects | |
| RAG Strict Source Control | |
| Concurrent LLM Serving | |
| DDoS Attack Response | |
| Blob Indexing | |
| Interpolating Missing Temperatures | |
| Testing Constraints | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| LRU Cache 1 | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| 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 |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report applying online (one via Workday, hearing back after over a month) or through an employee referral, then a recruiter or HR call that explains the process. Timing between steps appears uneven, and one experienced candidate was scheduled for a virtual technical interview the next day.
Several campus-style candidates report an online assessment before any interviews. It typically mixes aptitude or technical-fundamentals questions with one easy-to-moderate coding problem. Candidates describe it as a filtering step rather than a deep algorithm test. Not every experienced-hire report mentions this stage.
A few candidates report a group discussion, in one case with about ten students, on a non-technical topic such as whether dropping out of college is necessary for entrepreneurial success. It appears to assess communication and thinking on your feet. It shows up in campus-style accounts, so it may not apply to lateral hires.
Candidates typically report one or two technical rounds covering SQL joins and subqueries, OOP and SOLID, and data structures such as Two Sum or linked lists. Depending on the role, they also report Java multithreading, HashMap internals, React or Python topics. Some are asked to explain time complexity and walk through resume projects in detail.
Some candidates report an assignment beyond standard questions. One describes a 2-3 hour take-home console app judged on SOLID principles and unit tests. Another describes a live task designing a stock trading platform with OOP. These appear in individual reports, so treat them as possible rather than standard.
Final conversations with a manager, director, team lead or HR are commonly reported. They focus on fit, motivation, handling competing priorities and expectations for the role. One candidate reported a two-week hold after two rounds, and another was told a role was put on hold after being selected.
