Somehow I’ve never worked for “fresh” startups. Alway worked for startups that had at least 4 years of life (they qualify as startups at that stage? I guess so)

Somehow I’ve never worked for “fresh” startups. Alway worked for startups that had at least 4 years of life (they qualify as startups at that stage? I guess so). It’s been great: - Never had to do extra hours. 9-5 only - Plenty of room to “bring your own idea”. At this stage, startups have a tiny bit of organizational structure in the tech department, not enough to keep your tech idea out of the table. There’s usually no “architecture team” nor “secops team”, so everything moves faster - Plenty of room to make mistakes as well. Not much is rigid, so you can screw up things. That’s always good because if you screw up something then you are probably going to be the one fixing the underlying process that lead you to make that mistake. Your colleagues appreciate that - Code base is not very old (so, you can still ask around the original writers), nor it’s that big. So, either a small monolith or just a few microservices - And plenty of room to learn. Perhaps you are interested in architectural topics… maybe you even end up as the “architecture guy”. If you stick with the company you may even fill that new role they just opened “Head of architecture “