That doesn't really sound like a non-technical employee to me. Maybe a question of terminology, or the primary focus of the person's role, but a person who is coding sample apps using the company's API sounds pretty damn technical.
That doesn't really sound like a non-technical employee to me. Maybe a question of terminology, or the primary focus of the person's role, but a person who is coding sample apps using the company's API sounds pretty damn technical.
Are they good at what they do? Yes. Does what they do require that type of abstract thinking and computer skills? Not that I have seen, they seem effective at what they do, the lights are on, the place runs smoothly.
Edit: too old to edit! But still, thanks for the info.
On HN, I believe that people are trying to make a positive contribution when the post, and while correcting people on the internet can seem pedantic, I take it to be a positive contribution and an opportunity to learn something.
Hopefully I don't make the same mistake twice!
Perhaps "non-SE" or "non-Programmer" or "non-Engineer" might be closest to what we're trying to say here.
It's unfortunate that some technical people look down on others in these kind of roles.
I think all this really depends on the where the startup is in timeframe. A larger company will have more specialised employees who do only one thing, but a smaller one would have a single employee doing multiple roles even if in both cases their titles were exactly the same.
That one.
A implies B does not necessarily mean that B implies A. She's just saying that it's possible for a person to have skills beyond those required for their role. The examples you quoted aren't listed as what should be expectations of her role, they're examples of how she often pulls in her not-in-the-job-req skills in the service of her official duties.