Systems Engineer – Project Engineer VI
Voyager Technologies, Inc.Folsom, CA ; Reno, NV ; Long Beach, CA; RemoteRemote
Dedalus LabsSan Francisco, CA
53/100 · Fair. Based on age, reposts, pay, the company's hiring and ghost signals.
See the evidence behind this score.
Pro shows each part of the score, the reasons, the pay percentile and the listing history.
HirQ's ghost-risk estimate and company labels are automated opinions based on what we observe on employers' public job boards: how long a listing has been open, whether it was re-listed, wording in the description, and how often roles on that board close. They are not statements about an employer's intent, and a high-risk listing can still be a real opening. Figures are as of the date shown. How we measure
“- We sponsor visas for exceptional talents.”
Employer-posted ranges for Systems Engineer roles in CA in the last 12 months (78 postings).
This job: No pay listed
From Dedalus Labs's careers page, checked Nov 21
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.
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, networking, and storage on representative workloads. Reproduce races and recovery bugs, use failure injection and property-based tests, and explain what the verification establishes.
Secure interfaces. Build APIs, interprocess communication, and network protocols with explicit trust boundaries. Demonstrate concrete failure or attack paths and verify the fixes.
Filesystems, storage engines, databases, distributed systems, and Linux networking can complement either focus. Formal specifications, model checking, or proofs are strong bonuses when you can explain what they established and how they changed the implementation. GPU infrastructure experience is also useful.
Experience at a big tech company or on another large, fast-moving codebase is a plus, not a requirement. We value demonstrated judgment about compatibility, code review, and safe changes across shared components.
These are examples, not a checklist. Show depth in a relevant area and the ability to learn the layers around it. Production, open-source, research, and independent work all count. A particular employer or degree is not required.
Show us a controller, service, runtime, storage component, or other systems project you built, and a difficult correctness or performance problem you investigated. They can come from the same project. Use existing work.
Work from employment, open source, research, coursework, or independent projects is welcome. Public source code is optional. A redacted excerpt or a concrete account of private work is fine. Keep confidential information out of your application.
Tell us which problem in this role you want to own and why. If your strongest evidence is easy to miss on a resume, point us to it. An existing demo or short screen recording is welcome, and video is optional.
Same role or field, nearby or remote, ranked by HirQ score.
Voyager Technologies, Inc.Folsom, CA ; Reno, NV ; Long Beach, CA; RemoteRemote
Rangeview Inc.El Segundo, California, United States
Space KineticEl Segundo, California
ENSCO, Inc.El Segundo, California, United States
That's No Moon EntertainmentLos Angeles or RemoteRemote
Neon AerospaceIrvine, CA
Dedalus LabsSan Francisco
Dedalus LabsSan Francisco
Dedalus LabsSan Francisco
Systems Engineer
No pay listed · HirQ 53