20 tasks, each one witnessed by the sources that watched the job — and behind every one, a prompt you can use tonight.
You spend the morning reviewing system requirements, reading architecture docs, and checking alerts from AWS (for example EC2 instances or CloudFormation stacks).
Afternoons are meetings: design reviews, white papers or technical reports, and coordinating with admins who configure servers or run Ansible playbooks. You also test interoperability and run scripted tests (Airflow jobs or unit tests) to verify stability and scalability.
Expect to work with cloud services like Amazon Web Services (AWS): EC2 for compute and CloudFormation for infrastructure-as-code. You’ll also use tools like Ansible for configuration, Apache Airflow for workflow scheduling, and databases such as Apache Cassandra.
You might use AJAX in web interfaces and Adobe Acrobat to produce technical reports. Pick a few and get hands-on: spin up an EC2 instance and write a CloudFormation template first.
Yes, but carefully. Use AI to draft diagrams, suggest components, or write boilerplate CloudFormation/Ansible snippets, then manually review everything for correctness and security. AI can hallucinate wrong resource names or risky defaults.
Never deploy AI-generated templates or code without validating them against your security checks and running tests for scalability, portability, and interoperability.
Bureau of Labor Statistics (BLS) data for 2025 covers roles in this area: about 435,370 employed. The median pay listed is $116,580 per year, the bottom tenth $55,940, and the top tenth $188,470. These are BLS numbers and represent a broad occupation group.
Actual pay varies by company, cloud experience (AWS, Ansible), and industry.
Start with core skills: learn Linux basics, networking, and a programming/scripting language (Python). Then get hands-on with AWS: create an EC2 instance, deploy a simple app, and write a CloudFormation template.
Learn one config tool (Ansible), one scheduler (Apache Airflow), and a database like Cassandra. Build small end-to-end projects so you can show you can design, implement, and test solutions.
The hardest skill is translating requirements into robust, testable system architecture — not just diagrams, but templates and scripts you can deploy. That means producing CloudFormation or Ansible artifacts that meet functional specs and pass tests for stability, security, and scalability.
Good architects also run hardware/software tests, troubleshoot issues, and communicate trade-offs clearly in reports or presentations.