DEV Community

Cover image for Transitioning your Career to AWS and DevOps
Saloni Singh
Saloni Singh

Posted on

Transitioning your Career to AWS and DevOps

Nowadays, all of us are looking to transition our career in a more better way, probably Cloud or DevOps, as the demand is increasing in the market for these roles.

So, this post is all about some steps that I would recommend you to follow, I’m sharing my personal experience and the steps I followed, it may differ from person to person, so please do the same according to your pace and interest.

Image description

  1. Try to focus step by step on the services, don’t try to rush

  2. First, if possible, cover AWS (or any other cloud of your choice) completely, only then move to DevOps

  3. If you choose to go for AWS Developer roles, make sure you are really good with programming, and if you are going for Devops role, minimal programming is desired, but it is necessity, as there are many organisations, that expect you to code in interviews.

  4. Programming language can be any of your choice, preferably Python or Golang if you think of moving towards DevOps.

  5. Make sure, the services that you mention before the interviewer, you are really really good at them, please avoid bluffing about the services that you have very basic knowledge on, and if asked then you would be blank, as that creates an impression of not having enough knowledge.

  6. Try connecting with DevOps people and asked about their real projects, how they work and what all they cover.

  7. Avoid mentioning some common projects, like I have noticed in the interviews that I take, the candidate says, I have worked on an e-commerce website, or a retailing platform which is three tier application, I have created VPC, I created EC2, please note that real world projects aren’t this way. Try to state that we have managed the infra using IaC.

  8. Focus on IaC tools, preferably Terraform would be great.

  9. Be well prepared for the project you will be explaining, as that will be the one which interviewers would focus more on, so in and out you need to know everything about your project.

  10. Mention working on tools like JIRA, ServiceNow, or any ticketing tools, preferably JIRA would be good one, and tell that you have also worked on stories and epics, this frames an impression of real hands-on.

  11. Be consistent regarding your hands-on practice, avoid mugging up internet questions and answers, as nowadays the interviewer asks questions related to your project and some scenario based ones, so your practice is the key to your success.

  12. Regarding DevOps, try to avoid covering each and every tool, if you just focus on Git, Docker and Kubernetes it’s more than enough.

  13. At least one monitoring tool should be known, Datadog, Prometheus, Grafana or ELK, select any of your choice.

  14. Watch Udemy lectures if possible, for AWS watch Stephane Maarek’s course on Solutions Architect Associate.

  15. Regarding certifications, having one is good, but not necessary, at the end all that matters is your knowledge.

  16. For better insights on AWS and Kubernetes, I would recommend watching Cloud With Raj on Youtube, Raj is a Principle Solution Architect at AWS, the way he presents the things before you are good, also watch some of the system design cases as they are also the one’s that need focus.

For more help connect with me on LinkedIn: https://www.linkedin.com/in/saloni-singh-aws/

Top comments (0)