Senior DevOps & Infrastructure Engineer

Cloud infrastructure across production / staging / development

CI/CD pipelines and deployment workflows

Secrets management, IAM, and security practices

Monitoring, alerting, logging, and performance observability

Infrastructure cost optimization and reliability

Incident response and operational discipline

Infrastructure-related vendor and tooling decisions (in partnership with senior leadership)

5–8+ years experience in DevOps / Infrastructure roles

Strong experience with AWS, GCP, or Azure

Deep familiarity with:

Infrastructure-as-Code

CI/CD systems

Containers and orchestration

A security-first, reliability-first mindset

Calm, low-ego operator who performs well under pressure

Comfort operating in early-stage, ambiguous environments

Experience supporting AI or ML platforms

Multilingual background (Spanish, Russian or Arabic a plus)

Prior early-stage or founder-led team experience

Senior engineers who want real ownership

Builders comfortable trading short-term cash for long-term upside

Operators who value clarity, fairness, and responsibility

People who care about building infrastructure that actually matters

Candidates seeking guaranteed salary immediately

Resume-driven job hoppers

Engineers uncomfortable with accountability or ambiguity

This role is intentionally selective. If this model resonates with you, we would love to hear from you.

Early-stage work can feel ambiguous when expectations aren’t explicit. This document exists to give you clarity, context, and autonomy — without micromanagement.

If you’re the kind of engineer who thrives with ownership, this should feel grounding, not constraining.

Ownership over heroics — sustainable systems beat clever hacks

Calm under pressure — urgency without panic

Clarity over noise — we prefer clean, documented decisions

Fairness in contribution — Slicing Pie tracks value transparently

Build for durability — not quick demos

Primary focus: Context, access, and situational awareness

Get access to:

Cloud environments (prod / staging / dev)

Repositories and CI/CD pipelines

Monitoring, logging, and alerting tools

Review:

Current infrastructure architecture

Deployment workflows

Known risks, bottlenecks, and tech debt

Understand:

Product priorities and roadmap context

How decisions are made and documented

How Slicing Pie contribution tracking works in practice

Thoughtful questions

Early identification of blind spots

Respect for what exists, without hesitation to improve it

Primary focus: Reliability, security, and confidence building

Validate:

Infrastructure health and resilience

CI/CD reliability

Secrets and access control practices

Identify:

High-risk failure points

Gaps in monitoring or alerting

Propose:

A short list of prioritized improvements

Clear tradeoffs (cost, complexity, time)

You may implement low-risk, high-leverage fixes if appropriate.

Clear reasoning

Bias toward safety and clarity

Pragmatic improvements, not rewrites

Primary focus: Moving from observer to owner

Begin acting as the primary owner of:

Infrastructure decisions

Operational standards

Incident response posture

Collaborate with senior leadership on:

Scalability assumptions

Cost vs. reliability tradeoffs

Tooling or vendor decisions

Document:

Key systems

Decision rationale

Operating assumptions

Calm confidence

Explicit ownership

Systems-level thinking

Primary focus: Establishing a sustainable operating cadence

Present:

A 60–90 day infrastructure improvement roadmap

Clear priorities and sequencing

Define or refine:

Monitoring and alerting standards

Incident response expectations

Infrastructure documentation norms

Align on:

Ongoing time commitment

Near-term focus areas

How and when the role scales in responsibility

Strategic clarity

Operational discipline

Thoughtful pacing

You will not be asked to work unsustainable hours

You will not be expected to fix everything immediately

You will not be judged on output volume

You will not be micromanaged

We care more about sound judgment than speed.

Time and contribution are logged daily

Fair market rate is the anchor — no renegotiation

Equity accrues continuously and visibly

Questions about tracking or fairness are encouraged early

If something feels unclear, we address it directly.

By the end of 30 days, you should feel:

Oriented, not overwhelmed

Trusted, not watched

Clear about what you own

Confident that the compensation model is fair

If that’s not true, we treat it as a system issue , not a personal failure.

This role exists because infrastructure matters — and because the people who run it matter.