Hey everyone! I'm new to software engineering, having recently transitioned from a tiny research lab to my first real job at a startup. It's a contract role, and I've been tasked with adding a new feature to their existing product. However, I've hit a few roadblocks that have me questioning the norm in this industry.
First, even though I can test things locally, I don't have access to their codebase or database schema, which feels pretty limiting. I asked for access to AWS to get a better understanding of everything, but my request was denied. Instead, there's one engineer dedicated solely to deploying code on AWS, which seems odd to me. When I inquired about testing my work, I got the brush-off because they prioritize shipping quickly.
I've been asked to write documentation for my code, but it feels like I'm expected to fill in gaps that only the AWS engineer can address. There are no code reviews, no pull requests, and I'm working alone on my own GitHub repo. The CTO uses vague phrases that don't really help, and the CEO keeps changing the product direction.
This isn't my primary job, but I took it to gain real-world experience in Machine Learning Engineering since I'm aiming for that path. However, I'm feeling like I'm not learning much here. Is this common in startups? Should I stick with this or focus on my own projects? Also, how do I showcase AWS experience on my resume if I can't get any through this role?
2 Answers
I've heard experiences like yours are more common than you'd think, especially in some startups where management relies on buzzwords more than actual practices. It sounds like they might be protecting their codebase like it’s a trade secret, which can really hinder your learning. In general, if you're not getting the growth you hoped for, it might be worth considering other options. Sometimes, the best learning comes from your own projects, especially if this role is more about rushing out features than quality development.
And if you decide to dive into open source, you'll get real-world experience while contributing to something valuable. Totally worth considering!
I totally get where you're coming from! It seems like you have a lot of valid concerns. As for AWS experience, maybe look into side projects or online courses that let you work with it directly? That way, you can build something interesting for your resume even if this job isn’t giving you what you need.
Agreed! Hands-on experience, even through personal projects, will definitely stand out. Plus, there are plenty of free resources online to boost your understanding.
Absolutely! Taking charge of your learning path is key. Use this as a stepping stone, but don’t be afraid to carve out your own projects.
Exactly! If you're not getting any substantial experience, it might be time to pivot. Just remember, a meaningful project speaks volumes more than a sketchy gig.