Skip to content
The Chat Archive
mistral-medium-2505· Mistral AI LMArena Human Preference 140K

AWS certification is mostly about knowing the system, rather than a 'CS cert', right?…

  1. User

    AWS certification is mostly about knowing the system, rather than a 'CS cert', right? Because ideally you want someone who is capable of writing AWS themselves - this means they FOR SURE understand what exactly is going and and they're doing. Naturally, this desire is not really fulfillable at <300k after taxes.

  2. Assistant

    You're touching on a few interesting points about AWS certifications, software engineering expertise, and compensation expectations. Let me break this down:

    1. AWS Certifications vs. Computer Science Fundamentals

    • AWS Certifications are indeed more about understanding AWS services, architecture best practices, and operational knowledge rather than deep computer science theory (algorithms, data structures, etc.).
    • They validate familiarity with AWS tools and how to use them effectively, but they don’t necessarily prove someone can build AWS-like systems from scratch.
    • A "CS cert" (e.g., a degree or rigorous CS training) would focus more on fundamentals like distributed systems, networking, security, and low-level programming—skills needed to create something like AWS.

    2. Writing AWS vs. Using AWS

    • Writing AWS (or a cloud platform) from scratch is an entirely different beast. It requires deep expertise in:
      • Distributed systems (consensus algorithms, fault tolerance, scalability)
      • Virtualization and containerization
      • Networking (SDN, load balancing, DNS)
      • Security (IAM, encryption, compliance)
      • Storage systems (databases, object storage, block storage)
    • Most engineers using AWS don’t need to know how to build it—they need to know how to leverage it effectively. That’s where AWS certifications come in.

    3. Compensation Expectations

    • The idea that someone who could build AWS would be paid <$300k after taxes is unrealistic. Engineers with that level of expertise (e.g., senior distributed systems engineers at AWS, Google Cloud, or Azure) are typically in the high six-figure to seven-figure range (total comp, including equity).
    • AWS certifications alone won’t get you there—they’re more about proving operational/cloud engineering skills, which are valuable but not at the same level as core systems engineering.
    • If you want to work on building cloud infrastructure (not just using it), you’d need:
      • A strong CS background (or equivalent experience)
      • Deep knowledge of distributed systems
      • Experience with low-level programming (Go, Rust, C++, etc.)
      • A track record of working on scalable, fault-tolerant systems

    4. The Reality of Cloud Engineering Roles

    • Most cloud engineers (even highly paid ones) are users of AWS, not builders of it.
    • AWS certifications are useful for roles like:
      • Cloud Architects
      • DevOps Engineers
      • Solutions Architects
      • SysAdmins transitioning to cloud
    • These roles can pay very well (especially at FAANG or top tech companies), but they’re not the same as the engineers designing AWS services.

    TL;DR

    • AWS certs = good for using AWS effectively, not for building it.
    • Building AWS-level systems requires deep CS/distributed systems expertise and pays much more than $300k.
    • If you want to work on creating cloud infrastructure (not just using it), focus on distributed systems, low-level programming, and high-scale engineering—not just certifications.

    Would you like recommendations on how to bridge the gap between "using AWS" and "building AWS-like systems"?

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.