There is so little information written about equity for tech employees, and even less by software engineers who benefitted from it.
Uber and Square engineer @mcdickenson wrote the book Equity Compensation for Tech Employees, which fills this gap.
Here's the table of contents:
I reviewed the book before it was out, and it's a must-read if you are either based in the US or are/will be working for US-based companies issuing equity. Or if you want to know more on this important topic.
"Why are you looking to leave your current employer?" is a question I've asked hundreds of times when hiring at Uber. There are few things I've not heard.
Save for how Revolut treated engineers.
Here's how to build a culture where the hardest-working people voluntarily leave:
This was years back. I was doing the hiring manager interview. I ask the question and expect one of the common reasons - challenges, money, boredom etc.
"I'm pissed off, that's why. I put my heart and soul into this company, worked 80-hour weeks, and get slapped in the face."
Okay, this was new. "Can you give more details on what happened?"
"I didn't get a bonus."
"Well " - I think to myself - "that's not much to be pissed off about."
"So why did that tick you off?" - I ask. The person continues to explain this is not your usual bonus situation:
I dug deeper and the Amplitude founder is a legend.
They were the *first* company to introduce a 10-year post-termination exercise window. Their lawyers said they cannot be done. They did it, and open-sourced it, other companies following.
A 10-year post-termination exercise window means that an employee who joined in 2012, left 4 years later *still* made $10M, without having to exercise any options until now.
While there are many posts criticizing how difficult hiring processes are, especially for entry-level roles, it's only in private you hear interviewers and hiring managers talk about the other side.
Here's a short thread on a few observations that also explains some criticisms:
1. Entry-level applicants are on a very wide spread skillset-wise. They range from people who can only follow a tutorial to those who are hands-on with production-ready code. It skews towards the former though.
This is one reason there are so many automated closing assessments.
2. Resumes don't tell you much about entry-level people. Within the same bootcamp grads, there will be some strong candidates, and plenty of week ones. Same with colleges. It's impossible to predict how well a person will do on a coding exercise.
That first day as the Head of Engineering at a fast-growing startup is always glorious.
Not an engineering manager anymore, but a Head Of. The non-technical-at-all founder hired them because they *really* needed someone to get sort the eng problems.
A new story starts today:
The first week is done, and it's exciting. Well, a bit annoying as well. The founder keeps checking in, and talking about how they see this role, and what they want the EM (not Head of Eng) to do.
Problem is, much of it is not how the EM worked in the past, and it doesn't work.
Like the obsession the founder has with what are essentially micromanagement practices.
"This is how we work. High autonomy+high accountability is our culture". But then eng is told the work they should do, given deadlines with no input, and judged on "getting shit done".