We measure success by results and alignment. Here is how we define a "win" for this role over your first year:

After 90 Days

• The Foundation — You have developed deep familiarity with the current platform architecture, active technical initiatives, and existing pain points across the environment.

• The Integration — You have built strong working relationships with Engineering and Cloud Operations, and are engaging confidently in cross-functional and business-facing conversations.

• The Contribution — You have completed your first scoped architectural spike or initiative, documented your findings, and handed off clear, well-defined work to engineers.

After 1 Year

• Your Impact — Platform reliability, security posture, and observability have measurably improved, including elevated monitoring and telemetry practices across the environment.

• Your Growth — You have mentored engineers on Azure architecture best practices and are recognized as the go-to technical authority for the platform.

• Your Influence — You have established reusable architectural patterns and evaluated AI-assisted development practices that improved team velocity and delivery quality

Required Skills (The Non-Negotiables)

• Years of Experience — 8+ years of cloud engineering and architecture experience.

• Role-Specific Mastery — Deep, intimate knowledge of Microsoft Azure — its monitoring, automation, and platform services — with strong experience designing cloud solutions and validating approaches through focused, time-boxed spikes.

• Operational Excellence — Demonstrated ability to break down complex, ambiguous work into scoped, delegable pieces and lead delivery through others; hands-on experience with infrastructure-as-code (Bicep or Terraform) and scripting (PowerShell, Python).

• Communication — Excellent written and spoken English, with the confidence to engage and influence in business-facing and cross-functional conversations with both technical and non-technical stakeholders.

• Collaboration — Experience partnering with cross-functional and account teams to surface technical considerations early and help shape what gets built and why.

• Problem Solving — A pattern-oriented mindset — able to generalize individual requests into reusable solutions — along with working knowledge of Azure Monitor, Log Analytics, and KQL to strengthen platform observability

Nice to Have (The Bonus Points)

• Multi-Tenant / MSP Experience — Experience supporting multiple clients or tenants from a shared platform.

• Security & Compliance — Familiarity with security and compliance frameworks relevant to managed cloud services, including Microsoft Sentinel.

• CI/CD — Experience with CI/CD pipelines, ideally Azure DevOps.

• Certifications — Relevant Azure certifications (e.g., Azure Solutions Architect Expert).

These 'Core Three' represent the heartbeat of Atmosera. They are the behaviors and attributes we align to every day, defining how we interact, solve problems, and celebrate our wins together. This is simply who we are at our best.

• Humble (Low Ego, High Impact) — We share credit easily, admit when we're wrong, and view every mistake as a data point for growth.

• Hungry (Internal Drive) — We have a natural bias for action. We don't wait for permission to solve a problem or find a better way to do things.

• Mindful (Intentional Awareness) — We are conscious of our impact on the team. We listen more than we speak and respond to challenges with empathy and situational awareness.

1. Talent Screen: (30 mins) A conversation about your background and the role mission.

2. The Impact & Attributes Assessment: (45 mins) The "How" (Cultural DNA and The Core Three).

3. Collaborator Loop: (60-90 mins) The "What" (Required Skills and Core Capabilities). This stage may require a presentation or work sample.

4. Final Alignment: (30 mins) Closing conversation with Leadership.