It's impossible for every job task that needs to be done to always be interesting and fulfilling, even engineering jobs. Sometimes there's dirty work that had to be done that just sucks, and someone has to be paid to do it. My point is, if I advertise a job to clean toilets, don't show up and complain that cleaning toilets is boring. I know its boring, but I have to paid someone to do it, or buy self-cleaning Japanese toilets. I've had coding jobs before that were metaphorical equivalent of toilet cleaning, and I hated them, but sometimes you need to make rent. I did the work, hated it, and then went on to other more interesting things (founded a startup). I didn't bother submitting an editorial to a newspaper on the experience. It just seems self indulgent to me.
I didn't mean it in the sense "he is inferior to SWEs", I mean it from the sense that Google is a tech company, and at tech companies, the interesting jobs where new product development happens generally goes to engineers, PMs, product and UI designers.
It would be no different than if I went to work at a Hospital, I'd end up in claims processing or administration probably, and someone could say "he's not a doctor or nurse or medically trained, so of course, he's pushing paper"
To some extent, it's up to you to make your job interesting and fulfilling. If this guy spent 2 years doing HR and it was a grind, then he knew all the pain points and probably how to improve the workflow. Why didn't he take the initiative, get some coworkers together, and try to design a better system rather than wear earplugs eating alone in the cafe?
Google expects and depends on people to take initiative. If my project is not interesting, either I find another team that has a more interesting project, or I invent a project for myself and shop it to cosigners. I'm not supposed to sit here stewing in unhappiness for years waiting for my manager to say "oh, I noticed you aren't being fulfilled. Here's a new project to fulfill you."
It's not that only SWEs matter. Most startups have a technical founder and a non-technical founder. Non-technical skills often matter more than technical ones.
