1) Role Summary

The Junior Capacity Planning Analyst supports the Cloud & Infrastructure organization by collecting, analyzing, and reporting on capacity, utilization, and demand trends across compute, storage, network, and key platform services. The role focuses on producing reliable data views, identifying early signals of constraint or waste, and enabling informed decisions about scaling, purchasing, reservations/commitments, and performance risk mitigation.

This role exists in software and IT organizations because cloud and infrastructure capacity is both a reliability dependency (insufficient capacity causes outages and performance degradation) and a major cost driver (overprovisioning drives avoidable spend). The Junior Capacity Planning Analyst helps convert raw telemetry and inventory data into actionable capacity insights, improving planning discipline and reducing operational surprises.

Business value created includes improved forecast accuracy, reduced incident risk from saturation, better cloud cost hygiene through rightsizing recommendations, and better cross-team alignment between infrastructure supply and product/engineering demand. This is a Current role, widely used today in organizations operating cloud platforms, hybrid environments, or large-scale on-prem infrastructure.

Typical interaction occurs with: – Cloud Platform Engineering / SRE / Infrastructure Operations – FinOps / Cloud Cost Management (where present) – Engineering teams (workload owners) – Architecture and technical program management – Procurement / vendor management (for contracts/commitments) – Security and compliance (capacity controls, data handling) – Finance partners for budgeting and forecasting cycles

2) Role Mission

Core mission:
Provide accurate, timely, and decision-ready capacity insights for cloud and infrastructure services by maintaining clean datasets, producing forecasts and dashboards, and supporting planning routines that balance reliability, performance, and cost.

Strategic importance to the company: – Capacity constraints are a primary root cause of incidents (resource exhaustion, noisy neighbors, quota limits, throughput saturation). – Capacity oversupply is a primary driver of infrastructure waste (idle resources, oversized nodes, unused commitments). – A disciplined capacity planning function enables predictable scaling for product growth, launches, and peak events.

Primary business outcomes expected: – Improved visibility into utilization and headroom for critical services – Early identification and escalation of capacity risks – Practical recommendations that reduce spend without harming reliability – Consistent, repeatable reporting used in monthly/quarterly planning and budgeting cycles

3) Core Responsibilities

Strategic responsibilities (junior scope: supporting and informing, not owning strategy) 1. Support the capacity planning cadence by preparing monthly/quarterly capacity packs (utilization, headroom, forecast deltas, notable risks). 2. Assist with demand intake by capturing upcoming launches, migrations, and growth assumptions from engineering and product teams. 3. Contribute to optimization initiatives (rightsizing, commitment utilization, storage tiering) by providing analysis and tracking realized outcomes. 4. Maintain a capacity risk register (constraints, likely saturation dates, quota limits) and ensure it is reviewed in planning forums. 5. Document planning assumptions (growth rates, seasonality, peak factors) used in forecasts so outputs are auditable and repeatable.

Operational responsibilities 6. Monitor capacity health signals (CPU, memory, disk, IOPS, network throughput, queue depth, saturation, throttling) for priority platforms. 7. Prepare weekly headroom snapshots for critical services and environments (prod vs non-prod) and flag abnormal trend shifts. 8. Track reserved capacity/commitments usage (e.g., Savings Plans/RIs, committed use discounts) and surface underutilization risks. 9. Support incident and post-incident reviews by providing “capacity context” (utilization leading indicators, scaling events, quota/limit constraints). 10. Coordinate with operations for planned changes (cluster expansions, instance family changes, storage expansions) by ensuring data-driven sizing inputs are available.

Technical responsibilities 11. Collect and validate data from monitoring systems, cloud billing exports, CMDB/inventory, and platform logs; reconcile discrepancies. 12. Build and maintain dashboards (utilization, saturation, unit cost, capacity vs demand) in a BI tool or monitoring analytics layer. 13. Produce lightweight forecasts using time-series trend methods (moving averages, seasonality adjustments, regression where appropriate) under supervision. 14. Develop repeatable reports using spreadsheets, SQL queries, or scripts to reduce manual effort and improve consistency. 15. Define and track capacity KPIs (headroom days, forecast accuracy, utilization bands, constraint counts, actionable recommendations) aligned to team goals.

Cross-functional / stakeholder responsibilities 16. Partner with workload owners to validate demand assumptions and to interpret anomalies (deployments, traffic changes, feature toggles). 17. Collaborate with FinOps/Finance (if present) to connect capacity decisions to budgets, forecasts, and unit economics. 18. Communicate findings clearly to technical and non-technical stakeholders, distinguishing signal from noise and stating confidence/assumptions.

Governance, compliance, or quality responsibilities 19. Ensure data quality and lineage for key datasets (definitions, refresh frequency, source-of-truth alignment) and follow access controls for sensitive telemetry or cost data. 20. Follow change management practices when modifying dashboards, queries, or reporting logic; maintain versioned documentation and peer review where required.

Leadership responsibilities (limited; junior level) – No direct people management expectations.
– Demonstrates “micro-leadership” by owning specific reporting components end-to-end, improving processes, and proactively escalating risks with evidence.

4) Day-to-Day Activities

Daily activities – Check key capacity dashboards for critical platforms (e.g., Kubernetes clusters, databases, edge/CDN quotas, message queues). – Review alerts or anomaly reports related to saturation/throttling and validate whether they reflect real demand, misconfiguration, or telemetry issues. – Triage data freshness and fix broken pipelines/exports (e.g., delayed billing export, missing tag coverage, agent outage). – Answer stakeholder questions on headroom, utilization, and “can we support X?” with data and documented assumptions.

Weekly activities – Produce a weekly capacity snapshot for priority services: – Current utilization bands and peaks (P50/P95/P99 where relevant) – Headroom vs SLO/SLA guardrails – Top drivers of change (traffic, deployments, scaling policies) – Join infrastructure planning standup (or ops review) to walk through risks and planned scaling actions. – Validate upcoming demand signals: – Product launch calendar / marketing events – Migration schedules – Batch/ETL schedule changes – Maintain a “recommendations backlog” (rightsizing candidates, storage reclamation, unused commitments) and update status.

Monthly or quarterly activities – Build and publish the monthly capacity planning pack: – Trend analysis by service/environment – Forecast vs actual deltas and root-cause notes – Risks, constraints, and recommended actions – Commitment coverage and underutilization risks – Notable cost/performance tradeoffs – Support budgeting and forecasting cycles with baseline infrastructure run-rate and growth-driven deltas. – Assist with quarterly business review inputs for Cloud & Infrastructure (capacity health, efficiency improvements, reliability posture).

Recurring meetings or rituals – Capacity/FinOps working session (biweekly or monthly) – Infrastructure operations review (weekly) – SRE/performance review forum (weekly/biweekly) – Launch readiness or change advisory board (CAB) (context-specific) – Post-incident review (as incidents occur)

Incident, escalation, or emergency work (relevant but not primary) – During incidents involving resource exhaustion or scaling failures: – Pull quick evidence: utilization leading up to the event, scaling activity, quota errors, throttling, node pressure, storage fullness – Provide time-to-saturation estimates if the incident is ongoing – Help identify immediate mitigations (temporary scale-out, throttling non-critical jobs, disabling heavy features) in coordination with SRE/ops – After incidents: – Document capacity-related contributing factors and update thresholds/alerts or reporting to prevent recurrence

5) Key Deliverables

Concrete outputs commonly owned or co-owned by the Junior Capacity Planning Analyst:

• Weekly Capacity Snapshot (standardized report) for critical services and clusters
• Monthly Capacity Planning Pack (deck or doc) for Cloud & Infrastructure leadership review
• Capacity Dashboards (utilization, saturation, headroom, forecast, constraint tracking)
• Forecast Workbook/Model (documented assumptions, trend logic, scenario toggles)
• Capacity Risk Register (constraints, “days to saturation,” quotas, dependencies, owners, mitigation plan)
• Rightsizing & Optimization Candidate List (ranked by impact and confidence)
• Commitment Utilization Tracker (RIs/Savings Plans/CUDs) with under/over-coverage flags
• Data Dictionary / Metric Definitions for capacity KPIs and core datasets
• Runbook snippets for repeatable reporting tasks (data refresh, validation checks, troubleshooting)
• Post-Incident Capacity Evidence Pack (graphs and notes supporting PIR analysis)
• Tagging/Allocation Coverage Report (for cost and ownership mapping; context-specific but common in cloud)

6) Goals, Objectives, and Milestones

30-day goals (onboarding + baseline contribution) – Understand the organization’s infrastructure landscape (cloud accounts/projects/subscriptions, regions, major platforms). – Gain access to core tools (monitoring, BI, billing exports, inventory/CMDB, documentation). – Learn key KPIs and guardrails used by SRE/Platform (e.g., target utilization bands, SLO constraints). – Deliver first “shadow” weekly capacity snapshot with manager feedback. – Document data sources and refresh schedules for at least 3 critical services.

60-day goals (independent execution of defined scope) – Own weekly capacity snapshot end-to-end for a defined set of services (e.g., Kubernetes + storage + one managed database). – Improve one dashboard/report for accuracy or clarity (e.g., peak vs average, percentiles, seasonality). – Produce 2–3 actionable recommendations (rightsizing or commitment optimization) with quantified impact and confidence. – Implement a basic data quality check (missing data, outliers, stale refresh) for one pipeline.

90-day goals (repeatability + stakeholder trust) – Publish monthly capacity pack sections for assigned platforms with minimal rework. – Demonstrate basic forecasting competence: explain assumptions, show scenario ranges, quantify uncertainty. – Establish a repeatable “capacity risk register” update process and ensure owners review it. – Participate effectively in at least one incident/PIR by delivering clear capacity evidence.

6-month milestones (measurable operational impact) – Improve forecast accuracy for at least one platform/service by implementing better drivers (traffic proxy, job schedules, release calendar). – Reduce manual reporting effort by automating at least one recurring report (SQL/scripted extraction + templated output). – Contribute to a measurable efficiency outcome (e.g., 3–8% cost reduction in a scoped domain) through vetted recommendations and tracking. – Expand coverage to additional service types (network egress, cache layers, queue systems) depending on environment.

12-month objectives (recognized contributor within capacity function) – Be a dependable owner of core reporting for a significant slice of infrastructure. – Deliver consistent, decision-grade capacity insights that stakeholders use for planning and approvals. – Demonstrate the ability to connect capacity data to business drivers (growth, launches, reliability risk, cost). – Help mature the capacity planning operating model: definitions, cadence, and consistent decision records.

Long-term impact goals (beyond 12 months; career-building) – Build capability toward “mid-level” capacity planning: – More advanced forecasting techniques and scenario planning – Stronger cross-functional influence and negotiation around tradeoffs – Ownership of capacity planning for a platform domain end-to-end – Become a go-to analyst for reliability and cost-informed scaling decisions.

Role success definition – Stakeholders trust the data. – Risks are identified early (before incidents). – Recommendations are actionable, quantified, and tracked to outcomes. – Reporting is repeatable, efficient, and aligned to decision cycles.

What high performance looks like – Produces accurate, well-explained analyses with clear assumptions and caveats. – Spots leading indicators (trend inflections, saturation creeping, quota risks) earlier than reactive monitoring. – Communicates with crisp, decision-oriented framing: “What’s happening, why it matters, what we should do next.” – Improves processes (automation, definitions, templates) rather than repeating manual work indefinitely.

7) KPIs and Productivity Metrics

The following measurement framework balances output (what is produced), outcomes (business impact), quality (trustworthiness), efficiency (effort), reliability (risk reduction), improvement, collaboration, and stakeholder satisfaction.

Metric name	What it measures	Why it matters	Example target / benchmark	Frequency
Weekly capacity snapshot on-time rate	Delivery of weekly report by agreed deadline	Ensures consistent visibility and trust	≥ 95% on-time	Weekly
Monthly capacity pack completeness	Required sections/metrics included for assigned domains	Prevents gaps in decision-making	100% of required sections	Monthly
Data freshness SLA adherence	% of datasets refreshed within expected window	Stale data causes bad decisions	≥ 98% within SLA	Daily/Weekly
Data accuracy spot-check pass rate	Sampled reconciliation vs source-of-truth	Maintains credibility of insights	≥ 97% pass	Monthly
Metric definition compliance	Use of standardized KPI definitions across reports	Avoids conflicting narratives	≥ 90% adherence	Quarterly
Forecast accuracy (MAPE) – scoped service	Error between forecast and actual for a key metric (e.g., CPU peak, storage used)	Direct measure of planning quality	MAPE ≤ 15–25% (service-dependent)	Monthly
Headroom coverage reporting	% of tier-1 services with current headroom view	Ensures critical systems monitored	≥ 95% coverage	Weekly
Days-to-saturation visibility	Tier-1 services with estimated “days to saturation” where meaningful	Enables proactive scaling	≥ 90% of applicable services	Weekly/Monthly
Capacity risk register hygiene	Risks have owner, severity, ETA, mitigation	Keeps planning actionable	≥ 95% risks fully populated	Monthly
Early warning lead time	Time between risk flag and actual constraint/incident	Measures proactive value	≥ 2–4 weeks lead time average (where possible)	Quarterly
Incident capacity contribution	# of incidents where capacity evidence is provided within agreed timeframe	Speeds diagnosis	Evidence within 2 hours for major incidents	Per incident
Rightsizing recommendation throughput	# of vetted candidates delivered	Drives optimization pipeline	2–6 per month (scoped)	Monthly
Rightsizing acceptance rate	% recommendations adopted by owners	Indicates quality and practicality	≥ 50–70%	Monthly/Quarterly
Realized savings (verified)	Savings from implemented recommendations (normalized)	Business value; ties to cost	Target set by org; e.g., $X/quarter	Quarterly
Cost avoidance from proactive scaling	Estimated avoided incident/penalty/expedite costs	Shows reliability value	Documented cases; target N per quarter	Quarterly
Commitment utilization rate (RIs/SP/CUDs)	Actual usage vs purchased commitments	Prevents wasted commitments	≥ 90–95% utilization (context-specific)	Weekly/Monthly
Tagging/allocation coverage (if applicable)	% spend/resources with owner/team tags	Enables accountability and planning	≥ 95% for prod	Monthly
Dashboard adoption	Unique viewers / usage metrics	Confirms usefulness	Trend upward; baseline + 20%	Monthly
Stakeholder satisfaction score	Survey or qualitative score from key stakeholders	Captures trust and usability	≥ 4.2/5 or positive NPS	Quarterly
Cycle time to answer ad-hoc questions	Time to respond with validated data	Improves decision velocity	≤ 1–2 business days	Monthly
Automation coverage of reporting tasks	% recurring tasks automated	Reduces errors and time	+1–2 tasks/quarter	Quarterly
Documentation completeness	Reports with documented logic and sources	Enables maintainability	≥ 90%	Quarterly

Notes on benchmarks: – Targets vary by maturity and data quality. Early-stage capacity functions often start with on-time delivery and data hygiene before aggressive forecast accuracy goals. – Some services are inherently harder to forecast (burst traffic, batch jobs). Targets should be service-specific.

8) Technical Skills Required

Must-have technical skills – Spreadsheet modeling (Excel/Google Sheets)
– Use: trend analysis, pivot tables, scenario models, simple forecasting
– Importance: Critical – Basic statistics and time-series literacy
– Use: moving averages, percentiles, seasonality awareness, interpreting variability
– Importance: Critical – SQL fundamentals
– Use: querying telemetry exports, billing/cost datasets, inventory tables; joining datasets
– Importance: Important (often becomes Critical depending on tooling) – Cloud and infrastructure fundamentals (compute/storage/network)
– Use: interpreting utilization metrics, understanding scaling units and bottlenecks
– Importance: Critical – Monitoring/observability metric literacy
– Use: understanding CPU vs throttling, memory pressure, disk IOPS, latency percentiles
– Importance: Critical – Data quality and reconciliation practices
– Use: validating sources, handling missing data, identifying outliers
– Importance: Important – Basic scripting or automation mindset (even if not heavy coding)
– Use: repeatable report generation, small data transforms
– Importance: Important (language may vary)

Good-to-have technical skills – Python or R for analysis (pandas, notebooks)
– Use: time-series manipulation, forecast experiments, automation
– Importance: Optional (but valuable) – BI dashboarding (Power BI/Tableau/Looker)
– Use: publish self-serve capacity views; drilldowns by service/team/env
– Importance: Important – Cloud billing and cost allocation concepts
– Use: unit cost, showback, tagging, commitments coverage
– Importance: Important (especially in cloud-heavy orgs) – Kubernetes and container resource concepts
– Use: requests/limits, node sizing, cluster autoscaling signals
– Importance: Optional to Important (context-specific) – ITSM basics (incidents/problems/changes)
– Use: linking capacity risks to change tickets, PIRs, and operational processes
– Importance: Optional

Advanced or expert-level technical skills (not required at junior level; progression targets) – Forecasting methods and model evaluation (ARIMA-like approaches, Prophet-style models, confidence intervals, backtesting)
– Use: more robust forecasts and scenario planning
– Importance: Optional (future growth) – Capacity modeling and queueing concepts (Little’s Law basics, saturation vs latency behavior)
– Use: connecting utilization to performance risk and SLOs
– Importance: Optional – Infrastructure as Code literacy (Terraform/CloudFormation)
– Use: understanding provisioning patterns and constraints; not necessarily authoring
– Importance: Optional – Data engineering basics (pipelines, transformations, scheduling, data contracts)
– Use: reliable datasets and automation
– Importance: Optional

Emerging future skills for this role (next 2–5 years) – AI-assisted anomaly detection and forecasting governance
– Use: evaluating AI-generated insights, avoiding false confidence, monitoring drift
– Importance: Important (increasing) – FinOps-informed capacity decisions (unit economics, workload value tiers, policy-based rightsizing)
– Use: balancing cost vs reliability with explicit business context
– Importance: Important – Platform-level capacity policy understanding (guardrails, autoscaling policies, quota management as code)
– Use: enabling consistent scaling controls and preventing misconfiguration
– Importance: Optional to Important (depends on platform maturity)

9) Soft Skills and Behavioral Capabilities

• Analytical thinking and structured problem solving
• Why it matters: capacity problems often present as noisy data with multiple plausible drivers
• How it shows up: breaks down questions into measurable components; tests assumptions

• Strong performance: delivers a clear narrative with evidence, not just charts

• Attention to detail / data discipline

• Why it matters: small errors in filters, time ranges, or units can cause expensive decisions
• How it shows up: validates sources, reconciles totals, documents caveats

• Strong performance: stakeholders trust the numbers and stop “double-checking”

• Communication and data storytelling

• Why it matters: capacity insights must influence actions by engineering and leadership
• How it shows up: concise summaries, clear “so what,” visual clarity, avoids jargon when needed

• Strong performance: recommendations are understood and adopted

• Stakeholder management (junior level)

• Why it matters: demand signals come from other teams; buy-in is required for optimization actions
• How it shows up: asks good questions, follows up, respects time, closes loops

• Strong performance: workload owners respond, share plans, and collaborate

• Curiosity and learning agility

• Why it matters: infrastructure environments vary; new services and metrics appear constantly
• How it shows up: seeks to understand “how the system works,” not only the report format

• Strong performance: quickly ramps on a new platform’s capacity constraints

• Pragmatism and prioritization

• Why it matters: not everything can be measured perfectly; deadlines matter
• How it shows up: focuses on tier-1 services and highest-risk constraints first

• Strong performance: delivers “good enough + accurate + timely,” improves iteratively

• Integrity and transparency about uncertainty

• Why it matters: forecasts are probabilistic; overconfidence causes poor decisions
• How it shows up: states assumptions, confidence levels, and scenario ranges

• Strong performance: leaders can make risk-informed tradeoffs

• Collaboration under pressure (incidents/launches)

• Why it matters: capacity issues can escalate quickly
• How it shows up: responds calmly, supplies evidence fast, avoids blame
• Strong performance: becomes a dependable support partner during critical events

10) Tools, Platforms, and Software

Category	Tool, platform, or software	Primary use	Common / Optional / Context-specific
Cloud platforms	AWS, Azure, Google Cloud	Source of capacity primitives, quotas, utilization, billing	Context-specific (one or more Common depending on org)
Cloud cost management	AWS Cost Explorer / CUR, Azure Cost Management, GCP Billing Export	Spend, usage, commitment utilization, allocation	Common
FinOps platforms	Apptio Cloudability, VMware Aria Cost (CloudHealth), Finout	Normalized cost & usage analytics, showback	Optional
Monitoring / observability	Datadog	Infrastructure/app metrics, dashboards, anomaly views	Common (varies)
Monitoring / observability	Prometheus + Grafana	Metrics collection and visualization (often Kubernetes)	Common (varies)
Monitoring / observability	CloudWatch / Azure Monitor / GCP Cloud Monitoring	Native metrics, alarms, logs	Common
Log analytics	Splunk, Elastic (ELK), Loki	Correlate workload changes, error spikes, scaling events	Optional
Incident/ITSM	ServiceNow, Jira Service Management	Incident/change linkage, reporting workflows	Common in enterprise; Optional in smaller orgs
Collaboration	Confluence, Google Docs, SharePoint	Capacity packs, documentation, runbooks	Common
Communication	Slack, Microsoft Teams	Stakeholder updates, incident collaboration	Common
Work tracking	Jira	Recommendation backlog, tasks, cross-team planning	Common
BI / analytics	Power BI, Tableau, Looker	Executive-ready dashboards and reporting	Common
Data querying	BigQuery, Snowflake, Redshift, Azure Data Explorer	Query telemetry/cost datasets at scale	Context-specific
Data processing	dbt	Transform cost/usage datasets into analytics models	Optional
Spreadsheets	Excel / Google Sheets	Scenario modeling and lightweight forecasts	Common
Scripting	Python (pandas), Jupyter	Automation, analysis, time-series manipulation	Optional (but valuable)
Source control	GitHub / GitLab	Version control for queries, notebooks, docs	Optional to Common
Container orchestration	Kubernetes	Understanding cluster capacity, node pools, requests/limits	Context-specific (common in modern orgs)
Infrastructure inventory	CMDB tooling, cloud asset inventory	Resource inventory and ownership mapping	Context-specific
Automation	Airflow, cron, serverless scheduled jobs	Scheduled refresh of reports and datasets	Optional
Procurement/Vendor	Coupa, Ariba (or internal procurement tools)	Purchase tracking for capacity-related contracts	Context-specific

11) Typical Tech Stack / Environment

Infrastructure environment – Predominantly cloud-based (single cloud or multi-cloud), often with: – Managed compute (VMs, autoscaling groups) – Container platforms (Kubernetes/ECS/AKS/GKE) – Managed databases (RDS/Cloud SQL/Cosmos DB, etc.) – Object storage and block storage – CDN, load balancers, API gateways – In some enterprises: hybrid with on-prem virtualization (VMware), SAN/NAS storage, and dedicated network capacity planning.

Application environment – Microservices and APIs with varying workload patterns: – Always-on services with diurnal patterns – Event-driven services with burst traffic – Batch pipelines with fixed windows – Capacity signals often proxied by: – Requests per second (RPS), queue depth, concurrent users, throughput (MB/s)

Data environment – Telemetry data at high volume (metrics, logs, traces) plus cost and inventory exports. – Typical data sources: – Monitoring metrics APIs – Billing export tables – Resource inventory/CMDB – Tag/label taxonomies for ownership

Security environment – Role-based access controls (RBAC) for cloud and monitoring tools. – Handling of sensitive metadata (resource names, tags, project identifiers, sometimes customer/environment mapping). – Compliance expectations vary; common controls include least privilege and audit logs for access to cost/usage data.

Delivery model – The Junior Capacity Planning Analyst usually operates in an ops + platform engineering environment: – Central Cloud & Infrastructure team provides shared services – Product engineering teams own workloads and are consumers of capacity insights – Work is delivered through recurring reporting cycles and improvement backlogs.

Agile or SDLC context – Not a classic SDLC role, but often uses Agile practices: – Jira tickets for requests and improvements – Sprint-like cadence for automation and dashboard enhancement – Operational review rituals (weekly/monthly)

Scale or complexity context – Complexity comes from: – Many services and teams – Multi-region deployments – Variable workloads and seasonal peaks – Quotas/limits and dependency constraints (e.g., IP exhaustion, shard counts, storage IOPS caps)

Team topology – Typically embedded within or adjacent to: – Infrastructure Operations / SRE – Platform Engineering – FinOps (matrixed) – Junior role often sits in a small capacity/efficiency pod (2–8 people) or as part of a broader operations analytics function.

12) Stakeholders and Collaboration Map

Internal stakeholders – Cloud Infrastructure / Platform Engineering: primary partner; uses insights for scaling, quotas, architecture guardrails. – SRE / Reliability Engineering: uses headroom and saturation signals to protect SLOs; collaborates on incident learnings. – Infrastructure Operations (NOC/IT Ops): uses reports for change planning and day-to-day stability. – Engineering teams (workload owners): provide demand signals; implement rightsizing changes; validate assumptions. – FinOps / Cloud Cost Management: ties capacity actions to spend; tracks savings and commitment strategy. – Architecture: ensures capacity approach aligns with reference architectures and growth roadmaps. – Finance: budgeting/forecasting alignment; informs run-rate and growth-driven spend. – Security: ensures data access controls; sometimes sets constraints affecting scaling choices.

External stakeholders (as applicable) – Cloud vendors / MSP partners: quota increases, contract commitments, capacity advisories (more common in enterprise). – SaaS tooling vendors: monitoring/FinOps platforms where data integrations may require coordination.

Peer roles – Capacity Planning Analyst (mid-level) – FinOps Analyst – SRE / Ops Analyst – Business Operations Analyst (in infrastructure org) – Technical Program Manager (platform)

Upstream dependencies (inputs) – Monitoring/observability telemetry – Cloud billing exports and pricing data – Inventory/CMDB data and tagging coverage – Product launch calendar and engineering roadmaps – Incident logs and PIR outputs

Downstream consumers (outputs) – Platform/ops teams executing scaling and optimization – Leadership reviewing risk and budget posture – Finance/FinOps tracking commitments and savings – Engineering teams planning launches and performance work

Nature of collaboration – Predominantly “advisor + evidence provider.”
– The Junior Capacity Planning Analyst typically does not approve changes, but influences by: – Presenting quantified risk and options – Providing clear recommendations and tradeoffs – Tracking outcomes and closing the loop

Typical decision-making authority – Provides analysis and recommendations; final decisions usually owned by: – Platform Engineering/SRE leads for technical scaling choices – FinOps/Finance for commitment purchases – Engineering owners for workload-level rightsizing changes

Escalation points – Escalate capacity risks to: – Capacity Planning Lead/Manager – SRE on-call lead (for near-term incident risk) – Platform Engineering manager (for quota/architecture constraints) – Escalate data quality issues to: – Observability platform owners – Data platform owners (if telemetry in warehouse) – FinOps tooling admin (billing export problems)

13) Decision Rights and Scope of Authority

Decisions the role can make independently (typical junior scope) – Choose appropriate visualizations and summaries for assigned dashboards within established standards. – Define and maintain report templates for weekly/monthly capacity packs (formatting, clarity improvements). – Prioritize personal backlog of analysis tasks within assigned domain and deadlines. – Implement low-risk automation changes (query optimizations, scheduled refresh adjustments) following team process.

Decisions requiring team approval (capacity/infra analytics team) – Changes to KPI definitions, thresholds, or “official” headroom calculations. – Adding new data sources that affect enterprise reporting or cost allocations. – Publishing new dashboards as a source-of-truth used for executive decisions.

Decisions requiring manager/director/executive approval – Commitment purchases or contract changes (RIs/Savings Plans/CUDs, reserved hardware, colocation expansions). – Major capacity expansions with budget impact (new regions, major cluster expansions, large storage purchases). – Changes that affect production scaling policy or reliability guardrails (autoscaling boundaries, quota ceilings). – Any exception to governance, security, or compliance requirements related to data access.

Budget, architecture, vendor, delivery, hiring, or compliance authority – Budget: no direct authority; may provide inputs and analyses used for budget decisions. – Architecture: no authority; may highlight constraints and recommend options. – Vendors: no contracting authority; may assist with usage analysis. – Delivery: can own delivery of reports and dashboards; does not own infrastructure delivery timelines. – Hiring: none. – Compliance: must comply with data access and reporting policies; may contribute to evidence but does not define compliance policy.

14) Required Experience and Qualifications

Typical years of experience – 0–2 years in an analytical, operations, IT, or engineering-adjacent role (internships included). – Candidates with 2–3 years may still be “junior” if transitioning from another domain and lacking infrastructure context.

Education expectations – Common: Bachelor’s degree in information systems, computer science, engineering, mathematics, economics, or similar analytical field. – Alternative: equivalent practical experience with strong analytical portfolio and evidence of infrastructure literacy.

Certifications (relevant but not mandatory) – Common/Helpful (optional): – FinOps Certified Practitioner (helpful in cloud-heavy orgs) – Cloud fundamentals certs (AWS Cloud Practitioner / Azure Fundamentals / GCP Digital Leader) – Context-specific (optional): – ITIL Foundation (enterprise ITSM environments) – Kubernetes fundamentals (CKA is not expected at junior analyst level)

Prior role backgrounds commonly seen – Operations analyst or NOC analyst with strong reporting skills – Junior data analyst supporting IT or cloud cost reporting – Systems administration intern with strong Excel/SQL – Finance analyst moving into FinOps/capacity (if strong technical curiosity) – SRE/DevOps intern focusing on metrics and dashboards

Domain knowledge expectations – Understanding of: – Utilization vs saturation vs performance – Basic cloud pricing and capacity units (vCPU, GiB, IOPS, throughput, egress) – Common bottlenecks (CPU throttling, memory pressure, storage IOPS limits, network saturation, quotas) – Not expected to be an expert in architecture, but must be able to learn the environment quickly.

Leadership experience expectations – None required. Evidence of ownership, reliability, and proactive communication is preferred.

15) Career Path and Progression

Common feeder roles into this role – IT Operations Analyst / NOC Analyst – Junior Data Analyst (IT analytics, cost analytics) – Cloud Support Associate – Systems/DevOps intern or apprentice focusing on monitoring – Finance/Business analyst moving into FinOps/capacity (with upskilling)

Next likely roles after this role – Capacity Planning Analyst (mid-level): owns forecasts and planning for multiple platforms; leads stakeholder forums. – FinOps Analyst: focuses more heavily on cost allocation, unit economics, commitment strategy, and governance. – SRE / Observability Analyst: specializes in reliability metrics, monitoring strategy, and incident analytics. – Infrastructure Operations Analyst / Technical Program Analyst: broader operational performance reporting and process optimization.

Adjacent career paths – Data & Analytics path: Data Analyst → Analytics Engineer (telemetry/cost) → Data Product Owner (internal platforms) – Platform path: Capacity Analyst → Platform Operations Engineer → SRE (for those who expand technical depth) – Business operations path: Capacity/FinOps Analyst → Cloud Business Operations → Strategic Finance (tech spend)

Skills needed for promotion (to mid-level) – Stronger forecasting and scenario planning (driver-based models, backtesting, uncertainty ranges) – Ability to run cross-functional planning sessions and influence decisions – Deeper understanding of at least one platform domain (Kubernetes, databases, storage, network) – Improved automation (SQL + scripting; reproducible pipelines; documentation) – Ability to connect capacity decisions to business outcomes (SLO risk, cost, launch readiness)

How this role evolves over time – Early: report production + data hygiene + basic insights
– Mid: forecasting ownership + proactive risk management + optimization program tracking
– Advanced: capacity strategy, commitment and quota strategy influence, platform guardrails, and broader operating model ownership

16) Risks, Challenges, and Failure Modes

Common role challenges – Fragmented data sources (metrics in one tool, inventory in another, cost in another) with inconsistent identifiers. – Incomplete tagging/ownership mapping that makes it hard to route recommendations. – Misinterpretation of metrics (averages hiding peaks; CPU % not reflecting throttling; storage capacity vs performance limits). – Rapidly changing infrastructure (new clusters, instance families, migrations) making baselines unstable. – Competing priorities: ad-hoc questions vs recurring reporting vs improvement work.

Bottlenecks – Waiting on workload owners to confirm demand or approve changes. – Lack of access to required datasets due to RBAC or security processes. – Limited observability maturity (missing percentiles, missing high-cardinality labels, low retention). – Manual reporting processes that consume too much time.

Anti-patterns – Treating “utilization” as the only measure, ignoring saturation/performance constraints. – Publishing dashboards without definitions, leading to conflicting interpretations. – Over-recommending rightsizing without understanding workload behavior (causing performance regressions). – Forecasting based purely on linear trends without considering launches, seasonality, or scaling policy changes. – Focusing on cost savings only and ignoring SLO risk (or vice versa).

Common reasons for underperformance – Poor data hygiene and lack of validation (stakeholders lose trust). – Communication that is overly technical or overly vague, lacking decisions and next steps. – Inability to distinguish signal from noise (chasing random variance). – Failure to document assumptions, leading to unrepeatable analyses. – Not building relationships with workload owners; recommendations stall.

Business risks if this role is ineffective – Higher incident frequency due to undetected capacity constraints. – Expensive “emergency scaling” and rushed quota increases. – Persistent infrastructure waste (idle resources, unused commitments). – Poor budget predictability, leading to finance surprises and constrained investment. – Slower product launches due to uncertain platform readiness.

17) Role Variants

By company size – Startup / early growth:
– Role may be blended with FinOps or SRE ops analytics; tooling is lighter; emphasis on quick wins and dashboards. – Mid-size SaaS:
– Clearer cadence (weekly/monthly), stronger collaboration with FinOps, focus on Kubernetes and managed services. – Large enterprise:
– More governance (CAB, ITSM, audit), more complex tagging/showback, hybrid capacity (on-prem + cloud), stronger procurement involvement.

By industry – Consumer/high-traffic digital:
– More peak-event planning, seasonality, and performance sensitivity; stronger emphasis on burst behavior and autoscaling readiness. – B2B SaaS:
– More predictable growth; focus on multi-tenant efficiency, database/storage growth, and commitment optimization. – Internal IT / shared services:
– More chargeback/showback and service catalog capacity; often more ITIL alignment.

By geography – Variation mainly in: – Data residency constraints affecting where telemetry is stored – Vendor availability and procurement cycles – Working hours and on-call expectations
– Core role remains broadly consistent across regions.

Product-led vs service-led company – Product-led: closer partnership with engineering and SRE; demand signals from roadmap and usage analytics. – Service-led / managed services: more contract-driven capacity commitments; SLAs and customer onboarding drive demand.

Startup vs enterprise – Startup: fewer formal rituals; more direct execution; analyst may directly adjust dashboards and scripts without heavy change control. – Enterprise: formal reporting standards, approval workflows, and audit trails; more stakeholders and longer decision cycles.

Regulated vs non-regulated – Regulated: stricter access controls and auditability; more emphasis on documentation and data governance; sometimes less tooling flexibility. – Non-regulated: faster iteration, broader access to experimentation tools.

18) AI / Automation Impact on the Role

Tasks that can be automated (increasingly) – Data extraction, cleaning, and refresh monitoring (automated pipelines with checks). – Automated anomaly detection on utilization and saturation metrics (with alerting and root-cause hints). – Draft narrative generation for weekly/monthly reports (summaries of what changed). – Identification of rightsizing candidates and commitment coverage gaps using heuristic or ML-driven tools. – Forecast generation using packaged time-series models, including scenario variations.

Tasks that remain human-critical – Validating assumptions with workload owners (launch impacts, behavior changes, one-off events). – Interpreting anomalies in context (deployments, feature flags, incidents, customer behavior shifts). – Making tradeoffs explicit (cost vs reliability vs latency) and advising on decision implications. – Governance: ensuring definitions, accountability, and audit-ready documentation. – Prioritization: choosing what matters most given business objectives and tiering.

How AI changes the role over the next 2–5 years – The Junior Capacity Planning Analyst will spend less time on manual report assembly and more time on: – Validating AI-generated findings – Investigating “why” behind model outputs – Translating insights into operational actions and tracking outcomes – Expectations will rise around: – Data quality management (garbage-in/garbage-out risk increases) – Model governance (understanding confidence, drift, false positives) – Faster planning cycles (near-real-time views vs monthly-only)

New expectations caused by AI, automation, or platform shifts – Comfort with “analytics as product” thinking: dashboards and datasets treated as maintained products with SLAs. – More integration with platform autoscaling and policy engines (recommendations feeding into guardrails). – Increased collaboration with FinOps automation (policy-based rightsizing, commitment management workflows).

19) Hiring Evaluation Criteria

What to assess in interviews – Ability to interpret infrastructure metrics and explain what they imply (utilization vs saturation). – Analytical rigor: handling messy data, validating assumptions, reconciling sources. – Communication: summarizing findings for both engineers and non-technical stakeholders. – Practical forecasting thinking: not advanced modeling, but sound approach and humility about uncertainty. – Curiosity and learning: how quickly the candidate can ramp on unfamiliar systems. – Work habits: documentation, repeatability, and ownership of deliverables.

Practical exercises or case studies (recommended) 1. Capacity trend + headroom analysis (60–90 minutes take-home or live) – Provide a CSV of time-series metrics (CPU, memory, requests) and a simple service tiering guide. – Ask candidate to: – Identify trends and anomalies – Estimate current headroom and “days to saturation” under a given growth assumption – Recommend next actions (scale, investigate, do nothing) – Communicate assumptions and confidence 2. Dashboard critique – Show a dashboard with common issues (averages only, unclear time windows, missing percentiles). – Ask candidate to explain what is misleading and how they would improve it. 3. SQL mini-task (15–30 minutes) – Join a usage table to an inventory table to produce utilization by team/service. – Look for basic joins, grouping, filtering, and correctness.

Strong candidate signals – Explains metrics correctly and uses percentiles/peaks appropriately. – Demonstrates data skepticism: checks time ranges, units, missing data, and outliers. – Communicates clearly: “Here’s what changed, here’s why it matters, here’s what I’d do next.” – Makes realistic recommendations (e.g., test rightsizing in lower env, confirm with owner, set guardrails). – Demonstrates a habit of documentation and repeatability.

Weak candidate signals – Over-indexes on pretty charts without validation. – Treats utilization as a single number and ignores variability and constraints. – Can’t explain basic infrastructure concepts (CPU throttling, memory pressure, IOPS limits). – Lacks structure in problem solving; jumps to conclusions.

Red flags – Presents forecasts as certainty; cannot articulate assumptions or confidence. – Suggests aggressive cost cuts without reliability safeguards. – Blames other teams for missing data instead of proposing practical mitigation. – Disregards access control or compliance requirements for telemetry/cost data.

Scorecard dimensions (interview rubric) – Infrastructure & cloud fundamentals – Metrics/observability literacy – Analytical rigor (data validation, reasoning) – SQL and data manipulation – Forecasting approach (basic) – Communication and stakeholder orientation – Ownership, process discipline, and documentation mindset – Culture add: curiosity, pragmatism, integrity with uncertainty

20) Final Role Scorecard Summary

Category	Summary
Role title	Junior Capacity Planning Analyst
Role purpose	Provide accurate capacity visibility, basic forecasting, and actionable insights to balance infrastructure reliability, performance, and cost across cloud and platform services.
Top 10 responsibilities	Weekly capacity snapshots; monthly capacity pack inputs; dashboard maintenance; data collection/validation; basic forecasting; capacity risk register upkeep; optimization candidate identification; commitment utilization tracking; incident/PIR evidence support; stakeholder Q&A and demand intake support.
Top 10 technical skills	Excel/Sheets modeling; time-series/statistics basics; SQL; cloud fundamentals (compute/storage/network); observability metrics literacy; data validation/reconciliation; BI dashboarding; cost & usage concepts; basic scripting mindset (Python optional); documentation of assumptions and definitions.
Top 10 soft skills	Structured problem solving; attention to detail; clear communication; stakeholder management (junior); curiosity/learning agility; prioritization; integrity about uncertainty; collaboration under pressure; pragmatism; ownership and follow-through.
Top tools or platforms	Monitoring (Datadog or Prometheus/Grafana); cloud native metrics (CloudWatch/Azure Monitor/GCP Monitoring); BI (Power BI/Tableau/Looker); spreadsheets; SQL on warehouse (BigQuery/Snowflake/Redshift/ADX); Jira/Confluence; ServiceNow/JSM (context-specific); cloud cost tooling (CUR/Cost Mgmt).
Top KPIs	On-time weekly/monthly reporting; data freshness SLA; data accuracy checks; forecast accuracy (MAPE) for scoped services; tier-1 coverage/headroom visibility; risk register hygiene; recommendation throughput/acceptance; realized savings (tracked); commitment utilization; stakeholder satisfaction.
Main deliverables	Weekly capacity snapshot; monthly capacity planning pack sections; capacity dashboards; forecast workbook/model; capacity risk register; optimization candidate list; commitment utilization tracker; metric definitions/data dictionary; runbook snippets; post-incident capacity evidence packs.
Main goals	30/60/90-day ramp to independent reporting ownership; 6-month improvements in forecast accuracy and automation; 12-month trusted contributor producing decision-grade insights and measurable efficiency/reliability improvements.
Career progression options	Capacity Planning Analyst (mid); FinOps Analyst; SRE/Observability Analyst; Infrastructure Ops Analyst; analytics engineering path (telemetry/cost); platform operations path (with deeper technical upskilling).