Overview: My 12‑month plan transitions from SRE to Solutions Architect by building architecture skills, stakeholder influence, and product‑focused design experience. Each quarter has concrete milestones, measurable success metrics, and activities across learning, projects, mentoring, and visibility.
Skills to acquire
- Technical: systems design, distributed systems patterns, cloud architecture (multi‑AZ, VPC, CDN, IAM), cost optimization, IaC at scale (Terraform/Crossplane), API design, security (TLS, WAF), observability at architectural level.
- Soft: stakeholder communication, technical sales storytelling, requirements elicitation, architectural trade‑off negotiation, presentation & facilitation.
Certifications / courses
- AWS Certified Solutions Architect – Professional (months 6–12)
- Google Professional Cloud Architect or Azure Solutions Architect (optional, months 9–12)
- Courses: “Designing Data‑Intensive Applications” (book/course), System Design interviews course, advanced Terraform course.
Cross‑functional projects
- Lead a platform migration proof‑of‑concept (lift & modernize) with dev, security, and product.
- Define SLOs and error budgets for a customer‑facing product and propose architectural changes to meet targets.
- Design and present a cost‑optimization and reliability plan for high‑traffic service.
Mentoring & visibility
- Mentor 1–2 junior SREs on architecture principles; run brown‑bag sessions monthly.
- Present architecture reviews in 3 all‑hands or product guild meetings.
- Publish a public case study or internal runbook on a migration or design pattern.
Success metrics
- Architected solution accepted by stakeholders (proposal approvals).
- Measurable reliability/cost improvements (e.g., SLO attainment +15%, cost −10%).
- Completion of certifications and 3 cross‑team presentations.
- Positive feedback from PMs/engineers (>=4/5) on architecture workshops.
Milestones
- Month 3: Complete system design course; lead one SLO definition for product; present 1 brown‑bag; mentor assigned; draft learning plan. Metrics: course completed, SLO draft approved.
- Month 6: Finish AWS Professional prep (associate or equivalent cert complete); lead POC for migration; deliver architecture proposal with cost/reliability analysis. Metrics: POC demo, stakeholder sign‑off, certification (associate) achieved.
- Month 9: Architect and implement at least one production change (e.g., multi‑AZ failover or API gateway redesign) reducing incidents or cost; present case study internally; start professional cert exam. Metrics: incident rate down, cost saved, case study published.
- Month 12: Pass Solutions Architect professional cert; have 2 cross‑functional wins and measurable impact (SLO attainment improvement, cost reduction); transition plan agreed with manager and be staffed as Solutions Architect on at least one project. Metrics: cert passed, manager approval, stakeholder endorsements.
Rationale: This plan pairs technical depth with stakeholder work and visible deliverables so I demonstrate architecture thinking, influence, and measurable impact—key signals for a Solutions Architect promotion or role change.
