Software Engineer - Distributed Systems Control Plane — Cofounder
Listed on 2026-02-16
-
Engineering
Software Engineer, Systems Engineer
Software Engineer - Distributed Systems Control Plane— Cofounder
Equity Only (Pre-funding, No Initial Salary). Role:
Part-time.
We’re building a patent‑pending pre‑execution governance layer for regulated and distributed systems.
This role is equity‑based
. We are pre‑revenue and entering our first pre‑seed raise. We’re looking for a Control Plane / Distributed Systems Engineer to join as a cofounder and take full ownership of the product core. This is not a feature role, not a UI role, and not a “move fast and patch later” system. If this hire is wrong, everything downstream breaks.
You are the final technical authority on the execution layer.
You will:
- Design and own the execution governance architecture
- Establish hard in variants the system will never violate
- Decide what executes, what is rejected, and why
- Kill feature creep early—publicly and calmly
- Set the rules every other engineer must build under
This role has veto power
.
- Pre‑execution validation and gating services
- Deterministic execution flows (no “best‑effort” logic)
- Policy enforcement before runtime
- Service‑to‑service trust boundaries
- Infrastructure‑agnostic control logic
If you’ve designed systems where failure modes matter
, you’ll feel at home.
We’re looking for depth, not keywords. You should have real experience with several of the following:
- Distributed systems and backend architecture
- Control planes, schedulers, or orchestration layers
- Strongly opinionated API and service design
- Stateless vs stateful execution trade‑offs
- Languages such as Go, Rust, Java, or equivalent
- Message‑driven or request‑driven systems (gRPC, queues, streams)
You’ve shipped systems where correctness beat speed
.
- “No — that violates the execution model.”
- “This doesn’t belong in the control layer.”
- “That feature creates an implicit policy leak.”
- “We don’t support that — by design.”
- Not a mobile role
- Not a frontend role
- Not a blockchain‑hype role
- Not a Dev Ops‑only role
- Not a consensus‑protocol research post
You won’t be polishing UIs or chasing frameworks.
Why This Role Exists FirstWithout this hire, you get:
- Governance bolted on after the fact
- Fragile systems that work… until they don’t
This role prevents all of that.
Who You’ll Work With- Founder (product & governance)
- UI and integration engineers downstream
You define the ground they build on.
Location & Structure- Remote‑first
- Cofounder‑level ownership
- Equity meaningful enough to care
- Long‑term commitment, not contract churn
If you’ve built systems that other systems must obey
, we want to hear from you.
Apply via Linked In or send your CV to .
If you’re looking to experiment, iterate casually, or “see how it goes” — this won’t be a fit.
#J-18808-LjbffrTo Search, View & Apply for jobs on this site that accept applications from your location or country, tap here to make a Search: