I'm currently in the interview process for a Systems Development Engineer (SysDE) position at AWS, specifically working on building a new region. My background includes experience with AWS, Kubernetes, Python, and Shell scripting. While I appreciate the learning opportunities in my current role, the salary isn't very competitive. My aim is to boost my earnings while also having avenues for professional development, particularly in DevOps. However, the job description for the SysDE role seems a bit vague, only mentioning Linux and some programming tasks. I'd like to hear from anyone who has been a SysDE at AWS: what is the actual tech stack you work with? How much development work is involved? I'm a bit hesitant to shift to a role that seems predominantly focused on Linux administration if that's the case, even with the attractive pay package.
3 Answers
I've heard mixed reviews about working at AWS. It definitely looks impressive on a resume, but I've spoken to several people who found the work environment challenging. The key is to ensure that you're getting as much experience as you're giving; don't let them drain your energy without gaining valuable skills.
The experience can vary a lot depending on the team you join. Some teams are fantastic, while others are a bit of a nightmare. The good news is that it's quite straightforward to switch teams if you find yourself in a not-so-great situation. The specific work often depends on what you're supporting; it could be more focused on coding and developing processes, or it might lean heavily into sysadmin responsibilities. Also, the tech stack leans towards proprietary tools with a bit of CloudFormation.
I was in a role similar to SysDE, working on building AWS regions. Be wary, as it often turns into just a support role with expectations for on-call work. If you land in a product team that actually builds and innovates AWS services, you’ll likely have a much better experience. In my view, the job is a blend of systems engineering and software development, focused on long-term fixes rather than just putting out fires with automation.
You make a good point. I want to delve into more than just Linux system admin stuff. I’m worried about ending up stuck doing mundane tasks.