Should I Choose an AWS Support Engineer Role or a Cloud Engineer Role for Long-Term Success?

Starting in support at AWS is pretty common for new graduates, and many use it as a stepping stone to more hands-on roles. You'll certainly learn a lot about AWS and be directly involved with service teams, which can be invaluable. However, if you're itching to build and create, the Cloud Engineer role may suit you better to keep your technical skills sharp for future opportunities. It's worth noting that there's no stigma in tech support; many successful people started there. The skills you'll develop are definitely applicable in other fields, especially since support roles are customer-facing, which not all engineering roles are.

If you choose the AWS support route, definitely look for a Technical Field Community (TFC) opportunity to gain extra experience. Both paths have their merits; AWS support helps with professional growth in processes and standards, while consulting could offer you diverse project exposure. You might want to consider what your end goal is. If you're eyeing a switch to a Service Team within AWS, starting there gives you a boost, but you’ll need to act on it.

I started out as a Support Engineer at AWS and later transitioned to a Cloud Engineer role. The support position boosted my knowledge about AWS's core functionality and troubleshooting. However, I felt limited since I wasn't managing resources myself. Still, working closely with service teams helped me build valuable relationships for internal transitions later on. If you're keen on building systems, the Cloud Engineer position is a solid opportunity for hands-on experience with IaC and Kubernetes, which are major assets on your resume.

Regardless of the role, the outcomes will largely reflect your initiative in the position. The AWS Support role can provide deep exposure to real-world problems and large systems failures, which is hard to replicate elsewhere. If you plan to keep building on the side or seek internal opportunities quickly, you can leverage your Support Engineer experience well. If maintaining hands-on skills is crucial, the Cloud Engineer role is the better choice. But remember, proactive behavior in support can lead to great internal gains!

I think if you can present your AWS experience well on your resume, you'll avoid any negative perceptions from potential employers. Just be aware that you might lose touch with your technical skills in infrastructure managing if you don't use them much, so side projects could help. Additionally, being at AWS for 2-4 years can provide you with great learning opportunities. But if the Cloud Engineer role excites you more, consider going with that; job satisfaction is important! Just know that AWS Support offers a valuable learning experience, albeit without the DevOps exposure.