this post was submitted on 10 Aug 2026
16 points (100.0% liked)

CSCareerQuestions

2455 readers
2 users here now

A community to ask questions about the tech industry!

Rules/Guidelines

Related Communities

Credits

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

founded 3 years ago
MODERATORS
ericjmorey@programming.dev
odium@programming.dev
16
What is it like working for a startup? (sh.itjust.works)
submitted 1 week ago* (last edited 1 week ago) by abbadon420@sh.itjust.works to c/cs_career_questions@programming.dev
16 comments fedilink hide all child comments
 

I just had an interview with a startup, where I would be working as a junior fullstack engineer. However, the most senior person in the company (of 4 devs) has three years experience in software, and comes from an electrical engineering background. They work a lot with AI, but they are looking to bring more structure in the code. I am supposed to work with AI also and I get to work on all three applications that they have. I said I don't vibecode, I can use AI,but I need to know what I'm doing. They said I don't have to vibecode, but sometimes they need fast delivery.

This would be my first real job. I've been working as a tutor for 4 years, so I've seen a lot of simple code and greenfield code, and I've written texts and taught classes. So I have some valuabke experience. I was looking for a job in an enterprise company where I can learn from seniors, but this might also be a valuable way to learn a lot of stuff. It seems kind of rigity, but also flexible.

I'm wondering if anyone can share their experience working in a startup. Is it only chaos and misery, or is it also a good environment to learn a lot very fast?

Edit: they went with the other applicant :(

you are viewing a single comment's thread
view the rest of the comments
[–] jtrek@startrek.website 3 points 1 week ago

It varies.

I was employee #50 at a startup. Prior to my joining, they had a lot of incredibly poor practices. No release management. Few automated tests. Around when they hired me, that stuff turned around.

The CEO was kind of a controlling jerk, but was kept in check by the other founder. When that guy left, it got worse. The org also accrued layers of sycophants. The soft skills of knowing how to weasel your way into the CEOs favor paid off.

It's not really based on merit. It's all based on emotions. Building a cool thing can help, but that's not enough on its own. You could rewrite the code base so it's bug free and easy to expand, but if management doesn't know you or understand that, it won't matter. Meanwhile, the guy who's always at his desk making a lot of code shaped noise to management might get promoted.