Applied online. The recruiter quickly responded and set up a call where they described the position, and I gave my background. The next step was to do the coding challenge – create an in-memory DB. They recommended 30 minutes to 90 minutes for it, but I spent about 3 hours, just being thorough and making sure everything was correct.
A week later, a technical phone screen was scheduled. The interviewer asked me to describe a technical challenge I had faced and then asked me to code a solution to a question on a shared document. The question wasn't too difficult. After I coded the solution, they added a few requirements and asked me to code those up. As soon as I got it working, the interviewer basically said, "Great! Awesome!" and moved on. They never really asked follow-up questions or wanted me to discuss my implementation or ways to improve it or anything.
I got my rejection email the next day. I was a bit surprised since I felt my solution to the coding question was good, and the interviewer seemed fine with it. I didn't receive any feedback on why I was rejected either. I was also a bit frustrated because the initial coding challenge that I did was never brought up at all, so I felt like I had kind of wasted some time doing it. I will say that everyone (all the recruiters, coordinators, interviewers) was super nice, and they were efficient and timely in letting me know about their decision.
Create an in-memory DB.
The following metrics were computed from 67 interview experiences for the Thumbtack Software Engineer role in United States.
Thumbtack's interview process for their Software Engineer roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having good feelings for Thumbtack's Software Engineer interview process in United States.