Please mention the number of people in the startup, as it experiences probably vastly differ based on size

20 points

20-30 people (was there a few years with ebbs and flows). We had long hours and the first few years it was exciting. We built a lot of stuff and didn’t know about certain practices - especially DevOps, so when we got one, there was a lot of work to do.

For me, it taught me autonomy. You had to learn to own something and be able to educate others on how it worked to raise the bus factor above 1, optimally above 3 (it’s a start up after all).

Startups are often founded with the goal of being bought. Depending on where you work, they might care about code quality, testing, design, and all those nice things, but being first to market is probably the biggest concern. We had to strike a balance between being very agile and being able to deliver quality, maintainable features. Code was a vessel, an enabler, a necessity.

You had to hit the ground running when you arrived and be ready to learn a lot on the job. A prototype really meant something thrown together quickly that worked for a limited amount of usecases with fake data. Investors and customers had to be able to see the value first before wanting the real thing.

Ultimately, getting bought by a larger company made me leave. Things quickly changed from quirky, fun, stressful yet rewarding to procedure and corporate. Decisions weren’t made by devs anymore but had to go through a horde of people. Teams were made around individual products instead of people being able to move freely between them to understand the vision of the company.

In retrospect, it was a nice stage in my life and I definitely learned a lot. If you haven’t done it before, I’d recommend it if:

  • you can deal with pressure
  • like throwing stuff together or being on the other end of making a prototype viable
  • want to start a business yourself someday (going through the phases of a startup teaches you about that)
  • like being able to have a vision of the entire company (products, customers, fellow employees, …)
  • want to be at the forefront of something possibly new

Like any job, you can try it out for a few months and see whether you like it. If you don’t do not force yourself to hang around. Your salary might not raise as fast regardless of how fast the startup is moving.

Good luck!

P.S This is but one experience from one country in Europe!

Anti Commercial-AI license

permalink
report
reply
1 point

Offtopic, but I was not aware that licence CC BY-NC-SA 4.0 prevents commercial AI to use your content. It’s a good idea to use it for this purpose

permalink
report
parent
reply
8 points

And if you think that disclaimer actually means anything here I got some oceanfront property in Arizona for you…

permalink
report
parent
reply
3 points

It’s not a disclaimer, it’s a legal agreement for use of copyrighted work. It’s entirely on the author to enforce it and it will be expensive to attempt enforcement and the courts may not agree that it is enforceable or subject to copyright at all.

So, yeah…

permalink
report
parent
reply
3 points

I’m not a lawyer, but I just figured that if commercial AI is getting in trouble for using copyrighted works, that using a license which prohibits commercial use while allowing other uses should have the same effect. Whether AI can legally consume copyrighted works is being tested in the court of law, so adding this to my comments is a “just in case” measure.

Anti Commercial-AI license

permalink
report
parent
reply
3 points

Thank you for the detailed comment!

permalink
report
parent
reply
7 points

Don’t do it. Can wholeheartedly say fuck startups, especially if you’re not an expert in your field.

YMMV but they’ve been an extreme version of the horrible crap that goes on in corpos; ex layoffs because why keep your senior devs when someone newer is much cheaper and the company only has a few millions untill next round of funding.

permalink
report
reply
4 points

Recently left an organization that was failing to shed the “start up mentality.” I joined at just over 100 people when two years before they had about 40. They were over 400 five years later.

They had a lot of growing pains with regard to communication. They also were a very top heavy org because all of the original employees were promoted to directors with no management experience. People spoke often about being the xth person hired. In all hands meetings.

Honestly, I’ll be avoiding them like the plague now. I worked my 40 hours a week while begging to expand the department. Left when I was put on probation for not getting enough work done. Also never accept an unlimited pto agreement. Good way to never take vacation.

permalink
report
reply
2 points

I’ve always worked at startups, probably a dozen in total so far. I was usually the only technical person in the company (or one of very few), with typically less than 10-20 employees total. Was always paid well and enjoyed what I did, but I understand that might not be typical. Usually the company would eventually get sold off or just go out of business and then I would move on to something else.

When one of the companies got bought out and surged from ~20 to 100+ employees, it wasn’t long before I and most others slowly left one after another because the new owners didn’t know anything about technology and ran everything into the ground, blowing through ~100 million dollars with nothing to show for it (we did more previously with 5 million than they ever did with 100).

permalink
report
reply
2 points
*

Also in Europe, but I’ve worked at 3 different startups before becoming a contractor earlier this year.

  • First one I worked for 5,5 years, joined at ~30 people and saw things grow to 180 people at which point the company was sold and I left about a year after that.
  • Second one I worked for 7 years, was one of the first employees and responsible for building their frontend stack as well as various microservices from the ground up. Company grew to about 80 people, but I left after Covid layoffs. I wasn’t one of the layoffs, but culture went to shit quickly after that.
  • Third I was also one of the first people and helped build a pretty exciting architecture from scratch. Stayed for 3,5 years, but unfortunately the company never found market fit during that time and the team never grew beyond ~20 people.

Overall I can say:

  • If you value autonomy and you have a getting-things-done mentality this is the right gig for you.
  • Culture differs very much per workplace, you may need to be lucky. (I don’t think that’s unique to startups though.)
  • You need to be assertive and pro-active.
  • Don’t do it for the money. Startups usually pay less, but in theory make up for it by offering equity. But most startups fail, so in most cases this will never be more than theory. Even if you do get an exit, chances are the payout is less than you would’ve earned working those years for a bigger corporation.
  • The experience can be extremely rewarding because you can easily reach a position of influence.
  • You will learn a lot.
  • The experience can be frustrating because there is always pressure and a lot to do and you rarely have the means to do it all.
  • You will need to improvise a lot.
  • If you pull it off and your startup becomes successful the thrill is exhilarating.
permalink
report
reply

CSCareerQuestions

!cs_career_questions@programming.dev

Create post

A community to ask questions about the tech industry!

Rules/Guidelines

  • Follow the programming.dev site rules
  • Please only post questions here, not articles to avoid the discussion being about the article instead of the question

Related Communities

Credits

Icon base by Skoll under CC BY 3.0 with modifications to add a gradient

Community stats

  • 59

    Monthly active users

  • 32

    Posts

  • 201

    Comments