{"schemaVersion":"jobsearcher.job.v1","id":"f1b129ecad114f56a46b6208","url":"https://jobsearcher.com/jobs/f1b129ecad114f56a46b6208","canonicalUrl":"https://jobsearcher.com/jobs/f1b129ecad114f56a46b6208","title":"Senior DevOps & Infrastructure Engineer","description":"Senior DevOps & Infrastructure Engineer\nCompany: Coherence OS\nLocation: Remote (Global)\nCompensation: Equity-Only (Slicing Pie) Cash at Break-Even\nWe'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.\nThis 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.\nWe 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.\nAbout Coherence OS\nCoherence OS is an AI-native operating system focused on preserving human meaning, identity, and ethical coherence in the age of advanced automation.\nWe are building foundational infrastructure intended to support long-lived, global-scale systems — not short-term SaaS experiments.\nThis role is for someone who wants to build the substrate, not just ship tickets.\nCompany Stage & Visibility\n\nCoherence 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.\nWe do not have a public website yet. Full context about the company, mission, and roadmap will be shared during the interview process.\nThis 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.\n\nThe Role\nWe are looking for a Senior DevOps & Infrastructure Engineer to own the reliability, security, and scalability of our platform from the ground up.\nYou will be a core operator responsible for ensuring that the system runs cleanly, predictably, and securely — even as complexity increases.\nThis is a high-trust, high-accountability role.\nCompensation (Read Carefully)\nThis role starts as equity-only, using the Slicing Pie model.\nEquity is earned continuously based on fair market rate × time contributed\nContributions are tracked transparently\nThere are no cliffs, no discretionary grants, and no renegotiation\nOnce Coherence OS reaches break-even, the role converts to market-rate cash compensation\nEarned equity remains fully owned\nThis role is not a fit for candidates who require guaranteed salary from day one.\nWhat You'll Own\nCloud infrastructure across production / staging / development\nCI/CD pipelines and deployment workflows\nSecrets management, IAM, and security practices\nMonitoring, alerting, logging, and performance observability\nInfrastructure cost optimization and reliability\nIncident response and operational discipline\nInfrastructure-related vendor and tooling decisions (in partnership with senior leadership)\nWhat We're Looking For\n5–8+ years experience in DevOps / Infrastructure roles\nStrong experience with AWS, GCP, or Azure\nDeep familiarity with:\nInfrastructure-as-Code\nCI/CD systems\nContainers and orchestration\nA security-first, reliability-first mindset\nCalm, low-ego operator who performs well under pressure\nComfort operating in early-stage, ambiguous environments\nBonus (Not Required)\nExperience supporting AI or ML platforms\nMultilingual background (Spanish, Russian or Arabic a plus)\nPrior early-stage or founder-led team experience\nWho This Role Is For\nSenior engineers who want real ownership\nBuilders comfortable trading short-term cash for long-term upside\nOperators who value clarity, fairness, and responsibility\nPeople who care about building infrastructure that actually matters\nWho This Role Is Not For\nCandidates seeking guaranteed salary immediately\nResume-driven job hoppers\nEngineers uncomfortable with accountability or ambiguity\nNote:\nThis role is intentionally selective.\nIf this model resonates with you, we would love to hear from you.\nWhat to Expect in Your First 30 Days\nSenior DevOps & Infrastructure Engineer — Coherence OS\nWhy This Exists\nEarly-stage work can feel ambiguous when expectations aren't explicit.\nThis document exists to give you clarity, context, and autonomy — without micromanagement.\nIf you're the kind of engineer who thrives with ownership, this should feel grounding, not constraining.\nGuiding Principles (How We Work)\nOwnership over heroics — sustainable systems beat clever hacks\nCalm under pressure — urgency without panic\nClarity over noise — we prefer clean, documented decisions\nFairness in contribution — Slicing Pie tracks value transparently\nBuild for durability — not quick demos\nWeek 1: Orientation & System Understanding\nPrimary focus: Context, access, and situational awareness\nWhat You'll Do\nGet access to:\nCloud environments (prod / staging / dev)\nRepositories and CI/CD pipelines\nMonitoring, logging, and alerting tools\nReview:\nCurrent infrastructure architecture\nDeployment workflows\nKnown risks, bottlenecks, and tech debt\nUnderstand:\nProduct priorities and roadmap context\nHow decisions are made and documented\nHow Slicing Pie contribution tracking works in practice\nWhat We're Looking For\nThoughtful questions\nEarly identification of blind spots\nRespect for what exists, without hesitation to improve it\nNo expectation to “fix everything” in Week 1.\nWeek 2: Stabilization & Early Improvements\nPrimary focus: Reliability, security, and confidence building\nWhat You'll Do\nValidate:\nInfrastructure health and resilience\nCI/CD reliability\nSecrets and access control practices\nIdentify:\nHigh-risk failure points\nGaps in monitoring or alerting\nPropose:\nA short list of prioritized improvements\nClear tradeoffs (cost, complexity, time)\nYou may implement low-risk, high-leverage fixes if appropriate.\nWhat We're Looking For\nClear reasoning\nBias toward safety and clarity\nPragmatic improvements, not rewrites\nWeek 3: Ownership & Systems Thinking\nPrimary focus: Moving from observer to owner\nWhat You'll Do\nBegin acting as the primary owner of:\nInfrastructure decisions\nOperational standards\nIncident response posture\nCollaborate with senior leadership on:\nScalability assumptions\nCost vs. reliability tradeoffs\nTooling or vendor decisions\nDocument:\nKey systems\nDecision rationale\nOperating assumptions\nWhat We're Looking For\nCalm confidence\nExplicit ownership\nSystems-level thinking\nWeek 4: Roadmap & Operating Rhythm\nPrimary focus: Establishing a sustainable operating cadence\nWhat You'll Do\nPresent:\nA 60–90 day infrastructure improvement roadmap\nClear priorities and sequencing\nDefine or refine:\nMonitoring and alerting standards\nIncident response expectations\nInfrastructure documentation norms\nAlign on:\nOngoing time commitment\nNear-term focus areas\nHow and when the role scales in responsibility\nWhat We're Looking For\nStrategic clarity\nOperational discipline\nThoughtful pacing\nWhat You Will Not Be Asked to Do in the First 30 Days\nYou will not be asked to work unsustainable hours\nYou will not be expected to fix everything immediately\nYou will not be judged on output volume\nYou will not be micromanaged\nWe care more about sound judgment than speed.\nSlicing Pie in Practice (Transparency)\nTime and contribution are logged daily\nFair market rate is the anchor — no renegotiation\nEquity accrues continuously and visibly\nQuestions about tracking or fairness are encouraged early\nIf something feels unclear, we address it directly.\nHow We Know This Is Working\nBy the end of 30 days, you should feel:\nOriented, not overwhelmed\nTrusted, not watched\nClear about what you own\nConfident that the compensation model is fair\nIf that's not true, we treat it as a system issue, not a personal failure.\nFinal Note\nThis role exists because infrastructure matters — and because the people who run it matter.","company":"Coherence Os","rawCompany":"coherence os","city":"Remote","state":"OR","isRemote":false,"isActive":false,"createdAt":"2026-08-08T12:55:17.091Z","occupations":[{"code":"15-1299.08","title":"Computer Systems Engineers/Architects","slug":"computer-systems-engineers-architects"},{"code":"15-1252.00","title":"Software Developers","slug":"software-developers"},{"code":"15-1244.00","title":"Network and Computer Systems Administrators","slug":"network-and-computer-systems-administrators"}],"industries":[{"code":"541512","title":"Computer Systems Design Services","slug":"computer-systems-design-services"},{"code":"513210","title":"Software Publishers","slug":"software-publishers"},{"code":"541511","title":"Custom Computer Programming Services","slug":"custom-computer-programming-services"}],"jobPosting":{"@context":"https://schema.org","@type":"JobPosting","title":"Senior DevOps & Infrastructure Engineer","description":"Senior DevOps & Infrastructure Engineer\nCompany: Coherence OS\nLocation: Remote (Global)\nCompensation: Equity-Only (Slicing Pie) Cash at Break-Even\nWe'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.\nThis 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.\nWe 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.\nAbout Coherence OS\nCoherence OS is an AI-native operating system focused on preserving human meaning, identity, and ethical coherence in the age of advanced automation.\nWe are building foundational infrastructure intended to support long-lived, global-scale systems — not short-term SaaS experiments.\nThis role is for someone who wants to build the substrate, not just ship tickets.\nCompany Stage & Visibility\n\nCoherence 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.\nWe do not have a public website yet. Full context about the company, mission, and roadmap will be shared during the interview process.\nThis 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.\n\nThe Role\nWe are looking for a Senior DevOps & Infrastructure Engineer to own the reliability, security, and scalability of our platform from the ground up.\nYou will be a core operator responsible for ensuring that the system runs cleanly, predictably, and securely — even as complexity increases.\nThis is a high-trust, high-accountability role.\nCompensation (Read Carefully)\nThis role starts as equity-only, using the Slicing Pie model.\nEquity is earned continuously based on fair market rate × time contributed\nContributions are tracked transparently\nThere are no cliffs, no discretionary grants, and no renegotiation\nOnce Coherence OS reaches break-even, the role converts to market-rate cash compensation\nEarned equity remains fully owned\nThis role is not a fit for candidates who require guaranteed salary from day one.\nWhat You'll Own\nCloud infrastructure across production / staging / development\nCI/CD pipelines and deployment workflows\nSecrets management, IAM, and security practices\nMonitoring, alerting, logging, and performance observability\nInfrastructure cost optimization and reliability\nIncident response and operational discipline\nInfrastructure-related vendor and tooling decisions (in partnership with senior leadership)\nWhat We're Looking For\n5–8+ years experience in DevOps / Infrastructure roles\nStrong experience with AWS, GCP, or Azure\nDeep familiarity with:\nInfrastructure-as-Code\nCI/CD systems\nContainers and orchestration\nA security-first, reliability-first mindset\nCalm, low-ego operator who performs well under pressure\nComfort operating in early-stage, ambiguous environments\nBonus (Not Required)\nExperience supporting AI or ML platforms\nMultilingual background (Spanish, Russian or Arabic a plus)\nPrior early-stage or founder-led team experience\nWho This Role Is For\nSenior engineers who want real ownership\nBuilders comfortable trading short-term cash for long-term upside\nOperators who value clarity, fairness, and responsibility\nPeople who care about building infrastructure that actually matters\nWho This Role Is Not For\nCandidates seeking guaranteed salary immediately\nResume-driven job hoppers\nEngineers uncomfortable with accountability or ambiguity\nNote:\nThis role is intentionally selective.\nIf this model resonates with you, we would love to hear from you.\nWhat to Expect in Your First 30 Days\nSenior DevOps & Infrastructure Engineer — Coherence OS\nWhy This Exists\nEarly-stage work can feel ambiguous when expectations aren't explicit.\nThis document exists to give you clarity, context, and autonomy — without micromanagement.\nIf you're the kind of engineer who thrives with ownership, this should feel grounding, not constraining.\nGuiding Principles (How We Work)\nOwnership over heroics — sustainable systems beat clever hacks\nCalm under pressure — urgency without panic\nClarity over noise — we prefer clean, documented decisions\nFairness in contribution — Slicing Pie tracks value transparently\nBuild for durability — not quick demos\nWeek 1: Orientation & System Understanding\nPrimary focus: Context, access, and situational awareness\nWhat You'll Do\nGet access to:\nCloud environments (prod / staging / dev)\nRepositories and CI/CD pipelines\nMonitoring, logging, and alerting tools\nReview:\nCurrent infrastructure architecture\nDeployment workflows\nKnown risks, bottlenecks, and tech debt\nUnderstand:\nProduct priorities and roadmap context\nHow decisions are made and documented\nHow Slicing Pie contribution tracking works in practice\nWhat We're Looking For\nThoughtful questions\nEarly identification of blind spots\nRespect for what exists, without hesitation to improve it\nNo expectation to “fix everything” in Week 1.\nWeek 2: Stabilization & Early Improvements\nPrimary focus: Reliability, security, and confidence building\nWhat You'll Do\nValidate:\nInfrastructure health and resilience\nCI/CD reliability\nSecrets and access control practices\nIdentify:\nHigh-risk failure points\nGaps in monitoring or alerting\nPropose:\nA short list of prioritized improvements\nClear tradeoffs (cost, complexity, time)\nYou may implement low-risk, high-leverage fixes if appropriate.\nWhat We're Looking For\nClear reasoning\nBias toward safety and clarity\nPragmatic improvements, not rewrites\nWeek 3: Ownership & Systems Thinking\nPrimary focus: Moving from observer to owner\nWhat You'll Do\nBegin acting as the primary owner of:\nInfrastructure decisions\nOperational standards\nIncident response posture\nCollaborate with senior leadership on:\nScalability assumptions\nCost vs. reliability tradeoffs\nTooling or vendor decisions\nDocument:\nKey systems\nDecision rationale\nOperating assumptions\nWhat We're Looking For\nCalm confidence\nExplicit ownership\nSystems-level thinking\nWeek 4: Roadmap & Operating Rhythm\nPrimary focus: Establishing a sustainable operating cadence\nWhat You'll Do\nPresent:\nA 60–90 day infrastructure improvement roadmap\nClear priorities and sequencing\nDefine or refine:\nMonitoring and alerting standards\nIncident response expectations\nInfrastructure documentation norms\nAlign on:\nOngoing time commitment\nNear-term focus areas\nHow and when the role scales in responsibility\nWhat We're Looking For\nStrategic clarity\nOperational discipline\nThoughtful pacing\nWhat You Will Not Be Asked to Do in the First 30 Days\nYou will not be asked to work unsustainable hours\nYou will not be expected to fix everything immediately\nYou will not be judged on output volume\nYou will not be micromanaged\nWe care more about sound judgment than speed.\nSlicing Pie in Practice (Transparency)\nTime and contribution are logged daily\nFair market rate is the anchor — no renegotiation\nEquity accrues continuously and visibly\nQuestions about tracking or fairness are encouraged early\nIf something feels unclear, we address it directly.\nHow We Know This Is Working\nBy the end of 30 days, you should feel:\nOriented, not overwhelmed\nTrusted, not watched\nClear about what you own\nConfident that the compensation model is fair\nIf that's not true, we treat it as a system issue, not a personal failure.\nFinal Note\nThis role exists because infrastructure matters — and because the people who run it matter.","datePosted":"2026-08-08T12:55:17.091Z","dateModified":"2026-08-08T12:55:17.091Z","hiringOrganization":{"@type":"Organization","name":"Coherence Os","sameAs":"https://jobsearcher.com"},"jobLocation":{"@type":"Place","address":{"@type":"PostalAddress","addressLocality":"Remote","addressRegion":"OR","addressCountry":"US"}},"identifier":{"@type":"PropertyValue","name":"JobSearcher","value":"f1b129ecad114f56a46b6208"},"url":"https://jobsearcher.com/jobs/f1b129ecad114f56a46b6208"}}