A genuine question to those with VC or this kind of "spec ops coder" experience: is this kind of work worth it? I mean, yes, they are badass for putting in insane hours and foregoing everything else in life, but it seems a waste to spend this effort on a yet-another mess of an MVP held together with gum, twine, and duct tape.
I don't think hustle culture alone is enough if there are no results in personal growth, mission, or economic growth. One of these factors must be exceptional to justify the unbalanced life required to do well in this industry.
As a pure SWE, the code / systems that you work on are not at all as technically nuanced or challenging as what you'd get at a startup or big tech co. Your ability to go deep technically is sacrificed for an emphasis on speed and functionality. The focus required to do anything else is impossible in such a dynamic (volatile) environment.
As a more entrepreneurial engineer, you will get to grow horizontally (https://alexkondov.com/the-t-shaped-engineer). You'll drive product decisions, have more agency on direction, and get to interface with customers/users. You'll also have to get really good at saying "No" and stakeholder management.
On the mission side, a good amount of VCs claim to be making the world a better place somehow. I'm not convinced the secondary impact of money / company support they provide is moving the needle significantly here. You can have more mission alignment at a startup.
Financially, big tech is probably the best risk adjusted investment of your time. Startups have better outlier results, but are riskier. VC is somewhere in the middle if you get carry and the firm performs well.
This kind of work really favors work life integration. If work is your top priority, and you can put in absurd hours / shirk other responsibilities, this type of job might be for you.
>> what's the surprise? Sounds like a normal startup work.
The surprise is the asymmetrical expectations.
I would not expect a paycheck from the new company during the in-between-jobs vacation time (which I pre-arranged before accepting the new position).
I would expect them to think that such an "ask" is outrageous bordering on insane.
And then there is the normalization of wage-theft through manipulation.
To clarify my position: while this may represent a type of startup work that is very commonplace there is nothing at all normal about it -- it is just a clever form of stealing.
A genuine question to those with VC or this kind of "spec ops coder" experience: is this kind of work worth it? I mean, yes, they are badass for putting in insane hours and foregoing everything else in life, but it seems a waste to spend this effort on a yet-another mess of an MVP held together with gum, twine, and duct tape.
It depends what you want to get out of the role.
I don't think hustle culture alone is enough if there are no results in personal growth, mission, or economic growth. One of these factors must be exceptional to justify the unbalanced life required to do well in this industry.
As a pure SWE, the code / systems that you work on are not at all as technically nuanced or challenging as what you'd get at a startup or big tech co. Your ability to go deep technically is sacrificed for an emphasis on speed and functionality. The focus required to do anything else is impossible in such a dynamic (volatile) environment.
As a more entrepreneurial engineer, you will get to grow horizontally (https://alexkondov.com/the-t-shaped-engineer). You'll drive product decisions, have more agency on direction, and get to interface with customers/users. You'll also have to get really good at saying "No" and stakeholder management.
On the mission side, a good amount of VCs claim to be making the world a better place somehow. I'm not convinced the secondary impact of money / company support they provide is moving the needle significantly here. You can have more mission alignment at a startup.
Financially, big tech is probably the best risk adjusted investment of your time. Startups have better outlier results, but are riskier. VC is somewhere in the middle if you get carry and the firm performs well.
Sounds awful for anyone who values work-life balance and code that isn't poorly hacked together at the last minute.
This kind of work really favors work life integration. If work is your top priority, and you can put in absurd hours / shirk other responsibilities, this type of job might be for you.
So much drama for a work of week.
Everything is an odyssey these days.
"oh, they asked me to work before the agreement time", "they work during the weekend", what's the surprise? Sounds like a normal startup work.
VCs most of the time have no clue what they are doing but will behave as if they had built Meta or Google.
>> what's the surprise? Sounds like a normal startup work.
The surprise is the asymmetrical expectations.
I would not expect a paycheck from the new company during the in-between-jobs vacation time (which I pre-arranged before accepting the new position).
I would expect them to think that such an "ask" is outrageous bordering on insane.
And then there is the normalization of wage-theft through manipulation.
To clarify my position: while this may represent a type of startup work that is very commonplace there is nothing at all normal about it -- it is just a clever form of stealing.
It's far from correct but it's the normal behavior in this kind of environment. It sucks, the alternative is to not work for them