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

CSCareerQuestions

2455 readers
1 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
[–] onlinepersona@programming.dev 8 points 1 week ago

Generally, I have enjoyed smaller companies because it's easier to meet people and get to know them. When problems arise, you have a direct connection to whoever you need to talk to. The downside is that you need to do a lot of stuff yourself if you are the one pointing out the issue. It can get rewarded, but that depends on the company.

Startups are usually fast-paced and always hunting for more money and more desperate than large companies.

They were a good experience to learn from and they taught me what to focus on and when to let things go. There just isn't enough time to do things "the right way". In large companies it's much easier to bullshit your way into writing proper code (triple estimates, start a corporate sounding initiative, pretend to held up by other teams, use bullshit lingo to make thing sound complicated, make small promises deliver more, etc.)