Skip to content

Latest commit

 

History

History
109 lines (82 loc) · 7.94 KB

career.md

File metadata and controls

109 lines (82 loc) · 7.94 KB
Raw

What Do I Need For AWS Job?

There are three main groups of jobs related with AWS:

  1. DevOps Engineer
  2. Software/Cloud Engineer
  3. Software/Cloud Architect

Keep in mind, practice and experience are often more important than certificates: Why An AWS Certification Will Not Get You An AWS Job!

No two jobs will be the same. Find out the AWS position you want and then go research it on Indeed, LinkedIn, ZipRecruiter, CareerBuilder, GlassDoor, Monster. What appears on "most" of those job reqs is what you need to learn/know.

Create better searches on those job sites!

You can find recruiters by doing fuzzy searches on keywords + location. Then follow or message said recruiter for future opportunities. From there you can also find the commonly used "recruiter hashtags" that are relevant to your area. Recruiters tend to use common hashtags for job postings (sometimes location dependent -- #awsToronto #awsSeattle)

Where Do I Find Recruiters?

DevOps Engineer role

While not specific to AWS, the DevOps Roadmap is incredibly useful in painting some context for the general learning of AWS concepts like EC2 and logs management and CI/CD tooling.

That being said, for DevOps position, here is a very general idea to get you started:

  1. At least 1 major cloud associate level certification (AWS, Azure, GCP)
  2. At least 1 hands on with Ansible, Puppet, Chef, Salt
  3. At least 1 hands on with Docker or Kubernetes
  4. At least one scripting language, perf Python, JavaScript, Go, or Java
  5. At least 1 Windows or Linux, perf both
  6. An understanding of DevOps and Agile environments

When you have a good grasp of the above, these are some "good to knows":

  1. At least 1 hands on with Pulumi, CDK or Terraform
  2. At least 1 hands on with Gitlab CI, Github Actions, Jenkins, Drone CI, or Circle CI
  3. At least 1 hands on with ArgoCD, and Spinnaker

Software/Cloud Engineer role

Software/Cloud Engineer is responsible for a business logic that is about to be implemented (more in the definition). Since in such role, work on the actual code is being done, automation skills are not so important but a practical knowledge of tools that help you implement logic is necessary. That include:

  1. Ability to use: EC2, ECS, EKS, Lambda for development work
  2. Ability to use available databases and storage products to model and store data in:
    1. Relational databases like PostgreSQL, MariaDB
    2. NoSQL datastores like DynamoDB, DocumentDB, Redis, Elasticsearch
    3. S3
  3. Asynchronous systems like SQS, SNS, Kafka
  4. API platforms like API Gateway, AppSync
  5. Big Data platforms like AWS EMR, Glue, Athena
  6. Knowledge of CloudFront to optimize websites (if doing web development)

Software/Cloud architect role

When searching for AWS jobs, there's a lot of offers for Cloud/Solution/Software Architect positions. In general, an architect at an IT project is a software developer expert who makes high-level design choices and tries to enforce technical standards, including software coding standards, tools, and platforms.

Software architect role encompasses technical expert skills and soft skills, since communication across team members, representatives and across enterprise can be necessary. Usually an architect is a distinguished developer with years of work experience across many projects. No single path leads to this role but this paper tries to sketch a roadmap.

How Much Should I Make At x Position?

  1. Glassdoor
  2. LinkedIn Salary
  3. Payscale
  4. CompTIA IT Career Path
  5. CompTIA Tech Town Index 2019
  6. IT Career Roadmap 2020 by Salary - credits to /u/SinecureLife

How to write a good CV?

  1. Try to keep information about you on one page and include:
    1. Your current title
    2. Short description of your skills
    3. Your experience, only relevant one for your position
    4. Your certificates, school (if relevant)
    5. GitHub profile if active
  2. When listing experience, be concrete and precise; show what impact you had to the organization and provide measurable values e.g.
    1. Managing 5 AWS accounts in a process of company wide cloud migration process for 10 development teams
    2. Being technically responsible for 2 company products
    3. Developing organization wide CI/CD pipelines utilizing Serverless Functions (Lambda), Ansible, AWS APIs to 5 development teams
  3. Everybody lies, same as your competitors for a job; try to provide demonstrable information in the resume, it's easy to see if a person is not consistent
  4. Forget cover letters if it's not a VP/SVP/Director level; if an organization asks for it at technical positions, it's a sign of a pathological organization (Google doesn't do cover letters at all)
  5. If a company tries to do a reference check, that can be a signal of a pathological organization; don't bother getting references but try to understand reasons for them once asked
  6. KISS, for technical roles that's fine to have even txt with your achievements

More resources

  1. The cloud resume challenge - for ones starting the career

Where can I pickup those non AWS skills?

  1. KodeKloud (DevOps, Linux, Docker, Ansible, Puppet, Kubernetes, Chef, Docker Swarm, OpenShift)
  2. instruqt (DevOps, Docker, Kubernetes, Terraform, React, CI/CD, Git)
  3. Codecademy (Python, JavaScript, Java, SQL, Go, etc.)
  4. Automate the Boring Stuff (Python)
  5. Katacoda (Docker, Kubernetes, Linux, Git, Languages, Terraform)
  6. Linux Journey https://linuxjourney.com/ (Linux)
  7. Over The Wire (Security)
  8. DevOps Bootcamp (24 Video DevOps Bootcamp)

Success Stories

  1. How I Went From 14hr to 70k with no experience!
  2. Tossing My Coin That Hat Too I'm A College Dropout
  3. Guide to Passing All 3 AWS Associate Level Certifications
  4. How to Pass Three AWS Associate Certifications In One Month
  5. How To Start a Career in Cloud Computing

Other

  1. What Is SRE?
  2. What is DevOps?
  3. What is Agile?
  4. What is CI/CD?