My job as a Process Engineer - Technology (Part 3)

Part 3

How do we track our work?

We use SIMs to track our work and we use story points to estimate how much time it’ll take to complete, and how long it actually took to complete.

Story points:

  • 1 story point equals 4 hours (half a day of work)
  • 2 story points equal 8 hours (full day of work)

Oncall

My team has oncall and the oncall tasks include:

  • Triaging SIMs and TTs that come in
  • Twice a week office hours to answer questions from anyone internally at Amazon who has questions
  • Deploying software. Note: We mainly only deploy twice a week, but it could be more if we get approval & have a need to
  • Monitoring software availability
  • Updating the wiki for the software we deployed

Monitoring Software Availability

For our software (workflows), we’ve setup monitors and various metrics.

If the software triggers one of the metrics then we’ll get:

  • An email via our internal outlook email
  • A notification on our phone via the Amazon paging app
  • A TT will be created in our teams folder

If you’re oncall and get an alarm then you’re expected to look into it ASAP and drive it to resolution.

So, you can be woken up at random times during the night and have to log on to look into the issue.

Tech Reviews

For my team we create SIMs for our Tech Reviews.

  • We have a person who’s in charge of assigning Tech Reviews to Tech Reviewers.
  • Once a Tech Review is assigned to a Tech Reviewer, it’s supposed to be reviewed & feedback provided within 48hrs iirc
  • After Tech Reviewer reviews it it’s either approved or denied and needs changes

Who can become a tech reviewer?

Any Engineer on my team can become one after they’ve been in the role a bit. You’ll just need to go through training for it.

Deployment

After Tech Review SIM is approved you can create a PROD SIM for deployment.

The deployment SIM usually covers:

  • What version of the software & software name you’re deploying
  • What changes you made
  • Are these changes P4A, P4S, or both. Note: P4A is Paragon for Associates (internally facing) & P4S is Paragon for Sellers (externally facing)
  • Are the changes new
  • Are the changes being deployed to a new market place. Note: Marketplaces are countries
  • Provide a link to the software version that you’re deploying for the Git Sync
  • Update any of the wikis for the software

What are wiki updates for deployment?

My team has an internal Amazon wiki that lists all of our software and any info on them including stuff like what APIs it consumes.

Oncall Deployment Tasks

Going back to oncall for a bit, the oncall person would review all of the SIMs for deployment that day.

Note:

  • We have a Quarterly SIM which is the main SIM for all deployment SIMs for that quarter
  • That Quarterly Deployment SIM has a child SIM for each deployment day in that quarter
  • The Engineer attaches their deployment SIM as a child to the specific deployment day

If there are any issues with how the Engineer filled out the Deployment SIM, then the oncall person would comment on the SIM for it to be fixed prior to starting deployment.

Note: If the issue isn’t fixed in time then the oncall person removes that deployment SIM from that days deployment

After the oncall Engineer reviews the deployment SIM for that day and all issues are addressed, they have to create a MCM which is the deployment SIM for that day specifying what we’re deploying.

After the MCM is done all the Engineer sago have software deploying that day, and the other Engineers who are in charge of approving, have to review and either approve that the MCM is correct or provide comments for fixes.

Now, after the MCM is approved you can finally start actually deploying the software lol.

Note: If Amazon as a whole has any active Sev 1, Sev 2, or Sev 3 tickets, that could stop you from deploying after doing all that work with the MCM. The MCM has an automated system to look out for Sev 1-3s

Posted Aug 12, 2023, 10:44 PM UTC

10
Loading comments…