

21·
14 days agoIf you’re trying to shortcut the dev process by running an llm agent for reviewing PRs, you deserve every cost overrun you get. Letting an llm review anything written by an llm is one of the dumbest things I can imagine. If one of my devs suggested that to me, they’d have their access removed. I have zero sympathy for cost overrun, the litany of production incidents, or the amount of unmaintainable code that will inevitability come from such a decision.
I always schedule them the same day if I can. Waiting between interviews does no one any good. I do a 45 minute with them for a one-on-one interview. I have a few the people they’d be working with ready to do more of a technical interview for an hour or so. If things don’t go well after either, I let them know, and we part ways. If they do well, I put them in the yes pile. After one week from the first yes person, I choose the one I think best. Sometimes there is just one. When there’s more, I choose the best fit and let the others know.
One time, when hiring a qa, I had two people who where both great. I really hated having to tell one of them no. A month later, a qa position opened on a different team and I passed on her resume. After she was hired, I sort of poached her from the hiring manager. She still reports to them, but she works entirely on my projects. But that’s an aside.
My point is, a single interview is more than sufficient to hire anyone. The multiple interview crap, that’s become so common, is done solely to stress someone out so they’ll take a lower salary just to stop the stress.
Edit: Grammer