I'm currently a swe in AWS on a pretty impactful team with good WLB and pay. However, I'm not a huge fan of the way we do things at work. 99% of the code reviews is just making sure the business logic is correct with not much regards to performance, organization, or even maintainability. Documentation is a myth. If it works, ship it.
Prior to college, I didn't know this is how most cloud teams operate (or correct me if I'm wrong). On top of that, my team is just always focused on work and nothing else. Not many team events or overall team culture. Although this could just be the millennial / fresh grad side of me complaining.
Overall, I don't think I'm learning much here. Nearly all my CRs get approval without much in-depth analysis (I've purposefully submitted non-performant code to see if my co-workers will catch it and sometimes they don't).
My question is, is this common? I just passed the 1 YoE mark and if I start looking for new jobs, do I still count as a new grad?
YoE: just over 1
- Genesys / Creative washtubmoreDon’t even think of looking until you’ve been there for 2 years. After 2 years, you can start looking.
- Genesys / Creative washtubmoreLess than 2 years is a bad look. 2 years goes by fast. Less than 2 years at a job looks bad on your resume. Unless you can get a GLOWING recommendation from your current manager—stay put for 2 years. Build some cool shit on the side, do your own “learning” and move on once you hit that 2 year mark. Your nice WLB will take a hit on a new job, so there’s that, lol. Good WLB is rare in this industry.
- Oracle UhuM34It is quite common. What you are lacking and what you desire is a team that is excited about work, and excited about their coworkers. It is a great experience. Not going to find it with teams that have been together for awhile. Go out and find a new team, new development or support of a new product, with a mix of experience, many your age group. I'm 30 years in. I had that experience many times. Something every newbie needs. 1 year in it does not hurt to look and knock on doors. Don't make it a rush and see where it takes you. It will keep your interview skills honed at a minimum.
- If it bothers you, consider working at Google. You will likely face the opposite "problem" here.
- At AWS the focus is on OPs, they got it pretty much figured out. You should learn to appreciate that mindset even if you don't like it. IMO this is what makes AWS successful.
- Yes they figured out how to quickly absorb fresh meat into the system to run the cloud. There are opportunities to learn new things at AWS, but again there's a lot of competition who want the same thing you do. Get a mentor and switch team, but first you have to do well where you are right now.