Senior DevOps & Infrastructure Engineer

June 22, 2026

Senior DevOps & Infrastructure Engineer Company: Coherence OS Location: Remote (Global) Compensation: Equity-Only (Slicing Pie) → Cash at Break-Even We’re building Coherence OS because we believe the next era of technology requires more than speed and scale — it requires meaning, integrity, and systems that hold over time. This role isn’t for someone looking for a job. It’s for someone who wants to build infrastructure they can stand behind years from now, alongside a small, serious team that values fairness, clarity, and real ownership. We use the Slicing Pie model because it’s the only compensation system we’ve found that actually treats people like adults: contribution in equals ownership earned, dollar for dollar. If that resonates with you — not as a gamble, but as a principle — you’ll probably feel at home here. About Coherence OS Coherence OS is an AI-native operating system focused on preserving human meaning, identity, and ethical coherence in the age of advanced automation. We are building foundational infrastructure intended to support long-lived, global-scale systems — not short-term SaaS experiments. This role is for someone who wants to build the substrate, not just ship tickets.Company Stage & Visibility Coherence OS is in its earliest build phase. We are intentionally operating with a minimal public footprint while core systems, filings, and internal foundations are being finalized. We do not have a public website yet. Full context about the company, mission, and roadmap will be shared during the interview process. This role is part of the initial engineering team and is best suited for candidates who are comfortable joining early, helping shape foundational systems, and building before everything is public. The Role We are looking for a Senior DevOps & Infrastructure Engineer to own the reliability, security, and scalability of our platform from the ground up. You will be a core operator responsible for ensuring that the system runs cleanly, predictably, and securely — even as complexity increases. This is a high-trust, high-accountability role. Compensation (Read Carefully) This role starts as equity-only, using the Slicing Pie model. <ul> <li>Equity is earned continuously based on fair market rate × time contributed</li> <li>Contributions are tracked transparently</li> <li>There are no cliffs, no discretionary grants, and no renegotiation</li> <li>Once Coherence OS reaches break-even, the role converts to market-rate cash compensation</li> <li>Earned equity remains fully owned</li> </ul> This role is not a fit for candidates who require guaranteed salary from day one. What You’ll Own <ul> <li>Cloud infrastructure across production / staging / development</li> <li>CI/CD pipelines and deployment workflows</li> <li>Secrets management, IAM, and security practices</li> <li>Monitoring, alerting, logging, and performance observability</li> <li>Infrastructure cost optimization and reliability</li> <li>Incident response and operational discipline</li> <li>Infrastructure-related vendor and tooling decisions (in partnership with senior leadership)</li> </ul> What We’re Looking For <ul> <li>5–8+ years experience in DevOps / Infrastructure roles</li> <li>Strong experience with AWS, GCP, or Azure</li> <li>Deep familiarity with:</li> <ul> <li>Infrastructure-as-Code</li> <li>CI/CD systems</li> <li>Containers and orchestration</li> </ul> <li>A security-first, reliability-first mindset</li> <li>Calm, low-ego operator who performs well under pressure</li> <li>Comfort operating in early-stage, ambiguous environments</li> </ul> Bonus (Not Required) <ul> <li>Experience supporting AI or ML platforms</li> <li>Multilingual background (Spanish, Russian or Arabic a plus)</li> <li>Prior early-stage or founder-led team experience</li> </ul> Who This Role Is For <ul> <li>Senior engineers who want real ownership</li> <li>Builders comfortable trading short-term cash for long-term upside</li> <li>Operators who value clarity, fairness, and responsibility</li> <li>People who care about building infrastructure that actually matters</li> </ul> Who This Role Is Not For <ul> <li>Candidates seeking guaranteed salary immediately</li> <li>Resume-driven job hoppers</li> <li>Engineers uncomfortable with accountability or ambiguity</li></ul> <ul> </ul> Note: This role is intentionally selective. If this model resonates with you, we would love to hear from you. What to Expect in Your First 30 Days Senior DevOps & Infrastructure Engineer — Coherence OS Why This Exists 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. Guiding Principles (How We Work) <ul> <li>Ownership over heroics — sustainable systems beat clever hacks</li> <li>Calm under pressure — urgency without panic</li> <li>Clarity over noise — we prefer clean, documented decisions</li> <li>Fairness in contribution — Slicing Pie tracks value transparently</li> <li>Build for durability — not quick demos</li> </ul> Week 1: Orientation & System Understanding Primary focus: Context, access, and situational awareness What You’ll Do <ul> <li>Get access to:</li> <ul> <li>Cloud environments (prod / staging / dev)</li> <li>Repositories and CI/CD pipelines</li> <li>Monitoring, logging, and alerting tools</li> </ul> <li>Review:</li> <ul> <li>Current infrastructure architecture</li> <li>Deployment workflows</li> <li>Known risks, bottlenecks, and tech debt</li> </ul> <li>Understand:</li> <ul> <li>Product priorities and roadmap context</li> <li>How decisions are made and documented</li> <li>How Slicing Pie contribution tracking works in practice</li> </ul> </ul> What We’re Looking For <ul> <li>Thoughtful questions</li> <li>Early identification of blind spots</li> <li>Respect for what exists, without hesitation to improve it</li> </ul> No expectation to “fix everything” in Week 1. Week 2: Stabilization & Early Improvements Primary focus: Reliability, security, and confidence building What You’ll Do <ul> <li>Validate:</li> <ul> <li>Infrastructure health and resilience</li> <li>CI/CD reliability</li> <li>Secrets and access control practices</li> </ul> <li>Identify:</li> <ul> <li>High-risk failure points</li> <li>Gaps in monitoring or alerting</li> </ul> <li>Propose:</li> <ul> <li>A short list of prioritized improvements</li> <li>Clear tradeoffs (cost, complexity, time)</li> </ul> </ul> You may implement low-risk, high-leverage fixes if appropriate. What We’re Looking For <ul> <li>Clear reasoning</li> <li>Bias toward safety and clarity</li> <li>Pragmatic improvements, not rewrites</li> </ul> Week 3: Ownership & Systems Thinking Primary focus: Moving from observer to owner What You’ll Do <ul> <li>Begin acting as the primary owner of:</li> <ul> <li>Infrastructure decisions</li> <li>Operational standards</li> <li>Incident response posture</li> </ul> <li>Collaborate with senior leadership on:</li> <ul> <li>Scalability assumptions</li> <li>Cost vs. reliability tradeoffs</li> <li>Tooling or vendor decisions</li> </ul> <li>Document:</li> <ul> <li>Key systems</li> <li>Decision rationale</li> <li>Operating assumptions</li> </ul> </ul> What We’re Looking For <ul> <li>Calm confidence</li> <li>Explicit ownership</li> <li>Systems-level thinking</li> </ul> Week 4: Roadmap & Operating Rhythm Primary focus: Establishing a sustainable operating cadence What You’ll Do <ul> <li>Present:</li> <ul> <li>A 60–90 day infrastructure improvement roadmap</li> <li>Clear priorities and sequencing</li> </ul> <li>Define or refine:</li> <ul> <li>Monitoring and alerting standards</li> <li>Incident response expectations</li> <li>Infrastructure documentation norms</li> </ul> <li>Align on:</li> <ul> <li>Ongoing time commitment</li> <li>Near-term focus areas</li> <li>How and when the role scales in responsibility</li> </ul> </ul> What We’re Looking For <ul> <li>Strategic clarity</li> <li>Operational discipline</li> <li>Thoughtful pacing</li> </ul> What You Will Not Be Asked to Do in the First 30 Days <ul> <li>You will not be asked to work unsustainable hours</li> <li>You will not be expected to fix everything immediately</li> <li>You will not be judged on output volume</li> <li>You will not be micromanaged</li> </ul> We care more about sound judgment than speed. Slicing Pie in Practice (Transparency) <ul> <li>Time and contribution are logged daily</li> <li>Fair market rate is the anchor — no renegotiation</li> <li>Equity accrues continuously and visibly</li> <li>Questions about tracking or fairness are encouraged early</li> </ul> If something feels unclear, we address it directly. How We Know This Is Working By the end of 30 days, you should feel: <ul> <li>Oriented, not overwhelmed</li> <li>Trusted, not watched</li> <li>Clear about what you own</li> <li>Confident that the compensation model is fair</li> </ul> If that’s not true, we treat it as a system issue, not a personal failure. Final Note This role exists because infrastructure matters — and because the people who run it matter.

Back to blog

DISCLAIMER