3 ms·
I was an early employee. Lots and lots is said about compensation, I won't repeat it here. (Just treat equity like a tip.) One pro is that I got to set a lot
by gwbas1c 8y ago
I was an early employee.
Lots and lots is said about compensation, I won't repeat it here. (Just treat equity like a tip.)
One pro is that I got to set a lot of architectural direction. Because we were small, I didn't need to put up with a lot of groupthink or bad habits when fixing some very bad problems in the codebase.
Another pro is that I had some of the best working relationships in my life while we were small.
A con is that startups are crawling with bozo managers and people who just can't handle the responsibility that their role entails. I used to spend a lot of time pushing back on people throwing unreasonable amounts of their work onto me.
(QA who wouldn't follow process and wrote incomprehensible tickets; and support people who just wrote "it doesn't work" instead of diagnosing the customer's problem.)
Ultimately, as the company matured, the above problems worked themselves out. I helped define the processes for QA and support. Defining these processes is a big pro, IMO, of working for a startup.
Also: Incompetent people manifest themselves in startups just like in large corporations; it's just that large corporations tend to absorb them better. Startups die quickly if they can't push the incompetent people out.