Real, anonymous reports from people who interviewed for Software Engineer at ServiceTitan, newest first and distilled into what to expect across the loop.
Get your personalized ServiceTitan Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
After the recruiter call, about a week later I went through a set of timed technical interviews where the structure felt fairly standard. The whole thing centered on live coding, with multiple rounds that were meant to test how I worked through problems rather than just whether I knew a specific algorithm.
Once the technical interviews were done, I got pulled into a team-match style conversation with a hiring manager. Overall it felt like a normal process flow, just paced in a way that made the rounds feel compressed once you got going. I didn’t end up with an offer, but the experience was straightforward enough that I understood what stage I was in and what came next.
3 months ago
Average Neutral Vancouver, BC
My process started with an HR phone screen, and then I moved into three technical rounds. The coding rounds were pair-programming style and focused on implementing things with medium difficulty at most: one round was about building a custom data structure, and another focused on parallel processing and async/await. The next step was system design with a more architecture-heavy framing, and I expected the round to include behavioral questions based on how the agenda was set.
What threw me off was how disorganized the later parts felt. In the system design round, a manager was supposed to lead the session, lay out the plan, and run behavioral questions, but he disappeared halfway through the scheduled time—camera and mic off—while the other interviewer kept going. I ended up doing design work the whole time with no behavioral portion, and it left me feeling like the process wasn’t as structured or transparent as it should’ve been. Separately, I also ran into an awkward missing-interviewer situation where the agenda had been set that two people would join.
4 months ago
Difficult Negative United States
I started with an internal recruiter conversation, then I went straight into two leetcode-style pair coding rounds. The second coding round was notice…
6 months ago
Average Negative United States
I went into the technical interview expecting a live-coding collaboration, but the HackerRank environment became a real problem immediately. The tooli…
6 months ago
Average Negative United States
I didn’t really get a traditional interview experience at all. Instead, I received a HackerRank problem with a tight deadline and that was the extent …
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically begins with a recruiter call, followed by multiple technical rounds that include coding challenges and system design discussions. Candidates noted that while the structure was generally clear, there were instances of disorganization and long waits between stages.
Recruiter callTechnical roundsSystem design
Coding Challenges
Candidates faced a variety of coding challenges, often in a HackerRank format, with a focus on practical implementation in languages like C# and JavaScript. The challenges ranged from basic data structures to more complex concurrency problems, and many candidates felt the time constraints were a significant pressure point.
HackerRankData structuresConcurrency
System Design & Behavioral Rounds
After coding rounds, candidates typically engaged in system design discussions that sometimes included behavioral questions. However, some candidates reported that these rounds felt rushed or disorganized, impacting their overall experience.
System designBehavioral questionsInterview flow
Communication & Feedback
Several candidates experienced poor communication throughout the process, including missed interviews and lack of timely feedback. This led to frustration and a feeling of being undervalued, as many felt they were left in the dark about their application status.
Communication issuesFeedback delaysCandidate experience
Interview Environment & Dynamics
The interview atmosphere varied significantly, with some candidates experiencing friendly and supportive interactions, while others reported rudeness or a lack of engagement from interviewers. This inconsistency impacted candidates' perceptions of the company culture.
The overall difficulty of the interview process was perceived as high, with many candidates not receiving offers despite feeling they performed well in certain rounds. The disconnect between expectations and outcomes left many feeling dissatisfied with the experience.