I just got done with my onsite interview at Hex, so I wanted to contribute this data point.
For the full stack track, I went through quite a few rounds: web dev, system design, product taste, behavioral, and a CTO round. The feedback I ended up getting was that the web dev round relied too much on AI... Personally, I think the line for this kind of AI-native interview format is actually pretty hard to gauge. The interviewer will explicitly tell you that you're allowed to use AI, but they usually won't specify exactly how much you're supposed to lean on it. Sometimes AI generates a ton of logic in one shot, and when the code starts breaking, I end up spending a lot of time opening Chrome DevTools, stepping through breakpoints one by one to understand and debug the logic it generated... Not sure how everyone else approaches this interview format.
For web dev: design a notebook app that uses Hex's provided API to auto-sync notes.
For system design: I honestly forget what I was asked, it didn't seem particularly hard.
For product taste, the designer round was: a budget airline looking to differentiate itself from competitors by offering an in-flight entertainment system.
Requirements:
- Full color
- Touch screen, very small
- Hardware buttons are okay, but not ideal
- Where it lives is up to us
- Content to include: flight info, music, etc.
After that came a behavioral round, a round with the manager, and one with the CTO. Then a guy walked me around the office for a bit and we chatted about this and that.
Discussion
Loading comments…