2,656 karma · joined August 3, 2010
Always searching for great Go engineers: https://getstream.io/team/
Open source projects: https://github.com/tschellenbach Contact: thierryschellenbach at google's email service Twitter: https://twitter.com/tschellenbach
It's good to see leaderships take responsibility and change course in the best possible way. But the whole this is our fault, we should have seen this coming story is a bit nonsense. They are just being nice about the messy situation and taking responsibility even though its outside their control.
Many tech companies are down 80-95%. So if you used to pay employees 100 to generate 100, now you are paying 100 to generate 20 or in some cases 5. This only works if you can massively increase productivity or reduce cost.
There is no evil conspiracy, markets are just down
Go has been great at Stream. We are hiring atm. No go experience required and various levels of seniority.
Historically Stream has grown rapidly and the equity grants have been very significant compared to the base salaries. (who knows what the future brings, but hopefully that trend continues).
So a significant part of our team's compensation is equity, I think it's only fair to be transparent about those topics. Also important to share the last round valuation and the revenue, since many startups that raised at too high prices are currently deeply underwater on their employee's equity.
We do lunch and learns on equity, evaluating startups etc. That is important since most people don't have prior experience with evaluating startups.
A friend of mine didn't exercise his stock options when he was early stage at a company that had an exit above 1B. I think that shows how hard it is to evaluate how startups are doing. But sharing the data is a good starting point.
It seems more probable that this security leader failed to get buy in from the engineering teams, or that there was some technical debt that he couldn't get past.
I think many founders give up too early. You wont learn if you don't go through some difficult experiences.
Personally I believe in remote and that it will get even better as tech to facilitate it improves.
I don't believe in working 4 days for engineering specifically. The field changes rapidly, there is a large learning curve and it takes a lot of hours to really master it. There is also some fixed overhead in communicating with other departments which stays the same even if you work less hours. So you remove more than 20% of your productive hours with this approach. You also reduce the time you spend learning. This further hampers your productivity. I think it will be a niche thing only done by some startups that care about this, have no other way to attract talent and aren't very ambitious.
That being said, for some people it will work well. It's pretty common for some roles in the netherlands for instance.
I do think that as productivity and tools improve around remote and async work salaries in remote friendly jobs will equalize.