Delivery & Platform 90 days 2-3 hours/day updated 2026-06-01
NoOps 90-Day Learning Path
Master NoOps in 90 days — serverless, managed services, auto-scaling, and policy-driven automation. Remove manual ops work so engineers focus entirely on product value.
What NoOps means
NoOps is the aspiration to eliminate manual operational work through pervasive automation, serverless computing, and fully managed cloud services. Rather than abolishing operations, it transforms ops responsibilities into platform automation, policy-as-code, and self-healing systems. Teams embracing NoOps invest in abstractions so developers deploy, scale, and observe without ops tickets.
Who should follow this path
- Application developers seeking to own their deployments
- DevOps engineers automating away operational toil
- Platform engineers building zero-touch delivery
- Startup engineers operating lean with managed services
Prerequisites
- Experience with at least one cloud provider
- Basic understanding of serverless concepts
- Familiarity with CI/CD pipelines
- Knowledge of container and Kubernetes basics
The 90-day plan
Daily study recommendation: 2-3 hours/day, six days a week. Consistency beats intensity — block the time in your calendar like a meeting.
Days 1–15: Foundation
- NoOps principles and the toil reduction mindset
- Serverless architecture patterns (FaaS and BaaS)
- Managed databases, queues, and caches
- Auto-scaling and load balancing fundamentals
- Cloud provider NoOps offerings overview
Outcome: Map a workload to appropriate NoOps services and quantify toil reduction opportunity.
Days 16–30: Core concepts
- AWS Lambda and API Gateway deep dive
- Google Cloud Run and Cloud Functions
- Azure Functions and Logic Apps
- Serverless Framework and SAM
- Event-driven architecture patterns
Outcome: Deploy a serverless, event-driven application across at least one major cloud platform.
Days 31–45: Tools and workflows
- Policy-as-code with OPA and AWS Service Control Policies
- Automated compliance remediation
- Self-healing infrastructure with AWS Systems Manager
- Auto-remediation runbooks
- Drift detection and automated correction
Outcome: Implement self-healing, policy-driven infrastructure that corrects itself automatically.
Days 46–60: Hands-on projects
- GitOps for NoOps delivery
- Infrastructure automation with CDK and Pulumi
- Zero-touch deployment pipelines
- Automated canary analysis with no manual gates
- Cost governance automation
Outcome: Build a zero-touch delivery pipeline from commit to production with no manual steps.
Days 61–75: Advanced practices
- Observability in serverless environments
- Distributed tracing for Lambda and Cloud Run
- Cold start optimization strategies
- FinOps for serverless cost control
- SLOs for managed and serverless services
Outcome: Operate serverless workloads with full observability and cost visibility.
Days 76–90: Portfolio, interview & certification prep
- Portfolio: fully automated NoOps application
- NoOps interview question preparation
- AWS Serverless certification paths
- Evaluating NoOps maturity for an organization
- Documenting automation decisions and trade-offs
Outcome: Present a production-grade NoOps platform and articulate the automation trade-offs.
Weekly outcomes at a glance
| Phase | Outcome |
|---|---|
| Days 1–15 | Map a workload to appropriate NoOps services and quantify toil reduction opportunity. |
| Days 16–30 | Deploy a serverless, event-driven application across at least one major cloud platform. |
| Days 31–45 | Implement self-healing, policy-driven infrastructure that corrects itself automatically. |
| Days 46–60 | Build a zero-touch delivery pipeline from commit to production with no manual steps. |
| Days 61–75 | Operate serverless workloads with full observability and cost visibility. |
| Days 76–90 | Present a production-grade NoOps platform and articulate the automation trade-offs. |
Tools to learn
- AWS Lambda
- Google Cloud Run
- Azure Functions
- Serverless Framework
- AWS CDK
- Pulumi
- OPA
- AWS Systems Manager
- Argo CD
- Datadog
Labs to practice
Mini projects
- Build a fully serverless event-driven order processing system
- Implement self-healing EC2 auto-remediation with AWS Systems Manager
- Create a zero-touch GitOps pipeline with automated canary analysis
Interview questions to prepare
- What is the difference between NoOps and serverless?
- How do you handle stateful operations in a NoOps environment?
- What are the observability challenges unique to serverless functions?
- How do you enforce security policies in a NoOps platform?
- Explain cold start latency and how to minimize it in Lambda.
- What is event-driven architecture and how does it enable NoOps?
- How do you perform capacity planning when using auto-scaling managed services?
Certification suggestions
- AWS Certified Developer – Associate — AWS
- AWS Certified Solutions Architect – Professional — AWS
- Google Associate Cloud Engineer — Google Cloud
Browse the full certification registry for exam details and official links.
Free resources
- AWS Serverless Documentation
- Google Cloud Run Documentation
- Serverless Framework Documentation
- AWS CDK Documentation
- Pulumi Documentation
Related roadmaps
Related tool categories
// instructor-led option
Prefer live, guided training with mentors and certification support? DevOpsSchool.com runs paid instructor-led programs that pair well with this free path.
Explore paid training on DevOpsSchool.com ↗