What is ops load?

Tyler Technologies / Eng
โซโฌโ—€๏ธ๐Ÿ”ผ๐Ÿ”ฝ

Go to company page Tyler Technologies Eng

โซโฌโ—€๏ธ๐Ÿ”ผ๐Ÿ”ฝ
Apr 9 5 Comments

Poll: Do AWS teams actually provide more backend swe growth opportunities than other product teams at Amazon?

Everyone here complains about heavy oncall and ops load. What are the kinds of problems you have to fix when on call? What is ops load? I know the answers to these questions will vary from team to team...trying to get a general idea.

TC: 110K

#aws

18 PARTICIPANTS SELECT ONLY ONE ANSWER
VOTE VIEW RESULT

comments

Want to comment? LOG IN or SIGN UP
TOP 5 Comments
  • Google
    fh9393j

    Go to company page Google

    fh9393j
    At amazon/AWS, you own the entire infrastructure as a team. Instances, LBs, Queues, etc. literally everything. And each individual team usually owns 3-6 services. They all have different levels of maintainance and gatekeeping.

    Since most of the development at Amazon (that's the case everywhere else too) is promo driven. These infra and sometimes, integration tests, canaries, load tests etc. are just all over the place. Making development such a pain in the ass.

    So, whenever someone notices something, they log an Ops ticket that goes into the backlog. With immence pressure from the PM and managers, no one ever gets to resolve these items and the development keeps getting tougher and makes the feature launches such a pain in the butt. Finally teams will be working on launching a v+1 for all services thinking they will do everything right this time only to know it won't happen and then switch teams or companies. Then realize this is the Software Development Lifecycle that CS courses should teach not some agile or waterfall bull crap
    Apr 9 2
    • Meta
      wirt

      Go to company page Meta

      wirt
      My lord there are teams at amazon that own 6 services??
      Apr 9
    • Amazon / Eng
      BrazilBe๐Ÿ‘

      Go to company page Amazon Eng

      PRE
      iCIMS
      BrazilBe๐Ÿ‘
      @wirt Is 6 a lot of a little? My last company we owned 2 products which was made up of 4 services/pipelines. At Amazon we have one big product but several microservices and workflows go into it.

      For me I think the biggest issue is when leadership decides to take shortcuts to launch early and what winds up happening is that in the future it just becomes terrible.
      Apr 9
  • Amazon / Eng
    BrazilBe๐Ÿ‘

    Go to company page Amazon Eng

    PRE
    iCIMS
    BrazilBe๐Ÿ‘
    Some guy joined my team after being on sage maker team for 2 months. He was a college new hire and said he never did any feature work. They had a huge OE burden, so much so devs just became defacto SREs.

    Maybe it's a timing thing, idk. My team has had some bad weeks or even a month where OE is heavy due to system failures or upstream issues. So I don't think any team is perfect, but AWS is known for their more so heavy production issues
    Apr 9 1
    • Amazon
      LrLx18

      Go to company page Amazon

      LrLx18
      You should be careful with such teammate. A new hire would need more time than 2 months to learn the stack and start working on good projects. Initially the new hires get small items to ramp up and learn.
      Apr 9