<p><strong>Senior DevOps & Infrastructure Engineer</strong></p> <p><strong>Company:</strong> Coherence OS<br> <strong>Location:</strong> Remote (Global)<br> <strong>Compensation:</strong> Equity-Only (Slicing Pie) → Cash at Break-Even</p> <p>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.</p> <p>This role isn’t for someone looking for a job. It’s for someone who wants to <strong>build infrastructure they can stand behind years from now</strong>, alongside a small, serious team that values fairness, clarity, and real ownership.</p> <p>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.</p> <p><strong>About Coherence OS</strong></p> <p>Coherence OS is an AI-native operating system focused on preserving <strong>human meaning, identity, and ethical coherence</strong> in the age of advanced automation.</p> <p>We are building foundational infrastructure intended to support <strong>long-lived, global-scale systems</strong> — not short-term SaaS experiments.</p> <p>This role is for someone who wants to <strong>build the substrate</strong>, not just ship tickets.</p><p></p><p><strong>Company Stage & Visibility</strong><br></p> <p>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.</p> <p>We do not have a public website yet. Full context about the company, mission, and roadmap will be shared during the interview process.</p> <p>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.</p><p><strong><br></strong></p><p><strong><br></strong></p><p><strong>T</strong><strong>he Role</strong></p> <p>We are looking for a <strong>Senior DevOps & Infrastructure Engineer</strong> to own the reliability, security, and scalability of our platform from the ground up.</p> <p>You will be a core operator responsible for ensuring that the system runs cleanly, predictably, and securely — even as complexity increases.</p> <p>This is a <strong>high-trust, high-accountability role</strong>.</p> <p><strong>Compensation (Read Carefully)</strong></p> <p>This role starts as <strong>equity-only</strong>, using the <strong>Slicing Pie model</strong>.</p> <ul> <li>Equity is earned continuously based on <strong>fair market rate × time contributed</strong></li> <li>Contributions are tracked transparently</li> <li>There are <strong>no cliffs, no discretionary grants, and no renegotiation</strong></li> <li>Once Coherence OS reaches <strong>break-even</strong>, the role converts to <strong>market-rate cash compensation</strong></li> <li>Earned equity remains fully owned</li> </ul> <p>This role is not a fit for candidates who require guaranteed salary from day one.</p> <p><strong>What You’ll Own</strong></p> <ul> <li>Cloud infrastructure across <strong>production / staging / development</strong></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> <p><strong>What We’re Looking For</strong></p> <ul> <li><strong>5–8+ years</strong> experience in DevOps / Infrastructure roles</li> <li>Strong experience with <strong>AWS, GCP, or Azure</strong></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> <p><strong>Bonus (Not Required)</strong></p> <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> <p><strong>Who This Role Is For</strong></p> <ul> <li>Senior engineers who want <strong>real ownership</strong></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> <p><strong>Who This Role Is Not For</strong></p> <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> <p><strong>Note:</strong></p> <p>This role is intentionally selective.<br> If this model resonates with you, we would love to hear from you.</p> <p></p> <p><strong>What to Expect in Your First 30 Days</strong></p> <p><strong>Senior DevOps & Infrastructure Engineer — Coherence OS</strong></p> <p><strong>Why This Exists</strong></p> <p>Early-stage work can feel ambiguous when expectations aren’t explicit.<br> This document exists to give you <strong>clarity, context, and autonomy</strong> — without micromanagement.</p> <p>If you’re the kind of engineer who thrives with ownership, this should feel grounding, not constraining.</p> <p><strong>Guiding Principles (How We Work)</strong></p> <ul> <li><strong>Ownership over heroics</strong> — sustainable systems beat clever hacks</li> <li><strong>Calm under pressure</strong> — urgency without panic</li> <li><strong>Clarity over noise</strong> — we prefer clean, documented decisions</li> <li><strong>Fairness in contribution</strong> — Slicing Pie tracks value transparently</li> <li><strong>Build for durability</strong> — not quick demos</li> </ul> <p><strong>Week 1: Orientation & System Understanding</strong></p> <p><strong>Primary focus:</strong> Context, access, and situational awareness</p> <p><strong>What You’ll Do</strong></p> <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> <p><strong>What We’re Looking For</strong></p> <ul> <li>Thoughtful questions</li> <li>Early identification of blind spots</li> <li>Respect for what exists, without hesitation to improve it</li> </ul> <p><strong>No expectation to “fix everything” in Week 1.</strong></p> <p><strong>Week 2: Stabilization & Early Improvements</strong></p> <p><strong>Primary focus:</strong> Reliability, security, and confidence building</p> <p><strong>What You’ll Do</strong></p> <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> <p>You may implement <strong>low-risk, high-leverage fixes</strong> if appropriate.</p> <p><strong>What We’re Looking For</strong></p> <ul> <li>Clear reasoning</li> <li>Bias toward safety and clarity</li> <li>Pragmatic improvements, not rewrites</li> </ul> <p><strong>Week 3: Ownership & Systems Thinking</strong></p> <p><strong>Primary focus:</strong> Moving from observer to owner</p> <p><strong>What You’ll Do</strong></p> <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> <p><strong>What We’re Looking For</strong></p> <ul> <li>Calm confidence</li> <li>Explicit ownership</li> <li>Systems-level thinking</li> </ul> <p><strong>Week 4: Roadmap & Operating Rhythm</strong></p> <p><strong>Primary focus:</strong> Establishing a sustainable operating cadence</p> <p><strong>What You’ll Do</strong></p> <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> <p><strong>What We’re Looking For</strong></p> <ul> <li>Strategic clarity</li> <li>Operational discipline</li> <li>Thoughtful pacing</li> </ul> <p><strong>What You Will <em>Not</em> Be Asked to Do in the First 30 Days</strong></p> <ul> <li>You will <strong>not</strong> be asked to work unsustainable hours</li> <li>You will <strong>not</strong> be expected to fix everything immediately</li> <li>You will <strong>not</strong> be judged on output volume</li> <li>You will <strong>not</strong> be micromanaged</li> </ul> <p>We care more about <strong>sound judgment</strong> than speed.</p> <p><strong>Slicing Pie in Practice (Transparency)</strong></p> <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> <p>If something feels unclear, we address it directly.</p> <p><strong>How We Know This Is Working</strong></p> <p>By the end of 30 days, you should feel:</p> <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> <p>If that’s not true, we treat it as a <strong>system issue</strong>, not a personal failure.</p> <p><strong>Final Note</strong></p> <p>This role exists because infrastructure matters — and because the people who run it matter.</p>