Job Title: Platform Engineering Lead (Integration & Delivery) Company Name: Betwixt Job Url: https://www.linkedin.com/jobs/search/?currentJobId=4371571179&distance=25.0&f_AL=true&f_TPR=r10000&f_WT=2&geoId=103644278&keywords=software%20engineer&origin=JOB_SEARCH_PAGE_JOB_FILTER Job Description: Platform Engineering Lead (Integration & Delivery) Betwixt · United States (Remote) Easy Apply Save Save Platform Engineering Lead (Integration & Delivery) at Betwixt Show more options Your profile is missing required qualifications Show match details Help me update my profile BETA Is this information helpful? Get personalized tips to stand out to hirers Find jobs where you’re a top applicant and tailor your resume with the help of AI. Try Premium for PKR0 Meet the hiring team Michael Nylif 3rd 🧑‍💻Making AI Work Better @ Betwixt Job poster Message About the job Betwixt is building an “agent OS” style platform—lots of services, lots of capability, and now we need someone to bring it all together into a cohesive product that ships locally (desktop + local services) and in the cloud (web app + managed services). We’re a team of 3. This role is for someone who loves turning “a bunch of repos” into one integrated, repeatable, boring-to-deploy system. What you’ll own You’ll lead the integration and delivery layer across Betwixt—how services connect, how configs work, and how everything runs in: Local mode (desktop app + local services) Hosted/web mode (web app + backend) Cloud mode (GitOps/IaC, environments, releases) What you’ll build A single “Betwixt distribution”: predictable, versioned, and reproducible Standard service patterns (API contracts, auth flow wiring, config conventions, migrations, health checks) Local one-command bootstrap (dev + runtime): “clone → run → works” Release + packaging pipeline (containers, installers, charts, compose/helm—whatever is best) Environment management (dev/stage/prod), secrets strategy, and sane defaults Docs engineers actually follow (not wiki-sprawl) Your day-to-day (hands-on) Pull multiple repos into a unified integration plan Define interfaces and eliminate “tribal knowledge” configs Create a consistent runtime story (local orchestration + cloud orchestration) Improve CI/CD so releases are repeatable and traceable Partner directly with the founders to make product decisions practical What we’re looking for You’re probably a Staff/Principal-level builder who has done some version of this before. Must-have experience: Integrating multiple services/repos into a cohesive platform Shipping reliable local dev + local runtime (containers, compose/helm, service supervisors, etc.) CI/CD + release thinking: versioning, artifacts, compatibility, rollback Strong systems instincts: debugging distributed systems, network/auth/config issues Comfort in a small team: you design it and build it Nice-to-haves (not required): Rust and/or React familiarity (you don’t need to be a wizard in both) GitOps (ArgoCD), Kubernetes (k3s), IaC (Terraform/OpenTofu) Desktop app packaging (Tauri/Electron) + bundling local services Observability (logs/metrics/tracing) and security hygiene (secrets, signing) What success looks like 30 days: map repos + dependencies, standardize config patterns, first integrated “runs locally” path 60 days: stable local bootstrap + unified service orchestration, first release pipeline for a full stack build 90 days: repeatable releases across local + cloud, compatibility/versioning strategy, docs + onboarding that reduce founder involvement Why this role is fun You’ll have real leverage. This isn’t “keep the cluster alive.” It’s make the whole platform shippable.