Three candidates describe TSYS software engineering interviews with Java and OOP technical rounds, a manager or director conversation, and an HR round. The structure varies widely between reports.
$95K
Avg. Base Comp
$125K
Avg. Total Comp
3-5 rounds
Typical Rounds
Not reported
Process Length
Three candidates describe TSYS interviews for software roles, and each one reports a different mix of rounds. That makes the main preparation lesson flexibility: expect technical screening on core development skills, followed by a more conversational round with a manager or director, and an HR step.
One SDET candidate reports a technical round of about an hour and a half covering Java, Spring Boot, microservices and MySQL queries, plus multithreading and REST API design. The next conversation with the hiring manager and team focused on past projects and CV alignment. Another candidate, interviewing for an associate role, describes two technical rounds on OOP, design patterns and SOLID principles, then a director round and HR.
An internship candidate describes an online aptitude test that filtered out most of the group. Two technical rounds and an HR round followed, covering resume, Java, SQL and DSA. A manager round the next day drifted into DevOps, cloud and frontend questions. This is a single report, so treat it as a sign that breadth may help rather than as a rule.
To prepare, be able to explain each project on your resume in terms of the stack and the problems it solved. Review Java fundamentals, SQL, and object-oriented design. Confirm the job location and logistics with HR early. One candidate reports communication gaps, including rescheduling and silence after the final rounds, and another says their location question surfaced only after they had been told they were selected.
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 Tsys 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 Tsys
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Employee Salaries | |
| Rolling Bank Transactions | |
| Monthly Customer Report | |
| Comments Histogram | |
| Prime to N | |
| String Shift | |
| Find the First Non-Repeating Character in a String | |
| Top 3 Users | |
| Top 5 Turnover Risk | |
| Bagging vs Boosting | |
| Customer Orders | |
| Total Spent on Products | |
| Minimum Change | |
| Find the Missing Number | |
| P-value to a Layman | |
| Random SQL Sample | |
| Over 100 Dollars | |
| Scrambled Tickets | |
| Over-Budget Projects | |
| Flight Records | |
| Project Pairs | |
| Upsell Transactions | |
| Raining in Seattle | |
| Google Maps Improvement |
Synthesized from candidate reports. Individual experiences may vary.
One internship candidate reports an online aptitude test with mixed general questions that filtered most of the group, with about eighteen of seventy advancing. Other candidates do not mention this step, so it may apply mainly to campus or internship hiring.
Candidates report technical rounds on Java, Spring Boot, microservices, MySQL queries, multithreading and REST API design. Others describe OOP, design patterns, SOLID, SQL and DSA. One report puts the first technical round at about an hour and a half. Questions were described as fairly standard.
Candidates report a hiring manager or director round. One says it focused on past projects and CV alignment. Another describes it as a strategic conversation about experience and teamwork. The internship candidate says the manager round turned technical, with DevOps, cloud and frontend questions, so prepare for either style.
Candidates report an HR round covering basic background questions and logistics. One candidate was told they were selected and asked for documents, and then HR raised the Pune versus Mumbai location question. Another reports rescheduling and little follow-up. Confirm location and next steps early.
