Deployed Engineer Interview Experience
I had some serious issues in my demo, and 10 minutes later the COO called and basically said, “Yeah, that demo did not go well, but we think you can do the job, so why don’t you try again next week?”
Interview process
The process was basically a short intro chat, then a LangSmith demo take-home, then a much heavier LangGraph build-and-present round. The first demo felt practical and customer-facing, while the second one was way more about whether I actually understood the technical intricacies of LangGraph. I ended up getting the offer, and the whole thing left me feeling like they were very accommodating and reasonable, even though the ramp on their tools was genuinely brutal.
- Recruiter screen
- Take-home project
- Final round
Interview tips
I would tell a friend not to overcomplicate the take-homes. Pick a realistic, boring use case and spend your energy showing why LangSmith or LangGraph matters. Start with LangChain Academy and chat.langchain.com instead of generic ChatGPT, because the learning curve is real and the docs can be hard to navigate. They had also set up a Slack channel with all the interviewers, and I honestly did not use it enough at first. I underestimated how confused I was going to be and tried to muscle through it myself, which was a bad idea. In hindsight, that channel was absolutely part of the evaluation because this job is so collaborative and customer-facing. I would still think deeply first, but if you're stuck after real effort, ask. That is closer to how the actual job works. Also, if the demo breaks, stay calm and talk through your thinking. They care a lot about how you reason when the tooling gets messy.
Company culture
My read is that they're hiring deployed engineers aggressively right now and still figuring out what leveling really means. The process felt very startup-y in a good way: no recruiter layer, direct contact with someone on the exec team, loose timelines, no weird pressure tactics, and fast feedback. They seem to care a lot about practical signal over interview theater, which is why both take-homes were basically miniature versions of the actual job. At the same time, their products have a steep learning curve, and I think they know that, which is why they give candidates resources like a shared Slack channel. It also felt like they value collaboration and coachability a lot, not just raw technical skill.
Questions asked
Overview
The last round was another take-home, but this one was much more code-heavy and technical. I had to build a customer support agent with LangGraph and present it to two engineers plus the COO.
Question types asked
Specific questions asked
What features did you choose to implement and why?
How realistic did they want the demo to feel?
I kept it pretty straightforward and used the obvious paths in the data: customer orders, refund-style workflows, music lookup, and simple recommendations. I did very little domain research because the dataset naturally constrained the use cases anyway. Just like the first round, I tried to make it feel realistic instead of overengineered. The goal was to show something a real customer service agent might actually need, not impress them with complexity for its own sake.
Why did you build the agent architecture that way?
What other option were you considering?
This was the toughest part of the loop. I struggled hard with LangGraph, made some architectural choices they pushed on, and also had bugs in the live demo. I explained my reasoning clearly, admitted I had been weighing two options, and was receptive when they said they would have structured it differently.
Get full access with a membership, or share your experience to try it free.
