Live data from Hacker News

I Don’t Care How Well You Code, Understand Your Compensation

hackernoon.com

11–20 of 328 posts

Re: I Don’t Care How Well You Code, Understand Your Compensation

#11
post #8
post #2

I don't understand most of the financial terms used in this article. Where do I start?

The basic thing to understand is the concept of "dilution". Companies can issue new stock in exchange for new investment funding, driving down the value of existing stock. Sizable dilution is rare in publicly held companies, but common in privately held ones. There are often contractual terms which protect some parties against dilution. Founders and early stage investors may be protected, while other employees are no…

I think its rare to have any anti dilution protection for anyone in a high growth company.

At most you have then option to buy into further rounds, so you keep your percentage the same.

Re: I Don’t Care How Well You Code, Understand Your Compensation

#12

> So talk to the CFO about the numbers — when you’re hired, when it’s fundraising time, and any time in between. Hahahaha, oh man so here's the part where I just dump all my emails about the answers I have gotten back from CFOs over the last decade: - "common stock shareholders aren't privy to financial details" - "we don't share that information" - "I discussed it with the board [consisting of myself] and they decid…

One time I had the privilege of getting the CEO's assistant to read me over the phone a prepared high level summary of company financials. She read very quickly and refused to pause or repeat anything.

Re: I Don’t Care How Well You Code, Understand Your Compensation

#13
post #2

I don't understand most of the financial terms used in this article. Where do I start?

I hope the following is helpful rather than confusing - feel free to ask any clarifying questions. Also, I will preface this with the fact that I am an engineer and not a finance person. I may be subtly wrong on some points and I am happy to be corrected by those with more knowledge on these topics.

Liquidity preferences - Also described in the article as "investors escape safely on Preference stacks", investors usually have terms which state that when the company is sold, they get paid first so that they can at least recoup their investment before anyone else gets paid. Usually they get paid again with everyone else, resulting in a "double dip" into the sale proceeds.

Reverse-merger IPO - this is a rare (for tech companies) deal structure where private company A merges with public company B. The resulting merged company is now publicly listed because company B has already gone through the IPO process.

Dilution - described in the article as "over-dilution" and "dilutive financing", if there are X shares of a company and you own Y shares, then you own Y/X % of the company. If the company then creates Z shares to sell to investors, you own Y/(X + Z) % of the company. The difference between these percentages is dilution. Often, existing investors have anti-dilution provisions. They are able to buy additional shares in the round up to their existing percentage. Founders and employees usually have no such luck.

Ratchet in a down round - Admittedly, I don't know what a ratchet is. I would guess that it is a protection of some sort for investors from a down round and thus bad for founders and employees.

Non-liquid - (nearly) impossible to sell

Highly volatile - a plot of price over time looks like a rollercoaster

Anti-dilution provision - see the latter part of "dilution" above

IPO protections - Also have no idea what these could be. I would guess at something to protect investors who invest at a high valuation where the public valuation is lower.

409-A pricing - How the shares are assigned a value for tax purposes

Re: I Don’t Care How Well You Code, Understand Your Compensation

#14

It's really quite simple: you assume it's all worthless, because that's how it starts and that's how it generally ends. Even if it were going to be worth something, you'd have been better off taking the money up front and investing it however you wanted in the meantime. But it doesn't really matter, because you have no control over this anyway. All you have to do is decide whether the salary is high enough; the rest…

> All you have to do is decide whether the salary is high enough; the rest is irrelevant.

You mean feign interest in the company for two years longer than every VC that passed them over?

I'm being cynical, but I am baffled how Silicon Valley companies think they are going to be privileged enough to hire engineers that are actually interested in their company's ambiguous mission, amongst the subset of engineers randomly on the market at any given time

How many VCs weren't interested again?

Re: I Don’t Care How Well You Code, Understand Your Compensation

#16

It's really quite simple: you assume it's all worthless, because that's how it starts and that's how it generally ends. Even if it were going to be worth something, you'd have been better off taking the money up front and investing it however you wanted in the meantime. But it doesn't really matter, because you have no control over this anyway. All you have to do is decide whether the salary is high enough; the rest…

This is really wrong.

You can very well assume that it's worthless. If you do, chances are you will not do your research on things like early exercise and 83(b) filing (whether, for example, you work at a company that even allows things like that).

Then, in the very small chance that your equity is actually worth something, you will be kicking yourself really hard because if you'd only prepared, you could've been paying LTCG on the whole spread, rather than dealing with AMT and trying to find a private buyer for your illiquid stock to pay off the IRS and the CA FTB.

Re: I Don’t Care How Well You Code, Understand Your Compensation

#17

> So talk to the CFO about the numbers — when you’re hired, when it’s fundraising time, and any time in between. Hahahaha, oh man so here's the part where I just dump all my emails about the answers I have gotten back from CFOs over the last decade: - "common stock shareholders aren't privy to financial details" - "we don't share that information" - "I discussed it with the board [consisting of myself] and they decid…

[deleted]

Re: I Don’t Care How Well You Code, Understand Your Compensation

#18

It's really quite simple: you assume it's all worthless, because that's how it starts and that's how it generally ends. Even if it were going to be worth something, you'd have been better off taking the money up front and investing it however you wanted in the meantime. But it doesn't really matter, because you have no control over this anyway. All you have to do is decide whether the salary is high enough; the rest…

This is really wrong. You can very well assume that it's worthless. If you do, chances are you will not do your research on things like early exercise and 83(b) filing (whether, for example, you work at a company that even allows things like that). Then, in the very small chance that your equity is actually worth something, you will be kicking yourself really hard because if you'd only prepared, you could've been pay…

That all sounds like a fancy way of saying "playing the lottery".

Re: I Don’t Care How Well You Code, Understand Your Compensation

#19
post #13
post #2

I don't understand most of the financial terms used in this article. Where do I start?

I hope the following is helpful rather than confusing - feel free to ask any clarifying questions. Also, I will preface this with the fact that I am an engineer and not a finance person. I may be subtly wrong on some points and I am happy to be corrected by those with more knowledge on these topics. Liquidity preferences - Also described in the article as "investors escape safely on Preference stacks", investors usua…

Thank you. The jargon seems to be the biggest stumbling block here, the concepts make sense. If there is a "Finance for Hackers" out there I would love to read it.

Re: I Don’t Care How Well You Code, Understand Your Compensation

#20
So, I've been working for startups for a long time. Finally I've reached two "rules"- - Be a founder - Restricted Stock Units or Preferred Shares are the only way to go.

Options are way slanted against employees. If you have a market value of $150k and you take $80k in salary, you're giving up $70k of real money each year. The value of your options in most situations that work out well (Eg: base hits) are going to be less than that (when accounting for risk).

If you get fired in the 11th month, you've lost about $70k and get nothing.

IF you get fired in the 13th month, you have 1 year and one month vested, and 90 days (most likely) to spend real money to turn those options -- which you've already paid for by giving up market salary-- into something valuable.

Options are basically a raw deal, and I'm not even getting into liquidation preferences.

IF you give up real salary of $70k a year, that is the same, literally, as the angel who puts $70k into your A round.

You should be getting the same terms as the A round in that case.

That you don't is part of how the game is rigged. You should vest almost from the beginning.

I think 90 days of trial period with a cliff (Eg: you vest 90 days on your 91st day then every 30 days after that you vest another 30 days) is ok. You don't want the cap table to be too complex.

Yes, Venture Capitalists wouldn't like this. Of course, because it's fair rather than tilted towards them.

I know this won't become popular because engineers are too easy to manipulate. They read some self serving VC blog about why liquidation preferences are perfectly acceptable and they buy it.

But if you're there the year before the VC you took a lot more risk than they did. You're investing your real salary that you're not getting and could be getting by working for a fully developed company, while they are investing other people's money.

I've heard of programs called Slicing Pie and the like that make this easy.

Why you want to be a founder?

Well, after over 20 years working for startups, I have spent al to of time asking CEOs and CFOs specific pointed financial questions. I have gotten the runaround from them, and that's a flag that makes it easy to pass on the company. But when I haven't gotten the run around, way too often what they have told me was false.

Many times the CFO when asked for the number of authorized shares or the total shares on a fully diluted basis would give me some BS number. I don't know if he didn't actually know. (Many times the startup doesn't even have a CFO at that point.)

Many times I've been told that options accelerate, on acquisition, only to find out that the founders deal was that way but they wrote a new option plan for later employees that didn't have as nice of terms.

Just recently I saw a plan that gave the "compensation committee" the ability to do anything they wanted including cancelling all outstanding options grants, in the event of an acquisition.

I really don't know who wrote that document but I think it was one of the investors, and the "executive management" of the company never actually read it. They didn't believe it said that when I pointed it out. (Who am I, I'm just an engineer (this time, been a founder in the past, but I thought this company had reduced a lot of risk and so the tradeoff was worth it.)

So, another piece of advice- work for a company where the founders are hard asses when it comes to investment and terms. These people didn't even read the stock option plan (and weren't going to give it to me, despite requiring all of us employees to sign an agreement agreeing to its terms, because our CFO didn't realize that there was a separate plan document- he kept saying (or thought) that the agreements were the plan!)

This kind of lack of attention to detail is very common, in my experience in startups.

Working for a startup that fails is pretty lame, but working for a startup that succeeds and you get screwed out of the upside is much, much worse.

Post reply on HN