He was fired from the contracting firm, for which he was a W2. His status doesn't really factor into this.
That is his claim.
We don't know what else was going on and due to confidentiality rules, we're unlikely to hear anything from Pillar.
Based on his reaction on Facebook, Medium, and in these comments, I'd wager they had other concerns.
It seems like a lot of new consultants don't understand the differences between working as a 1099 contractor vs. W2 contractor vs. regular employee. I've met plenty of people who mistake a W2 contractor as the same as a regular employee except that the work is temporary.
I would like to point out that W2 contractors should expect their performance to be evaluated by the hour because that's the rate the client is being is charged for solutions. That's why it's important for W2 contractors to work only during normal business hours so that the client can't claim (later when payment is due) that the client didn't have opportunity to approve of said work and evaluate said work when the contractor delivered solutions to them.
Nothing is ever that simple. There are perfectly valid reasons for some companies to be unhappy with a contractor unilaterally deciding to work until 2am, and then not turning up for work the next day.
Falling asleep after your manager texts you to see why you haven't turned up for work today is unprofessional, whether you were staying up late night to code or to binge watch Netflix.
Please note that I am talking about this specific situation here. If you are working on your own products or in a team where people view this as expected behaviour, staying up late to take advantage of as many 'in the zone hours' as possible seems like an effective use of a programmer's time.
Don't stay up until 2AM working on your contracting firm's projects. Don't personalize contract assignments. Don't act for your firm's clients like you're their full-time employee: you aren't. Don't assume clients are OK with you coming in super late because that's what programmers do: many aren't OK with that.
There are some really great things about working for contracting firms: you get a W2 and benefits and mostly all the downside risk protection of an employee while getting exposed to all the random projects a consultancy gets. You get to dip your toes into lots of different projects. And when you get sick of a certain kind of project, often, you can easily no-harm no-foul switch to other projects. Contracting firms can be great.
But if you try to treat a contracting firm the way you would a startup or tech product company, things are going to suck for you. In particular: you must force yourself to deliver a day's worth of work and then put things down. If you're compulsive and need to work late into the night, stop doing client work, and switch to personal projects.
Contracting firms usually can't bill for your 2AM binge coding session. Clients generally want to pay for work done during business hours on a well-defined schedule. It does not matter that you believe that's not how software is delivered; it's how software is bought. If you run yourself ragged refactoring things until late in the evening, your contracting firm isn't going to be impressed with you: they're going to see, from 1000 miles away, that you're burning yourself out pointlessly in a manner that isn't going to make them an extra penny, and they're going to get pissed.