Senior Software Developer applicants have rated the interview process at TEKsystems with 2.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 47% positive. To compare, the company-average is 56.6% positive. This is according to Glassdoor user ratings.
Candidates applying for Senior Software Developer roles take an average of 12 days to get hired, when considering 15 user submitted interviews for this role. To compare, the hiring process at TEKsystems overall takes an average of 18 days.
Common stages of the interview process at TEKsystems as a Senior Software Developer according to 15 Glassdoor interviews include:
Phone interview: 24%
One on one interview: 20%
Skills test: 12%
Presentation: 10%
Drug test: 10%
Other: 7%
IQ intelligence test: 5%
Background check: 5%
Group panel interview: 5%
Personality test: 2%
Here are the most commonly searched roles for interview reports -
I applied through other source. The process took 2 weeks. I interviewed at TEKsystems (Chennai) in Oct 2022
Interview
HR contacted me after getting the profile through Naukri. HR was very professional and explained about the projects and requirements by arranging a Google meet. Later, they scheduled a technical interview with the client, which was professionally handled by informing me in advance and scheduling it at a convenient time. The whole process was smooth. Unfortunately, I can't proceed further as I was looking for WFH.
Interview questions [1]
Question 1
Forms
Types of forms
Optional classes
Components of stream
Java 8 concepts
Functional interface
Collect and group by
Total 3 rounds
2 technical ( 1 internal and 1 client round)
1 managerial round
Client was HSBC
Thier round level was : medium to hard
They asked system design problems and 1 coding question
Interview questions [1]
Question 1
1st round
Basic node concepts
1 easy coding problm
And previous project discussion
Overall level was easy
2nd round : was by HSBC CLIENT
Interview conducted on KARAT platform
Where the interview can be of any country
Interview time : 1hr
They asked 5 system design problems scenarion based
And 5 minutes for each problem
Then one coding problem for 30 minutes
Problems like
How would calculate throughput
They already had code , we had to fix some bugs there in 30 minutes
I applied through a recruiter. The process took 2 weeks. I interviewed at TEKsystems
Interview
Terrible experience with the recruiters. They bait and switched a role at NVIDIA, requested a completed HackerRank assessment up front (with surprise frontend/React questions for a backend role), two references up front, tried to negotiate my requested hourly down after we'd already agreed on a number, and then ghosted me. Definitely won't be working with them again and will advise my network to avoid.
Interview questions [1]
Question 1
Hackerrank includes:
1. Longest increasing subsequence
2. Build a to do list in React (input box, button, list)
2. Minimum value to get positive step by step sum
I applied through other source. The process took 3 weeks. I interviewed at TEKsystems (San Francisco, CA) in Sep 2025
Interview
Applied via LinkedIn after being contacted by a recruiter. The process began with an online iOS skills assessment, which required a couple of days of preparation. Following that, I had an interview with a manager that focused mainly on manual testing skills, with little emphasis on programming.
When that role wasn’t a fit, I was interviewed again for a programming-focused position. During the conversation, I was asked about availability and mentioned I would need about five business days to start. I was told information would be sent to the client, but I did not receive further communication after that.
Advice for Candidates:
Be prepared for both technical and non-technical interview tracks (e.g., manual testing vs. programming).
Expect the process to involve online assessments as an initial step.
Clarify next steps and follow-up timelines during interviews, as communication may vary.
Interview questions [1]
Question 1
General manual testing / Quality Engineering scenarios and best practices
Required detailed, test-plan-level answers (not just high-level concepts) — expected to cover 5–10 key essentials, edge cases, and potential gotchas
Questions about availability for interviews and potential start date