Job Title: Senior Backend Engineer (or Senior Full-Stack Engineer) Company Name: Coherence OS Job Url: https://coherence-os-inc.breezy.hr/p/d6d2548a4893-senior-backend-engineer-or-senior-full-stack-engineer?source=remotive Job Description: Company Website Coherence OS Senior Backend Engineer (or Senior Full-Stack Engineer) El Dorado Hills, CA - Remote (Any Location)Full-Time$150k - $190k / year Job OpeningsSenior Backend Engineer (or Senior Full-Stack Engineer) Apply To Position Use My Indeed Resume Apply Using LinkedIn Senior Backend Engineer (or Senior Full-Stack Engineer) Company: Coherence OS Location: Remote Compensation: Equity-Only (Slicing Pie) → Cash at Break-Even We’re building Coherence OS because we believe the future of AI systems depends on whether we design them with clarity, restraint, and respect for human meaning. This role is for engineers who take pride in clean execution — who understand that long-lived systems are built by people who care deeply about correctness, maintainability, and shared responsibility. We use the Slicing Pie model because it’s the fairest way we know to align contribution and ownership. If that principle resonates with you — not as a gamble, but as a value — you’ll likely feel aligned here. About Coherence OS Coherence OS builds AI-driven systems that prioritize human identity, ethical alignment, and long-term societal impact. We are building infrastructure meant to last — systems designed for clarity, integrity, and scale, not quick wins. The Role We are looking for a Senior Backend Engineer (or Senior Full-Stack Engineer) to help implement and evolve the core backend systems that power Coherence OS. This role focuses on clean execution under senior architectural guidance — translating system intent into reliable, maintainable software. 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. Compensation (Read Carefully) This role starts as equity-only, using the Slicing Pie model. Equity accrues based on fair market rate × time contributed Contributions are tracked transparently No cliffs, no arbitrary grants, no renegotiation Upon reaching company break-even, the role converts to market-rate cash compensation Earned equity remains fully owned This role is not a fit for candidates who require guaranteed salary from day one. What You’ll Do Build backend services and APIs that support core product functionality Integrate AI and data services into production workflows Implement features under defined architectural guidance Maintain clean abstractions, documentation, and code quality Collaborate with engineering, evaluation, and product stakeholders Contribute to system reliability, performance, and maintainability What We’re Looking For 5+ years backend or full-stack engineering experience Strong experience designing and implementing APIs Experience integrating AI or ML services Pragmatic, execution-oriented mindset Comfort working within architectural constraints Calm, collaborative, low-ego working style Bonus (Optional) Multilingual background (Spanish, Russian or Arabic a plus) Prior experience on early-stage or research-adjacent teams Who This Role Is For Senior engineers who enjoy building well-structured systems People who value fairness and proportional ownership Builders comfortable with ambiguity, but disciplined in execution Who This Role Is Not For Candidates seeking guaranteed salary immediately Engineers who resist architectural direction People uncomfortable with shared ownership models WHAT TO EXPECT IN THE FIRST 30 DAYS Purpose This exists to make expectations explicit and reduce unnecessary ambiguity. Week 1 — Context & Orientation Access to codebase, services, and documentation Review existing backend architecture and workflows Understand how features flow from design to implementation Learn how Slicing Pie contribution tracking works No expectation of major output. Week 2 — Early Contributions Begin implementing well-scoped backend tasks Integrate or extend existing APIs Identify areas where abstractions or documentation can improve Ask questions early and often Week 3 — Ownership Within Scope Take ownership of specific services or workflows Improve code quality, tests, or documentation Collaborate closely with senior engineering leadership Make thoughtful implementation tradeoffs Week 4 — Rhythm & Roadmap Establish a sustainable working cadence Align on near-term priorities Clarify how responsibility may expand over time Confirm mutual fit (technical, cultural, and financial) What You Will Not Be Expected to Do Rewrite the system Work unsustainable hours Guess at priorities without guidance Over-optimize prematurely Success Looks Like Clean, reliable contributions Clear communication Growing confidence and trust Alignment on fairness and ownership Powered bybreezy