[a-dub]

here's an idea for an "experienced" technical interview structure. "we care about x, y and z. you have forty five minutes to convince us that you will meaningful help us achieve our goals. we then will take 30 minutes to push on technical details as we see fit. you will be judged based on technical content, choices, taste and your overall approach and strategy for moving us forward and convincing us that you're the right person to do it. good luck!"

[BugsJustFindMe]

> we care about x, y and z. you have forty five minutes to convince us that you will meaningful help us achieve our goals. we then will take 30 minutes to push on technical details

This part is good.

> as we see fit. you will be judged based on technical content, choices, taste and your overall approach and strategy for moving us forward and convincing us that you're the right person to do it. good luck!

This part is confrontational and will lead to worse outcomes. "As we see fit" signals capriciousness. "You will be judged" signals hostility. "you're the right person" engineers conflict; there is no "the right" person, only "a good" person. And telling someone "good luck!" in this context is like telling them to try not to die while standing on a narrow plank over a pit of sharp spikes. No matter how you think you mean it, it will come across as callous to many.

[FireBeyond]

I do agree with your assessment, on both parts, but I think it could survive with minor tweaking.

"We are going to push on the technical details, both those we agree with and disagree with. This is where the rubber meets the road. You've painted a picture, how does it stand up to scrutiny and challenge. In the end, while there may not be perfect alignment, we're looking to see how your ideas go through the process of validation and how we get there, communication, exploration, and collaboration-wise."

[BugsJustFindMe]

I'm not sure what exactly that's meant to do other than using more words to say the same thing only this time with hackneyed cliches. IME it's best to avoid empty metaphor that does little more than occupy space.

Like...

> This is where the rubber meets the road. You've painted a picture, ...

Was this written by AI? It's so bad, lol.

[FireBeyond]

Hah, it is, in hindsight, and I agree (and bleh, last thing I want to sound like is AI!). But I think my point is more - if it had been framed as something like "defending your thesis/dissertation", seeing if your choices stand up to scrutiny, versus the somewhat snooty down-the-nose feeling of "We are judging you. Speak now." then it is better - and real: your architecture and code decisions should stand up to review/critique, after all.

[BugsJustFindMe]

Framing something as "defending" against "critique" creates an interaction that is immediately adversarial, which is not so far distant from judging down-the-nose, IMO. They are words of combat and criticism, and I think we get better outcomes when we find ways to ask a candidate to "discuss strengths and compromises" without that. I don't want any of my candidates to feel like they are on defense against me in a scenario where they know that there is a catastrophic power imbalance and I am able to use literally any reason I want to kick them to the street. People don't think well in that kind of situation.

> last thing I want to sound like is AI!

My suggestion of it signaling AI was somewhat tongue-in-cheek. Humans have been writing inexpertly and injecting cliched fluff since the invention of writing. Communicating with precision is one of the most difficult things that any of us ever do.

[paulluuk]

I wonder how many great engineers with stage fright you would lose this way, though.