Meat Filter

Every engineering job now has a front door, and standing in the front door is a person. The badge says hiring manager, or talent partner, or people experience lead, depending on what the title inflation was doing the year they were onboarded. Their job is to determine whether you, a person with twenty years of building distributed systems, are technically qualified. Their qualification for determining this is that they were available.

The call starts on time, which is the last thing about it that will make sense. They open with a warm paragraph about culture, delivered at the cadence of someone who has delivered it eleven times today. Then they look down — you can see them look down, the eyes drop exactly four centimeters — and read, carefully, the way a tourist reads a menu in a language they don't speak: "Can you tell me about your experience with... Kubernetes?" They pronounce it like a Greek island. They will write down whatever you say, which is the important part, because they will not be able to evaluate it, which is the other important part.

You answer. You mention that you migrated a fleet of services off it last year because it was overkill for the workload. This is, technically, the best possible answer: it demonstrates depth, judgment, and scar tissue. On their screen it registers as "did not like Kubernetes," and somewhere a checkbox goes the wrong color. The sheet did not have a field for nuance. The sheet has never met nuance. The sheet was written by an engineer three reorgs ago, who has since left, possibly because of this process.

And then the classic. The role is for an engineer building autonomous AI agents — systems that plan, write their own code, call tools, deploy themselves, and occasionally email customers at 3 a.m. It is 2026. And the meat filter looks down, four centimeters, reading a script from 2015, and asks, with total sincerity: "Would you say you're more frontend or more backend?" You might as well be asked whether you're more horse or more carriage. The agent does not have a front end. The agent barely has a back end. Half the time the agent is the end. But the script has two boxes, so you say "a bit of both," which is the answer that gets you forwarded, and the agent you were going to build quietly ships itself while you're on the call.

Then comes the part where they ask, "Do you have any questions for me?" And here is a free piece of advice, offered in the spirit of public safety: do not. Every question you ask is a small act of cruelty. Ask what the deployment pipeline looks like and watch two things happen. Either they dodge — "great question, that's definitely something you can dig into with the team!" — which is a sentence engineered, like a pool noodle, to keep anything from getting hurt. Or, worse, they try. They attempt an answer. They say "I believe it's in the cloud," and then, sensing weakness, add "the AWS one," and with every additional word you can watch them get measurably less intelligent in real time, a man sinking in quicksand by flailing. You came here to be evaluated. You are now, against your will, conducting a wellness check.

It is important, at this point, to stop being angry, because the anger is based on a category error. You thought this was an interview. It is not. It is a filter, and not a smart one — a meat filter, a biological form-field. Its entire function in the system is three operations: confirm that you are a human, capture a phone number, and forward a PDF to the next human. That's it. It is a CAPTCHA with a LinkedIn profile. Getting upset that it doesn't understand distributed systems is like being insulted that the turnstile at the subway didn't ask about your thesis.

And to be fair to the meat filter, it is doing exactly what the company built it to do. Nobody at the top wanted engineers screening engineers; engineers are expensive, and making them talk to strangers lowers velocity and raises attrition. So the company hired the cheapest possible gate and handed it a script, the way a nightclub hires a bouncer and hands him a clipboard. The bouncer doesn't know if you can dance. He knows if you're on the list. The difference is the bouncer knows he's a bouncer.

There is a final irony, and it is the kind this site likes. The meat filter is the single most automatable job in the entire hiring pipeline. Read a script, capture a field, forward a document, express warmth in a fixed paragraph: there is no step of it that the machine can't do better, faster, and with correct pronunciation of Kubernetes. Which means the one person in the building qualified to evaluate whether a hiring manager is technically necessary is the candidate on the other end of the call, nodding politely, already knowing the answer.

So be kind. Answer the questions. Spell your phone number slowly. Ask nothing. You are not being judged. You are being forwarded.