Forward Deployed Engineer applicants have rated the interview process at Stuut with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 67% positive. To compare, the company-average is 42.9% positive. This is according to Glassdoor user ratings.
Common stages of the interview process at Stuut as a Forward Deployed Engineer according to 3 Glassdoor interviews include:
Only had initial call and then was dropped from interview process. Spoke with a recruiter after resume drop. It was a fifteen minute behavioral call with typical questions for this sort of role. Nothing out of ordinary.
I applied online. I interviewed at Stuut (New York, NY) in Jul 2026
Interview
I only made it two rounds. First round was 15 minutes and just typical screener questions(see questions asked). Second round was a 45 minute technical conversation that to my surprise was actually a conversation. They just wanted to hear what I had built and how.
The only thing that was disappointing is that I got no feedback after the second round, just a generic rejection. Overall I feel pretty neutral about the whole thing.
Interview questions [1]
Question 1
what was the most complex integration you have architected?
Interview process was actually quite fun. Well structured, different style than the usual slop you see with companies these days. Couple behavioral rounds, couple technical rounds. Focussing on culture and product fit. Those went decently well, I reckon I messed up the second tech round tho. Either way, the coding challenges were fun and the team was great to chat with. I genuinely thought I'd make it through but unfortunately no. Still, enjoyed it though. I believe there's the initial behavioral call, the manager round, the coding assessment and tech round, then the onsite. Anyways, fun company, fun interview loop. I liked it, though I got rejected.
Interview questions [1]
Question 1
Keyword extractions from a varied string. That was a fun sub-challenge in the coding exercise. Mind you, the exercise is multiple related challenges, so missing or not completing one would render no output for the entire thing.