Thumbtack Software Engineer Interview Guide

Two Software Engineer candidates describe a similar opening: a recruiter conversation, then a one-hour technical screen. Both were interviewed by people they called respectful and supportive, and both were ultimately rejected.

The two screens tested different things. One candidate got a strings and n-gram problem and solved it with an optimized approach. Even so, the feedback was about language fluency: they were told to show stronger Kotlin proficiency and to use higher-order functions more effectively. That candidate also coded without an editor, which made idiomatic style harder. If you pick a language for the screen, practice writing it in a plain text environment and use its conventional constructs.

The other candidate described a single main problem that was not a standard LeetCode question but had the same algorithmic feel. It was built in parts. Finishing part one led to part two, and part three seemed to be something you could explain verbally. For that candidate, the later parts appeared to be more about walking through an approach than coding it out.

That same candidate described the onsite as a roughly six-hour day with system design, a behavioral conversation with a potential manager, and several more coding rounds. They described it secondhand rather than as a round they completed, so treat the format as indicative. Prepare data structures and algorithms first, then a system design walkthrough and a few concise stories about your past projects.