jdwyah

I've done 100s of interviews over the years. But haven't been doing any for the past 3.

But now we're scaling, so need to figure out how to do a technical interview again. But... man, all my technical interview methods feel obsolete / inadequate. Seems pretty silly to not let a candidate use Cursor/Claude when I would 100% be expecting them to use it every day. But also if we just vibe something together it'll be darn hard to figure out what they actually know.

Looking for a process for mid to sr level.

Anybody feel like they've figured this out yet?

- "Take a look at this PR / codebase" doesn't age well, because "claude make me a powerpoint that ELI5s this codebase" is better.

- Simple coding puzzle was never very good, but at least showed they could type. All of this is just LLM fodder now, do I really care?

- Complex system debug / comprehension type questions are always hit-or-miss in my experience. I feel like any setup I do to make a tough to solve problem will be trivial for Claude, so doesn't feel authentic either.

- System design at ~whiteboard still feels reasonable / CS basics.

CLI are nice, but tools like Linear have got me accustomed to typing command-k and then autocompleting my way to success.

We just updated ours to be much more interactive and while we've kept the standard CLI argument behavior, I have fully converted and don't see myself going back anytime soon.

Basically it meant taking common option sets and adding a descriptions that make them more discoverable, then letting you search. eg

$ cli ? What would you like to do? c create Create a new config create --env-var Create an ENV Var provided item with --env-var create --secret Create a new secret in Prefab with --secret

Then being flexible enough to collect the other pieces of information it needs afterwards (what environment would you like to set the secret in / etc)

Are there any CLIs that use this pattern particularly successfully? I'd love to see how far we can take this.