Earlier quoted context omitted.
> a software engineer who considers writing any tests beneath them, a job for someone else I'd also balk at that for an interview take-home test. I was an Indian QE guy looking for a dev job once. I was that guy whose job was to write tests for someone else, which wasn't fun at all. If I had interviewed somewhere and I felt the conversation was going towards "how good are you at writing tests, write some", I'd have n…
I can see why your experience might lead you to that particular bias. However, that's not where he's coming from. If you've followed his blog over the years, you'll see that he believes you cannot be a decent hardware engineer unless you also have some formal verification chops and use formal methods as part of your design methodology. That's his bias. He expects a practicing HDL engineer to write their own verificat…
The client trusts him, not a theoretical average engineer but the exact specific engineer who has been successfully delivering results. The client wants another one of those HDL engineers who handles verification. The candidates rejection is indeed an impasse, such happens. Doesn't mean the candidate was wise.