Employer profile
Dedalus Labs
4 open roles indexed with location, benefit, and apply-link signals where available.
Open roles
Showing the most recent indexed roles for this employer.
-
Platform Engineer
San Francisco | OnSite
onsite $120K-$250KPlatform Engineer San Francisco | OnSite About the role Dedalus Labs builds persistent computers for AI agents. Our flagship product, Dedalus Machines, gives agents an isolated environment where they can run software, keep files and state, and work over time. You'll own the internal platform engineers use to build, test, release, and operate our software. Your focus is CI/CD, GitHub Actions, build systems, release pipelines, and observability. A source change should move through a reliable pipeline, and a production failure should lead us to the relevant request, resource, release, and evidence. You'll work across a large, fast-moving codebase to remove slow feedback, manual release steps, and gaps in visibility. Success means engineers ship safely with less coordination and can turn platform telemetry into concrete fixes. What you'll work on Build and CI infrastructure. Own GitHub Actions workflows, runners, test execution, build caching, and artifact storage. Reduce queue time, repeated work, flaky failures, and local/CI differences. Measure build latency and reliability as the codebase grows. Our open-source tooling includes Bessemer (BSMR) , our build system, and Hollywood , which generates GitHub Actions from typed TypeScript definitions and runs actions locally. Improve the tools themselves when their behavior limits the development workflow. Release engineering. Build repeatable pipelines for artifact publishing, staging validation, promotion, production rollout, and rollback. Connect every running version to its source, build inputs, and tested artifact. Make failed releases diagnosable and recovery procedures testable. Platform observability. Build consistent instrumentation across services and infrastructure. Correlate logs, metrics, traces, errors, and
-
Platform Engineer Intern / Co-op
San Francisco | OnSite
onsite Salary not disclosedPlatform Engineer Intern / Co-op San Francisco | OnSite About the role Dedalus Labs builds persistent computers for AI agents. Our flagship product, Dedalus Machines, gives agents an isolated environment where they can run software, keep files and state, and work over time. You'll improve the internal platform engineers use to build, test, release, and understand our software. This means GitHub Actions, build systems, release pipelines, and observability: collecting and connecting logs, metrics, traces, and errors so we can follow an operation across the platform and turn failures or regressions into specific fixes. Our open-source tooling includes Bessemer (BSMR) , our build system, and Hollywood , which generates GitHub Actions from typed TypeScript definitions and runs actions locally. About the internship This is an evergreen opening. We review applications on an ongoing basis. Internships and co-ops last 3-9 months, depending on your school and co-op program. Show us that you can learn something difficult, finish a working version, and improve it when the first approach fails. Prior production ownership is not required. You should be able to explain your project's hardest bug, limits, and your contribution. Work you might take on CI/CD and builds: Improve a GitHub Actions workflow, investigate a flaky test, reduce runner queue time, or fix a build-cache miss. Measure the effect on build time and reliability. Release pipelines: Automate artifact publishing, staging checks, release promotion, or rollback verification. Make it possible to trace a running version back to its source and build. Observability: Instrument a service
-
Systems Engineer Intern / Co-op
San Francisco | OnSite
onsite Salary not disclosedSystems Engineer Intern / Co-op San Francisco | OnSite About the role Dedalus Labs builds persistent computers for AI agents. Our flagship product, Dedalus Machines, gives agents an isolated environment where they can run software, keep files and state, and work over time. You'll implement and debug the software that creates, schedules, and runs Machines. Projects can involve the control plane, Kubernetes controllers and operators, or our Rust virtual machine monitor (VMM), the software that runs virtual machines. We want someone curious about how a system behaves when requests overlap, a node fails, or a process stops halfway through an operation. About the internship This is an evergreen opening. We review applications on an ongoing basis. Internships and co-ops last 3-9 months, depending on your school and co-op program. Show us that you can learn something difficult, finish a working version, and improve it when the first approach fails. Prior production ownership is not required. You should be able to explain your project's hardest bug, limits, and your contribution. Work you might take on Kubernetes and orchestration: Improve a controller or operator and test how it reconciles desired and actual resource state. Investigate scheduling, pod lifecycle, networking, or recovery after a node failure. Control-plane correctness: Fix a resource-lifecycle bug involving retries, cancellation, concurrent requests, or cleanup. Write a test that reproduces the failure and verifies the repair. Runtime and storage: Improve VM startup, snapshot restore, memory use, or an I/O path. Establish a baseline and measure the change on the
-
Systems Engineer
San Francisco | OnSite
onsite Salary not disclosedSystems Engineer San Francisco | OnSite About the role Dedalus Labs builds persistent computers for AI agents. Our flagship product, Dedalus Machines, gives agents an isolated environment where they can run software, keep files and state, and work over time. You'll build the control plane and runtime that create, schedule, isolate, and recover our customers' Machines. The work spans Kubernetes orchestration, distributed resource lifecycles, and our Rust virtual machine monitor (VMM), the software that runs each virtual machine. We welcome depth in the control plane or runtime, with room to work across both. You'll carry a change from design through implementation, verification, rollout, and operation. The central questions are whether the system remains correct under concurrency and failure, and how efficiently it uses compute, memory, storage, and the network. What you'll work on Kubernetes and orchestration. Build and debug controllers and operators, reconciliation loops, scheduling, and workload lifecycles. Reason about desired and observed state, retries, resource cleanup, and recovery after node or network failures. Trace behavior through Kubernetes APIs, networking, storage, and the underlying Linux host. Control-plane services. Implement the APIs and services that create, schedule, and manage Machines. Design durable state transitions and clear ownership so concurrent requests, cancellation, and partial failures cannot leave resources in an incorrect state. Rust VMM and runtime. Work on virtualization, guest memory, devices, and Linux I/O. Improve startup, execution, snapshots, and recovery. Understand the boundary between guest, hypervisor, and host, including resource isolation and security. Performance and correctness. Profile latency, allocations, syscall overhead,