Retool · Primly Community

Retool senior / L5 system design interview, what to expect (my recent experience)

remote_swe_42 · 5 replies

Just finished my Retool onsite a few weeks ago for a senior backend role. Figured I'd write up the system design round because I couldn't find much detail when I was prepping.

First: Retool's system design is different from the typical "design Twitter" or "design a URL shortener" drill. The problems skew toward internal tooling, data pipelines, and multi-tenant SaaS infrastructure. Makes sense given the product.

My specific prompt was something like: design a system that lets enterprise customers embed Retool apps into their own portals, with isolated permissions per customer tenant. So basically multi-tenancy, auth propagation, and iframe security all at once.

What they actually cared about: Tenant isolation. How do you make sure customer A's data is never accessible to customer B's embedded app? They pushed hard on this. API gateway design and rate limiting per tenant. Not just "add a rate limiter" but how does pricing/quota enforcement translate to technical controls? Latency tradeoffs. They asked specifically: your caching layer is warm for 90% of tenants but cold for a new one signing up. What breaks, and how do you handle it? Real-time data: Retool heavily uses websockets for live data in components. They wanted to know I understood the statefulness implications at scale.

The interviewer was collaborative, not adversarial. He actually started sketching the architecture alongside me on the whiteboard tool (they use a shared canvas in Zoom). When I went down a path he thought was suboptimal, he'd ask clarifying questions rather than just correcting me.

I'm a mid-senior with 6 years backend, mostly fintech distributed systems. The level of depth expected felt appropriate for senior but not staff. They didn't really push me on the math (back-of-envelope estimates) as hard as FAANG would.

Total round was 50 minutes. First 5 was pleasantries and confirming the prompt, then design for about 35, then 10 for my questions. I asked about how they handle schema migrations across tenants in production. He lit up at that question, which I took as a good sign.

Happy to answer questions about the other rounds too.

5 replies

pivot_pat

The tenant isolation angle is very Retool-specific. When I interviewed there a while back (didn't take the offer, different reasons) the system design was also product-adjacent. Not a generic FAANG prompt. They want to see you've actually thought about their problem space.

Did they bring up their deployment models? Retool Cloud vs. Retool On-Premise is a real architectural concern for enterprise, and interviewers there sometimes probe how your design handles the on-prem variant.

qa_quinn

Yeah, actually. About 10 minutes in I mentioned that the multi-tenancy story looks different for a self-hosted deployment and he kind of nodded and said something like "good, keep that in mind as you go." It didn't become a deep sub-thread but they clearly wanted to know I was aware of it.

visa_vik

Really useful. Preparing for a Retool senior SWE loop right now and this is exactly the texture I needed. Websocket statefulness at scale is something I wouldn't have thought to specifically prep. Adding it to the list.

Did the round end with a hard stop at 50 or did they let it run over if things were going well?

hardware_hugo

Hard stop at 50. Interviewer actually apologized and said he had another block. So don't let your design run too long in the weeds, you want to leave room for their questions.

alex_design

The collaborative whiteboarding style you're describing is how I'd want my engineers to interview too. The adversarial style tests stress tolerance, not design ability. Glad to hear Retool is doing this the right way.

For anyone prepping: when an interviewer sketches alongside you, they're also evaluating whether you can incorporate feedback mid-design. Don't ignore what they add to the board.