Twilio · Primly Community

Did the Twilio loop for a senior infra role last month, here's the actual breakdown

infra_ines · 4 replies

Applied for a Senior Platform Engineer role. The process was five rounds total and took about 3.5 weeks from first screen to offer.

Round 1 (recruiter): 30 min, standard. She actually knew the team and what they worked on, which is rarer than it should be.

Round 2 (take-home): They sent a lightweight coding problem, something like building a webhook delivery system with retries. Open-ended, open internet, 48-hour window. I used Go and actually read their Webhooks docs to inform the design. That part felt deliberate, like they wanted to see if I'd bother.

Round 3 (technical deep dive): An hour with two engineers. Half my take-home walkthrough, half system design. We spent a lot of time on failure modes: what happens when the downstream is slow, how do you backpressure without losing messages. Real problems. I liked it.

Round 4 (behavioral): Two 45-min rounds back to back. STAR-method, but they pushed for specifics. One question was 'tell me about a time you made a call that turned out to be wrong, and what you did after.' Be ready to actually answer that.

Round 5 (hiring manager): More culture and team fit, also a chance to ask real questions about the roadmap.

Overall the process felt like they were evaluating someone who'd actually do the job. No fizzbuzz, no 'reverse a linked list' stuff. The take-home framing with their own product was the biggest signal about what they value.

4 replies

remote_swe_42

the take-home being open-internet and framed around their own product is interesting. did they grade it or just use it as a conversation starter? trying to figure out how much time to actually invest.

infra_ines

both. they read it before the call and came with specific questions, so they definitely graded it. but the conversation was where they figured out if you understood the tradeoffs you made or were just guessing. i'd invest real time, maybe 4-6 hours. a polished 70% solution with a clear README explaining what you'd add beats a frantic 100% with no context.

sre_sol

webhook delivery system with retries is such a good take-home. at-least-once delivery, idempotency keys, dead letter queues. if you've run kafka in prod this should feel familiar but you still have to make it legible to reviewers who don't know your background.

careerveteran

the 'tell me about a time you made a wrong call' behavioral is one of the better interview signals out there. candidates who can't give a crisp answer to that usually either haven't failed yet or can't reflect on it. both are problems.