Envié una solicitud electrónica. El proceso duró 3 semanas. Acudí a una entrevista en ServiceTitan en oct 2025
Entrevista
As others have said, the process started off smoothly. Recruiter was responsive, process seemed very well thought out, almost too good to be true. Pre-screening was fine. The "live" programming interview seemed to go okay. Not a lot of feedback from the ServiceTitan person watching, but that was to be expected. Expected to hear back from the Recruiter but got nothing. Had to reach out to them and they finally responded. Gave me a lame excuse about not being fast enough for "required speed and problem-solving efficiency during the technical evaluation". Strange that finishing a coding exercise in the allotted time isn't fast enough. Even the "proctor" said he didn't finish the second/optional task.
The recruiter initially told me that they interview with the applied for position in mind, but that they consider you for roles above and below that. They claimed to have everything streamlined so that they don't waste your time or theirs. He also mentioned they were hiring for many levels and roles, so applicants were considered for different things at one time. When I asked after receiving the rejection email, with their lame excuse, I was ghosted.
So much for the following that they put in all their postings:
"Being human isn’t about checking every box on a list. It’s about the experiences we have, people we meet, and the perspectives we share. So, if you have the skills but are hesitant to apply because of your background, apply anyway. We need amazing people like you to help us challenge the conventional and think differently about the problems that we’re solving. We’re in this together. Come be human, with us."
Preguntas de entrevista [1]
Pregunta 1
"Live" coding was two exercises. The first heavily involved C# generics. The second was an extending the first problem with C# extension methods.
Envié una solicitud electrónica. Acudí a una entrevista en ServiceTitan en mar 2026
Entrevista
Initial with internal recruiter followed by 2 leetcode style coding pairs. The 2nd coding pair substantially more difficult than the 1st. Final interview for system design and pan-technical discussion.
While they give you 90 minutes for the antiquated leetcode tests, they don't tell you that they're filtering for completion within 60 minutes. This is horrendously dishonest as the following the instructions and engaging the interviewer (hence they're naming it a "coding *pair*") means that even though you complete the tasks correctly with all unit tests passing, if you utilize your time entirely in order to try and demonstrate your thought process and skills, you won't be selected. There does seem to be some potential bias at play as well.
Preguntas de entrevista [1]
Pregunta 1
First leetcode was to complete the implementation of an interface in C# for a custom dictionary.
Second leetcode was to implement a multithreaded http downloader that uses URL links to get page objects and recursively loop through each page and call all URL links in resultant pages.
Solicité el puesto a través de un captador. El proceso duró 2 semanas. Acudí a una entrevista en ServiceTitan
Entrevista
30 minute call with recruiter, 2 90 minute rounds of coding interviews, plus additional interviews, but was ghosted after 2nd coding exercise. My solution and tests could be improved, but worked and met the requirements. If the goal is getting perfect solutions instead of assessing a candidate's knowledge, skill, and composure, they are likely missing out on great engineers.
