If your primary innovation is business model, and all the interesting tech you end up working on is purely a result of your scale, well, you're not a tech company. You're a company.
Those companies are probably great (or at least, so far as great == profitable/growing), but calling them 'tech' loses sight of what's interesting about tech to me. I'd argue that true 'tech' companies create technology as their primary or near-primary focus.
So... Uber? Not a tech company, I think. AirBnB? Not tech. Apple? Tech. Google? Tech.
(And yes, I'm aware these companies I call 'non-tech' are probably solving hard, tech-related problems; their developers contribute MLOC to open source projects, and they even release internal tools as open source. But to me, what you sell defines what you are as a company.)
I don't know how anyone gets away with calling call center employees "tech workers." It's a farcical trend and a way to make headlines ("Tech workers making only $30k a year"). They're not more tech workers than a developer at a news company is a journalist.
Countless of these articles critiquing the tech work culture pop on HN and it's rarely ever written by devs/management. The tone always comes off as criticism from 'outsiders' who worked within the company, who treat the pride taken in creating eccentric workplaces as somewhat alien to them. Maybe because they aren't truly insiders to the culture... especially in the sense that they aren't ever the creators/leaders or long term members. Only temporarily working within the environment before going back to more typical corporate environments from where they write their analysis with a certain level of cynicism.
The part in the fresh air interview that talks about jargon is especially interesting.
Well, I agree this sorts of equivocation can completely confuse important issues. But worth noting that you will always be able to ignore an opposing viewpoint if they have to agree with you on the definition of every term. Better to simply say in this case that the terminology confusion invalidates parts of his argument, and then when replying to bend over backwards to state your thesis unambiguously (in both languages if necessary).
Generally newly created, but not necessarily. In 'The Lean Startup' by Eric Ries one of the primary examples is based around Intuit, which is a large publicly traded company.
You're wrong, if you work at a tech company you're a tech worker. Programmers like to think they're special, but you're the help just like the sales people, support people etc
There's also the idea at this point of a stereotypical "start-up culture" that lives beyond the idea of whatever a "start-up" is. This also breaks the circular definition, because from that perspective "start-ups" no longer define "start-up culture".
The article used the word start-up 3 times, plus one more in the title of his book. The company he worked for however, HubSpot is 10 years old and public and thus by definition is not a startup. Other two companies mentioned, Amazon and Netflix are both over a decade old and public and thus are not start-ups by any stretch of the imagination. Startups and tech companies are not synonymous and using them interchangeably is harmful to our discourse. If we can't agree on what words mean, how can we agree on deeper issues?
PS. I also have issue with author's use of the word "tech worker" to describe telemarketers. I maybe wrong, but a "tech worker" to me is not someone who works for a tech company but rather is one who creating the tech.