I've been a Systems Engineer for about a year and I also contribute actively to open-source projects like Prometheus. Recently, I've received a job offer from AWS for a Cloud Support Engineer position focusing on Linux. My plan is to use this role as a stepping stone towards a Systems Engineering position at AWS. I checked with my recruiter about the possibility of transitioning internally, and he assured me that it wouldn't be an issue, especially since the organization is new and there's a chance to help with automation tasks. I'm really tempted as working at AWS has always been a dream of mine, but I'm concerned about what happens if I can't transition into Systems Engineering internally. How hard would it be to shift back to an infrastructure-focused role externally after spending time as a Cloud Support Engineer? I plan to continue my open-source work and build internal visibility as I go. Any honest insights would be greatly appreciated.
3 Answers
If you've got bills to pay, taking the job could be a safe move. But it sounds like you're more attracted to the potential of getting into Systems Engineering at AWS, which is exciting! Just remember, it's about the opportunity and growth, not just the paycheck. Sounds like you've thought this through!
They might say internal mobility is easy, but be cautious. Those Systems Engineering positions tend to be competitive, especially right now. Even if that doesn't pan out, your skills and experience should still keep your career on a solid path. Don't stress too much!
Landing a CSE role at AWS could really boost your resume. If the internal transfer to Systems Engineering doesn’t pan out, getting a Kubernetes certification could help you pivot into a sys engineering or platform role elsewhere. It's a smart career move overall!
You're right about the paycheck not being the only factor! I think the experience and exposure you gain there might outweigh any initial concerns you have.