From Belonging to Burnout, Five Years at Airbnb
news.techworkerscoalition.org
news.techworkerscoalition.org
Since I first used Airbnb 7 years ago, the only real change I can think of is when they added experiences (which is awesome don’t get me wrong), surely at some point you begin to wonder if we are utilising this talent effectively.
Engineers with 5 YOE are making $500k+ a year at these companies because they are generating much more than that in revenues and profits for the companies. Airbnb is worth $110B.
It's not all blinking cursors, there are thousands of little experiments going on all the time. Increasing the number of bookings by 2% here, 3% there. Increasing the average price of bookings. Random extra features here and there to close that one whale of a client. Expanding into corporate accounts. Improving performance by 5% to take a big chunk out of the tens of millions of dollars infrastructure bill.
From a 10,000 foot view looking at the product, it always looks like it's 90% done in the first couple of years and then things just coast along lazily. But from a profit point of view, that last 10% can generate hugely outsized returns. It's the power of exponential growth, all those extra late nights and tiny improvements that move the needle just a little bit all compound over time.
In a big company belief that something is worthwhile is better than actual value because market forces, that care about actual value, cannot act on each sub-project out of thousands of projects in the same company independently; but managers, which by definition can only care about their beliefs (idealism rears its ugly head again) do very much act on teams independently. The engineering department will pay $500k+ to engineers who exist only to pervert insufficiently representative metrics just as readily as the market would stop that from happening if they weren't hiding in an autocratic structure hundreds of times larger than the limits of their own abilities to be wasteful.
Indeed, there is no reason to think that the market has a greater ability to eliminate waste within a company worth $100B than it has within a communist country (which exists as an entity in international markets) worth the same.
Also $500k engineers should have as the only purpose in life to do engineering, working on projects that are found by management to be important, not to find themselves something to do. Most engineers are bad at business decisions and it would be a waste of time and skills for them to do it anyway. An engineer with business knowledge is no longer an engineer, is a product owner or a senior architect, etc.
I've always felt that there is a dilemma in this space. Any number of small UI features can claim a small increase that are often just noise and curated data (assuming no malicious baking), the cumulative increase isn't even close what the claims stacks up to.
The only fundamental way for a business to make more money is to invent actual, new feature and business models. Shifting a box here and there, enlarging an icon just creates a generation of glorified engineers and PMs who are placing their attention entirely on the wrong thing. Yet the success reporting often rewards this behavior and eventually drown the business in fruitless 'noise' endeavors that favors short term gains over actual innovation.
So a single data point? I didn't see it claimed that there is not a single small thing that can have a big effect. It's about large numbers. I think individual examples obfuscate more than they help us understand, when it is given in lieu of wider view instead of just as a support for one.
In this context, I would also like to see considerations of a larger picture. Sure, it helps any single company make more money. What about beyond that? Because money is a proximate goal, even if it's the ultimate one for a business, from a human society point of view that introduced this tool for a specific reason and not for its own sake.
For example, what does it mean to have some ultra-optimized large companies dominating their space? Would society really lose something without some micro-optimizations, even if they raise profit? The people who end up not making a purchase on a website because they are not as much caught in the optimized patterns, is it actually bad for them, or maybe they are actually better off and the optimizations tricked them into making an actually unfavorable (even if slightly) purchase? I think there is more to consider than just the view from the respective company or even the department. Are the means used to win actually good from a wider point of view that is not centered on that winner alone?
If someone does not make a purchase because something is slightly off, are they actually worse off, neutral or better in the end? It can't have been all that important to them to make that transaction, no?
The answer to this is better measurement and statistical analysis, not abandoning the effort entirely. It does take more than "haha, trend line go up" to prove a change had a positive impact, but it can be done.
On your second point, though, if all you focus on is building new features, you are losing out on tons of unrealised gains you could've had by making an old feature work better. At the scale a bigco works in, small percentages add up to quite a bit.
From a company’s perspective, the PMs and devs good at optimizing existing features already exist. Why not hire them to work alongside and behind the devs and PMs good at developing new capabilities?
I’m not sure this is fair for services like Airbnb where what they sell is conveniences.
Their entire product existed before Airbnb. It even existed before the internet. What Airbnb did so successful was that they branded themselves with a good product that disrupted the market by being easier to use.
The thing about disrupting markets by selling easy of use, is that your competition is already well versed in the market you disrupted. Some of them may do the dinosaur but others will take your ideas and try to make them better. If you don’t continuously improve the ease or use of your product, then people are going to download eurobooking or whatever other options there are now instead.
You know this, because you’ve likely done it yourself a million times with various applications that do the same thing, but some find a way to be easier to use.
Obviously these companies are going to want to find (or invent) new products to get included. But that is typically more of a non-software quest that eventually leads to some of the engineers being tasked with building what the marketing/sales/business process people find.
Before you complain how people waste their talent, maybe ask yourself what you did to help them. Or broadly how to truly make society reward people who do God's work. Society cares about getting likes, don't want to pay even a little for quality work, so smart people give them a platform to earn likes and show them ads. Everyone is complicit, the worst among them put all blame on "smart people".
right now these fake tech companies are literally the best we can do to keep everything moving forward on an economic basis.
Just as we tricked each other into bidding up crypto tokens, we could self-hypnotize to bid up biotech patents or something similar, but we have not yet decided to do that.
Another reason to have in-house expertise in various areas is that they easily pay for themselves, which is a special case of the generic argument that large companies should be larger than most people expect because tiny percentage gains are worth a large amount in absolute dollars. If, in the lifetime of the specialist team like the kernel team, a single person found something that persistently reduced TCO by 0.5%, that would pay for the team in perpetuity, and Twitter’s kernel team has found many such changes.
If removing a blinking cursor has a 1% chance to increase the booking rate by even 0.1%, , then it's worth it for AirBNB to pay an engineer to implement the change.
The keyword "impactful engineering" needs some clarification though.
It does not mean there's a 100x guy walking around the office while everyone is slacking off.
A specific proof of concept hacked together by a guy in a week might eventually become the company's flagship product. That's impact. However, the thing needs to be rewritten from scratch to become production ready or even deployable, and that takes far more work that does not fit the definition of "impactful".
I personally know a principal engineer of a FANG which single-handedly wrote the proof of concepts of more than a few projects that thousands of users use every single day. From his own words following one of his recent presentations, "this needs to be rewritten from scratch as this would get me rejected from our job interviews".
A surgical ten lines of code across 5 services can absolutely create billions of dollars out of thin air. The combination of technical, political and domain expertise required for such changes is relatively rare.
(I mean political in the purest, non-controversial sense, i.e. the communication skills to answer objections and acquire group consensus on the required change.)
That is probably true. But we shouldn’t forget that these people can do these things often because they are supported by a large number of people who do the mundane tasks that need to be done.
For example, lets say you give a project to a competent engineer, he writes a clean and maintainable solution quickly alone. But if you schedule it to him together with another engineer of similar status but much less competent, then the other engineer will take a part of the project and basically block it since the competent engineer is unlikely to to take that fight, and instead just lets the project stall.
You don't get promoted for pointing out incompetence, there is a reason managers hires consultants to do that for them. This made me wonder, are there software consultants who act like management consultants and mostly go in and fire a lot of people? I don't think management consultants would do a good job of firing the right software people, they would need to be engineers.
It’s really hard to be surgical about this because who wants to be the good engineer that has to pick up the barely functioning pieces of code left behind. Who wants to reward a solid engineer with a big refactor job on an already late/failing project? The optics aren’t great. I’m not saying it never works, but as a general rule, deferring the project is often a better option.
It's all a numbers game. The median member of your kernel team, the median fire extinguisher, the median link to a sales web page, the median joist in a floor, all will do nothing of note. But if you distribute the resources properly they will hopefully be where they are needed to generate a positive ROI that pays for the overall system. If you zoom in too much or too little it all looks silly.
You need a bench. Some of the brilliant folks who are great at pushing through problems are awful and maintenance and sustainment. I worked for a bit in a SWAT engineering team tasked with addressing crisis problems or emergency response. If you don’t have people you’re developing on the bench, you won’t be able to respond to those types of things and will get bogged down with tech debt.
I was a faux “10x” person because I had license to break the rules to get shit done - because the value of what we were doing was higher than the cost of cleaning up the mess. (Not because of any brilliance on my or the teams part) We did two years worth of work in a month, but it’s still being refactored 3 years later.
Meta-meta-question: assuming that it does, how does the line get described (let alone drawn) dividing "this work contributes to identifying the 1%" from "this is a waste of time"?
(Insert something about gradient descent and local vs global maximums here)
I'll call this a genuine question, I could definitely use some refinement of my own optimization of this problem space (and not wind up in micro-optimized dead ends etc).
If the payoff in the 1% case is high enough, then you don't have to know beforehand! Just do all 100 changes and the one winner pays for all the rest.
Sure, the major shareholders might see their wealth increase noticeably, but anyone else (even small shareholders through option programmes) will generally not see a big effect.
Now, is that additional shareholder wealth really worth the years of engineer effort going into that?
Don't get me wrong: airbnb is an amazing service that has improved the lives of myself and other regular people.
I'm just arguing that maybe most of the benefit from society happened within the first couple of years plus maintenance and critical innovation as needed, and the rest is suboptimising for the benefit of the few.
Where the engineers are partially compensated in stock, RSUs or options? Absolutely. Its not like they're focusing on optimisations at the expenses of other, more dramatic changes.
Leaving a review has become a huge bloated mess. The sight is slow as heck. And driving prices up just makes me more likely to look at alternatives. It’s still good, but it feels increasingly less fast and cheap.
AirBnb lost billions of dollars last year, and it has rarely made positive quarterly earnings. Based on your example, the engineers are highly overpaid as there efforts rarely generate a profit. They are being paid by funds from speculators (stockholders and venture capital) that are betting on huge profits in the future.
In reality, these engineers are being paid due to labor market forces and extremely focused recruiting policies (eg only hiring those with degrees from top engineering schools or poaching workers from other companies that have similar policies).
The simple truth that most software engineers don't want to hear is - people are quite conservative in this. If it works once, most folks would be extremely happy to keep using it for next 20 years in exactly same way, as it is. Bug-less has higher priority than shiny (which is highly subjective) and constantly changing.
Unfortunately this tech oligopoly landscape doesn't leave users many ways to express this preference, but I often wonder if the culture will change at some point in the future as the industry matures.
An aging western population might have an influence here as well, in the long term. Older folks have less tolerance for having to relearn how to do the same thing they already knew how to do for the umpteenth time.
Signups/purchase flows are meant to trap users and keep them from escaping--not create a smooth, easy to use experience
Employees get so aligned with these experiment systems that obvious faults in statistical approaches go unnoticed. At the end of the day it becomes just a way to put something on your promotion case.
In most cases, core product stays the same over the years without significant innovation.
That's because capitalism is a winner-takes-all game.
Spending 1000000 manhours to get 0.001% improvement in quality pays off, for exactly this shitty reason.
I don't think engineers at AirBnb are overpaid or wasting their time but I do think most engineering leadership doesn't understand the idea of _true_ reliability where a service can run itself for long stretches of time.
You're grossly misrepresenting the problems being faced and what forces engineers to work into the wee hours of the morning.
Just because stuff seems done to you or you notice no change, that does not mean nothing is being worked on.
Let's take basic A/B testing. To you, it's a blinking cursor. For the company, it's a bunch of business metrics being reported from N different components feeding into a data lake, with different versions of the same feature being deployed simultaneously to specific subsets of all customers based on their profile. But the cursor blinks differently depending on the market, and needs to comply with accessibility guidelines, on all X supported browsers regardless of their quirks. Some markets might not even have a cursor at all. Perhaps your cursor is only expected to show in a specific geographical location.
But you see a blinking cursor, and as you are oblivious to everything then you think it's just a tag somewhere. To you that's just a line of HTML, right? How hard could that be?
These basic everyday requirements are oblivious to those who have zero first-hand contact or experience with professional user-facing problems imposed by business requirements.
However, just because you're oblivious or unfamiliar to these requirements, they don't mean they aren't requirements.
Think about it for a second. If it's necessary to target a service to specific geographical markets to comply with legal and/or business requirents, and given it's considerably more profitable to target a shop to a customer based on their personal interests, why would you ignore that and naively presume that the hypothetical "blinking cursor" is straight-forward to implement? And I'm not even touching hard technical probs which most developers aren't experienced or competent in, such as security and reliability.
There is a widespread problem in software development which is this this tendency to be very opinionated over all problems in spite of being totally ignorant and oblivious to the underlying problem domain. Everyone is an idiot except themselves, who always hold the answer in spite of not even knowingwhat the problem is, let alone understanding it.
Unless you're reinventing the wheel for each modification.
What leads you to believe in that? I mean, you have zero insight or understanding how things work or were designed. You have zero idea of where that blinking cursor comes from, let alone who owns that particular bit of code.
Let's think things through for a moment. Let's imagine you're talking about a blinking cursor in a random page from Google or Amazon. These are organizations where you have teams owning small widgets that show off only in specific pages, and that the page that you see in your browser come from a lengthy page engine pipeline that has all sorts of tests and failsafes, not to mention regional and localized deployments managed by whatever deployment policy.
This doesn't even take into account the whole workflow from product managers, who often demand data on the impact of touching a button.
You don't just edit a HTML file and hit save, don't you?
Could you paint me a realistic scenario for such multifaceted complexity revolving around this blinking cursor in a particular field? I can see how this might depend on a language/writing system but kind of get lost beyond that.
I do have experience with such "professional user-facing problems imposed by business requirements" btw but they tend to be more related to desktop and factory software each used by hundreds which is probably a few zeroes less than what we're talking about here.
>And I'm not even touching hard technical probs which most developers aren't experienced or competent in, such as security and reliability.
I know more than most that software can behave in weird ways but don't you think if there's a reasonable worry that altering this blinking cursor affects security that something is off?
This isn't just a personal opinion. I've heard it spontaneously from various friends and acquaintances.
Granted we're mostly a similar demographic in a single market.
But even so.
I can't and won't speak on behalf of AirBnB, but you should keep in mind that in general:
a) all software grows by accretion until a breaking point,
b) paying off technical debt without solving any concrete problem or adding any tangible benefit is not considered a worthwhile investment,
c) a site did not changed for the worse if the data shows its conversion rate increased.
It's a business whose product transcends the site it's presented on, and exists in spite of the quality of its site.
If you think about it, both are true. If you don't think these are true, you are far too caught up in a hamsterwheel to notice.
As a company hires more and more people, modern development and devops can create as much unnecessary complexity as needed.
Basically a common tactic of corporations is to espouse "we are a family" but it is just a manipulation tactic for employees to work long-hours and to give their all to the company. The "we are a family" mantra would be fine if it was coupled with a healthy separation of work and life; with the biggest indicator being that healthy working hours (around regular 8 to 9 work hours only) is maintained.
In contrast, something like Netflix culture which is "we are a team and not a family" seems like to be more of a healthier alternative. On a last point, the "we are a family" (i.e. we care about our employees as persons instead of just means or cogs) mantra is fine but it usually turns into "we are a toxic family" (i.e. give your all to the company) instead of it being a "we are a healthy family" (i.e. our company values each employee).
Also look at what a company does instead of what it says.
Whether it is a "family" or a "team," you can be assured that the company will be looking out for itself first and foremost, potentially to the detriment of the employees. I don't think that's necessarily bad, but you as an individual need to watch out for yourself no matter what rhetoric the company uses.
If Netflix wants to fire half their engineering team every year, that's fine, as long as everyone walks into the arrangement with the mindset of a contractor, or a mercenary who's only there for the paycheque.
Considering the same labour laws apply to Airbnb and Netflix, yes it's a far more honest approach. Not admirable, not right or fair, but a lot less manipulative.
Netflix pays well, has a generous severance package, and is honest about its culture. I think there is nothing wrong with them making it easy to fire.
Take care of yourself.
For all other companies always reciprocate their loyalty. If there is none from their side, don’t invest in the company.
When you are just starting out fresh from study you still believe in the “we can do this team if only we work a bit harder.” , but that’s usually a myth.
I had great managers who, if up to them entirely, would have my interests at heart (as demonstrated by decisions fully under their control), but hey, they don't call the shots in the end.
You're a cog in a machine and you may be the golden child while they need you, but once they don't, you're out. And all the talk of "family" is just that, talk. It's why the fake "we care" stuff gets under my skin - it's a lie - they care about "you" in the theoretical employee sense, but they don't care about you as an individual. Individual relationships do matter, but "the corp" in the end is an emotionless machine.
And it doesn't matter whether you're a desk analyst or a CEO, I've seen both go from "calling the shots" to "not aligned to where the company wants to do" really damn quick.
I guess a lot of people in tech have gone through the experience of getting a job straight out of college, working yourself to death trying to prove something (whether that's to yourself or your employer) and getting burnt out to some degree, or not seeing any dividends for it. These companies do a very good job at blurring the lines between expectations and what's realistic through the "perks" of the job and whatever flavor of culture reigns.
In my job I deal a lot with low and middle management in lots of companies. Unfortunately I did not find any exception to the general observation that today's low and middle management is a bunch of incompetent impostors with their career as the only concern, occupation and reason in life. That includes technology companies that I cannot name, but known by various acronyms. And I am saying this as a lower level manager myself.
This guy's story is not a rare one, and it points to a larger spiritual crisis in modern life I think.
The perfect worker for them oh god lol.
The term "airfam" is such a weird thing, people saying 'Thanks fam!" these days... I am not your family, I will not lend you 20,000$ if you in a rough spot, I will not take care of your kids if you die. Maybe I just take the word 'family' too literally hah, maybe a bad habit from expecting variable names to do what they are called
“Families” can be wonderful.
But blood families can be just as abusive, as manipulative, aggrandizing and as toxic as the “work” family.
- If you are an engineer, your total comp is easily north of $200,000. At that pay scale compared to other careers, I expect (and I did) to burn through the night as needed. That's a lot of money for anyone to expect to have a comfortable work/life balance. I always compare myself with doctors residency, accountants, or labor jobs, who would do a lot more work for a lot less. Tech pay, benefit, and work/life balance are outrageously good in my opinion.
- I have worked at AirBnB, Stripe, and Robinhood. And between the 3, AirBnB actually has the chillest work culture. It's known to be "too much democratic debate vs work output". But your experience may be different.
- Most importantly: Just as much as you can quit the company whenever you like, companies can also lay you off whenever they want. My main takeaway is to take care of yourself. Don't buy into Airfam or company family. You do what's right for you and company does what's right for them. (I can't comment on the specifics if Airbnb layoff was the right business move).
This isn't true at all. In my last job (not tech) a "brutal" week might be 50 hrs and people were making double that, albeit in more senior roles (10+ years of experience).
How are other careers relevant? You take the best offer you can get in the (SWE) market, and if avoiding burnout is a choice criterion for you, you avoid the corresponding companies. Many of them are willing to pay the same compensation or more with a reasonable work-life balance, especially once they realize that they also benefit from it one way or another.
One benefit of a free market is to help optimize resource allocations, and telling yourself "it could be worse" rather than asking "could it be better?" is counterproductive.
The US is mixed, and frankly leaning heavily to command-by-committee, same thing that caused the commies to fail. Our committee is the FOMC. Low rates increase valuations on anyone who promises 'the future'. High tech salaries are almost certainly a distortion of their meaningful value.
- I get flexibility at other times to make up for it.
- It isn't super frequent or for very long.
- It is for a good reason.
I don't think even 300k or 400k (or whatever the going rate is for 20 YoE) would be enough for me to deal with regular death marches to help someone meet their OKRs for that quarter. I've happily worked until 3 AM a bunch of nights in a row on something that was important, but I've also busted my ass for things that could have been delivered later or not at all and it wouldn't have really mattered, and those ones are a real punch in the gut.
Regarding that, there was an excellent business editorial in a recent Economist issue that wrote on that exact topic: "Company or cult?" [1]
SWE is a high paying profession and rightly so because companies get to make millions off our backs.
His LinkedIn also says he joined Airbnb in 2016 which means his stock is worth multiple millions since IPO.
Perhaps, the contractors had a better gig? At least they might have felt less pressure to please the corporate ethos, and they were hopefully paid hourly overtime during the silly death marches.
This stuff is sickening and toxic.
Wow, incredible, and insulting.
I can't imagine getting played out by Bill Withers.
When I started, I didn’t even have a manager for a few months. I actually burned out within my first 3 months there, and my Director personally helped me navigate the leave process —- I wound up taking a 3 month fully paid leave (they topped the difference between what the STD insurance they provided me paid and my full salary). When I returned I had a great manager!
I worked with a lot of contractors too, but my department converted well over half of the ones I worked with, and eventually the others churned out until they hired people full time. Mostly we started with contractors because it was easier to hire them but very difficult to get headcount (we sure did try).
Anyway it was a pretty wild ride but I wouldn’t trade it for the world. Things were definitely uneven though. One thing that really made me sad was when they replaced the food team who we all loved with contractors (who we also all loved). After I left they really screwed over the Portland office too. But it wasn’t all bad and I cherish the friends I made there.
Was it infra?
At the end of the day, you have to prioritise your own well being.
As one anecdote goes:
Patient says that he recently made it up with his mother.
Psychiatrist ask what happened.
"She died" answers patient.
And we all know a lot of those families who meet once a year because of the need. And companies then want to call themselves "families".
It is sometimes just too hard to wrap your head around this. How what is basically a website requires such a workforce? I get that it is much more than a website, there are various aspects of platform and etc. I understand that my comment might seem off. However 7000 is really a lot people.
Hey now what’s wrong with being in the East Bay?
"I could have left Airbnb before things got so bad. But despite all that I observed and experienced, I truly loved my job."
If I love a job, I hesitate to quit just because some of the management is terrible. As a point of reference, many people on Hacker News have read my book "How To Destroy A Tech Startup In Three Easy Steps":
https://www.amazon.com/Destroy-Tech-Startup-Easy-Steps/dp/09...
If you go read the reviews on that book, one of the most common sentiments is "Lawrence should have left that job much earlier than he did." And yet, I really loved the work and I had a lot of fun, in many ways. Maybe I didn't emphasize how much fun we had along the way, but I think, getting to work on great tech while being well paid is a relatively rare gift to an engineer, so I don't think many of us really want to walk away from a job too soon. I do understand why an engineer might stick with a place like AirBnB, even if the burden is heavy.
How insulated from the rest of society in the US do you have to be to find that shocking?
How can this person even say this when they don't touch any financial data? A quick look at Q4 2020 results for Airbnb shows a $1B loss on net income ex. IPO costs and a $21M loss on the financially engineered/hacked "adjusted EBITDA". An unprofitable company is not in a position to be keeping jobs for the sake of it.
> These material conditions bled into work-life - while some of us took Ubers to work and shopped at Barney’s, others maxed out credit cards or could only afford to live in the East Bay
Oh no, customer support can only afford to live in the East Bay. This person needs to get a grip. A customer service agent is not making 200k+ in any world. That is a recipe for running a failed business. You know what does let people live where they want? Building more housing.
> a clearer non-product career ladder
There is no "ladder" to being a customer service agent. Experience doesn't scale your value to the company, so there's no reason for there to be a ladder. And with the advent of gig platforms there's no reason for there to be a manager either. Saying that customer service agents need a career ladder shows how delusional this person is with respect to running a business.
This person needs to realize that life is about working for yourself, never for the "Airfam". Loyalty means nothing. If they're burned out (it sounds like they are) then they can leave with their multi-million dollar stock options and free up a job for the rest of us who would gladly get paid half a million dollars a year to complain about "inequities". Corporate won't care they left and they shouldn't feel bad about it either. Sometimes some people just aren't cut out to keep going hard day in and day out for 5+ years. And that's okay, because if you worked at Airbnb then you can easily get a cushy job somewhere else.
Starting looking for a job doing manual labour. Working with a computer no longer an option. Had 2 engineering degrees: electronics & embedded.
Can relate, but the career advancement prospects in software-unrelated fields are seemingly non-existent and employers are increasingly exploitative (e.g. CP Rail). Seems you have to start your own company to get anywhere or you're just spinning your wheels for the rest of your working life.
What? It absolutely does. As a dev the more senior customer support people are often the first people I think of when trying to solve complex business logic related issues in legacy code. Also, customer support are sitting between clients and dev, and the more problems they can solve without passing along the chain the more time you save. There's a tonne of value in experience in that role.
One of my friends was on the food team. She was an amazing musician and won our talent show. She wound up transitioning to work on music partnerships until the pandemic hit.
Okay, but only if you promise to write a similar essay after you yourself are burned out by the company, for the edification of the public.
Yeah, this is wrong. I have a good friend who developed his understanding of the customer in that role, and leveraged it to become, gradually, a director. He was good, and he was recognized, and he was promoted.
I am so glad to see people speak out about their experience, especially at companies which claim to uphold a certain set of values. Such as Amazon or Airbnb.
I recall at Twilio, I was emailed by an HR person ... from the email account of a Director of Engineering. An HR person impersonated a Director of Engineering in order to recruit and have a better chance of getting the attention of software engineers, to attempt to persuade those engineers to join their team.
Yet, one of Twilio's principles is/was "Transparency". Yet, there they were-- their HR people engaging in practices which are deceptive.
We must hold companies to their supposed principles, and to a reasonable expectation of professional ethics in general. \
Bravo, I say, to the author of this article.