What to expect interviewing for software engineering roles at TSG Risk Management: a HackerRank-style assessment, an HR screen, and technical rounds on OOP, SDLC and refactoring, based on three candidate reports.
$123K
Avg. Base Comp
$140K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates describing TSG Risk Management engineering interviews all mention an online coding assessment, so start there. The one report for the Software Engineer title describes a 90-minute HackerRank assessment with two problems and a git/DevOps question. The first problem was easy, the second was noticeably harder, and that candidate was rejected after the assessment.
Two other reports come from adjacent levels, so treat them as context rather than a forecast for this title. A software engineering intern reported a Leetcode-style assessment on strings and linked lists, a relaxed HR screen, and a live Java session. That session included a longer OOP design problem that tested inheritance, polymorphism, encapsulation and abstraction, and the candidate received an offer. A lead-level candidate described a recruiter call about background and salary expectations, then a HackerRank assessment on arrays and puzzles. Interviewers then asked about SDLC principles, testing, refactoring and OOP. That candidate declined the offer.
For preparation, practice timed easy-to-medium algorithm problems and be ready for a sharp difficulty jump. Review class hierarchies, method overriding and access modifiers, and prepare examples of testing and refactoring decisions. The intern felt the US HR team was somewhat disconnected from the engineering office, and the lead candidate found a follow-up call after the assessment impersonal, so confirm next steps with your recruiter.
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 TSG Risk Management process.
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 TSG Risk Management
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Employee Salaries | |
| Empty Neighborhoods | |
| Bagging vs Boosting | |
| Size of Joins | |
| P-value to a Layman | |
| Hurdles In Data Projects | |
| Type-ahead Search | |
| Three Zebras | |
| Precision and Recall | |
| Target Indices | |
| Transformer Encoder Layer | |
| Duplicate Rows | |
| RAG Strict Source Control | |
| Type I and II Errors | |
| Swap Variables | |
| Your Strengths and Weaknesses | |
| Client Solution Pushback | |
| Stakeholder Communication | |
| Google Earth Storage | |
| Branch Sales Pivot | |
| Scaling Up Recommender | |
| Designing a Fraud Detection System | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Merge Sorted Lists | |
| String Shift | |
| Rolling Bank Transactions |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an online application followed by a timed assessment. The Software Engineer candidate got a 90-minute HackerRank link with two problems, one easy and one harder, plus a git/DevOps question. That candidate did not advance. An intern reported a Leetcode-style assessment on strings and linked lists.
The intern and lead-level candidates both describe a recruiter or HR conversation. The intern called it relaxed, with standard behavioral questions. The lead candidate was asked about background, understanding of the role and company, salary expectations and availability. Timing may vary by level, so confirm the order of stages with the recruiter.
Candidates who got this far report conversational technical sessions. The intern did live Java coding, including a longer OOP design problem on implementing methods in a predefined class structure. The lead candidate discussed SDLC principles, testing practices, refactoring and OOP. These two reports cover different levels, so a Software Engineer loop may differ in depth.
