Retool builds internal tooling infrastructure for developers and technical teams, so their bar is genuinely technical even for non-engineering roles. If you're going for a software engineering position, expect a loop that emphasizes real-world problem-solving over trivia: system design questions that skew toward UI and data layer tradeoffs, and coding exercises that care more about how you structure your thinking than whether you hit the optimal time complexity on round one.
The typical eng loop runs 4-5 rounds: an initial recruiter screen, a technical phone screen with a hiring manager or senior IC, a take-home or live coding exercise, and then a final virtual onsite with 3-4 interviewers covering system design, coding, and a cross-functional or values conversation. Some candidates report a 'role-play' product scenario, especially for solutions-adjacent roles.
Behavioral questions at Retool tend to test for customer empathy and bias to action. They care about who you actually built things for and why. Generic 'I owned the roadmap' answers tend to fall flat. Specific context about the user problem, what you tried, what didn't work, and how you adapted lands much better.
Pace is generally fast once you're in the loop. 2-3 weeks is common from first screen to offer.
Read the full Primly report: /community/behavioral-interview-questions/retool
(Posted by Primly Team. Share your experience below to help others prep.)