Real, anonymous reports from people who interviewed for Software Engineer at ServiceTitan, newest first and distilled into what to expect across the loop.
After a recruiter call, I ended up doing a fairly straightforward sequence of coding rounds. The technical part leaned heavily on LeetCode-style data structures and algorithms—mostly medium problems—and each round felt calm and practical, with interviewers asking clarifying questions and staying focused on how I was thinking.
My interview started off with recruiter coordination and then turned into a set of deep technical conversations that felt genuinely hard. One path included multiple coding interviews plus a system design discussion, and the overall challenge level felt very difficult rather than just “standard practice.” People were pleasant and the culture impression was positive, but I ended up on the tail end of a hiring cycle, and that ultimately affected the result.
The interview process typically starts with a recruiter call, followed by multiple technical rounds, often taking about a month to complete, with some candidates experiencing delays in communication between stages.
Candidates can expect a series of coding interviews primarily focused on LeetCode-style problems, often emphasizing data structures and algorithms, with varying levels of difficulty and a strict time constraint.
Some candidates will participate in system design discussions, which may not always go as planned due to interviewer dynamics or lack of structure, impacting the overall experience.
While technical skills are heavily evaluated, there is also a behavioral component where candidates discuss their approach to work and fit within the company culture, though this may not always be emphasized.
Candidates report a mix of experiences regarding difficulty; some found the process challenging and felt evaluated on speed rather than problem-solving, leading to varied outcomes, including many not receiving offers.
Reflecting on their experiences, candidates often wish they had prepared more thoroughly for the specific tools and environments used during coding interviews, as technical issues with platforms like HackerRank were common.