{"id":778844,"url":"https://alion.io/job/dedaluslabs-systems-engineer-intern","title":"Systems Engineer Intern","company":{"id":673997,"name":"Dedalus Labs","domain":"dedaluslabs.ai","url":"https://alion.io/company/dedaluslabs","size_band":"1-10","is_staffing_agency":false,"employer_type":"direct","is_intermediary":false,"listed_via":null,"ats_vendor":"Ashby","truth_index":null},"role":"Early Careers","role_family":"Early Careers","seniority":"intern","employment_type":"internship","work_mode":"on_site","remote_scope":null,"remote_scope_basis":null,"remote_working_hours":null,"hiring_geo_confidence":"structured","locations":["San Francisco, United States"],"countries":["US"],"hiring_countries":[],"hiring_countries_total":0,"salary":null,"salary_estimate":{"min_usd":56000,"max_usd":95000,"period":"year","method":"role_seniority_country_remote_cell","sample_n":90},"experience_years_min":null,"visa_sponsorship":false,"relocation_package":false,"has_equity":false,"technologies":[{"name":"AI Agents","optional":false},{"name":"C++","optional":false},{"name":"Rust","optional":false},{"name":"GitHub","optional":true}],"status":"live","first_seen_at":"2026-07-02T00:32:06Z","employer_posted_date":"2026-07-02","last_verified_at":"2026-09-26T03:32:29Z","board_verified":true,"closed_at":null,"days_open":86,"trust":{"level":"ok","repost_count":null,"flags":[],"days_open":86},"description":"Mission\nDedalus Labs is an AI research neolab building infrastructure for AI agents.\nWe’re building the persistent compute layer that powers the next generation of autonomous software. Our platform spans distributed storage, virtualization, orchestration, networking, scheduling, and runtime infrastructure for long-running AI agents.\nWe’re looking for unusually high-potential engineers who want to learn how reliable systems are designed, built, broken, and improved.\nAbout the internship\nThis is a paid, full-time, approximately three-month internship based in San Francisco.\nApplications remain open on a rolling, year-round basis. When we meet an exceptional or unusually high-slope engineer, we can invite them to join the team for a season.\nYou’ll work directly alongside Dedalus engineers on real infrastructure, not a disconnected intern project. You may shadow experienced engineers, but you’ll also be expected to take ownership, write production-quality code, investigate difficult problems, and explain your decisions.\nInterns who demonstrate exceptional technical ability, judgment, ownership, and mutual fit may be considered for full-time roles.\nYou might be a fit if you\nThink abstractions are useful because you understand what’s underneath them.\n\nEnjoy figuring out how operating systems, networks, and distributed systems actually work.\n\nCare about latency, throughput, memory usage, and system reliability.\n\nLike debugging difficult problems and learning from them.\n\nThink distributed systems are fun rather than frightening.\n\nRead systems blogs or papers because you’re genuinely interested.\n\nBuild things outside of class simply because you enjoy it.\n\nBelieve the best infrastructure disappears into the background.\n\nAre high agency and fiercely independent.\n\nSay how things ought to be built, then build them.\n\nAre a competitive teammate with a heart of gold.\n\nAre hungry to learn, improve, and reflect deeply on feedback.\n\nGo above and beyond in everything you do.\n\nWhat you’ll build\nCore compute and runtime primitives for long-running AI agents.\n\nVirtualization, sandboxing, and isolation systems for secure multi-tenant workloads.\n\nPersistent state, storage, snapshotting, and recovery mechanisms.\n\nLow-latency scheduling and resource-management systems.\n\nNetworking and runtime infrastructure across the agent execution path.\n\nProfiling, debugging, benchmarking, and performance tooling.\n\nProduction-grade systems software in Rust, Go, C, or C++.\n\nRepresentative projects\nYou might find yourself working on problems like:\nReducing sandbox startup latency from seconds to milliseconds.\n\nBuilding snapshot and recovery mechanisms for persistent agent state.\n\nDesigning a scheduler for thousands of concurrent, long-running workloads.\n\nProfiling bottlenecks across storage, networking, scheduling, and runtime layers.\n\nImproving isolation and resource controls for secure multi-tenant execution.\n\nBuilding test harnesses that simulate machine loss, degraded networks, and partial failures.\n\nImplementing or evaluating ideas from systems research against our production architecture.\n\nWhat we look for\nStrong programming fundamentals, including data structures, concurrency, memory, and performance.\n\nExperience building and debugging software in Rust, Go, C, C++, or another systems-oriented language. Rust is preferred but not required.\n\nExposure to systems through coursework, research, open source, internships, or self-directed projects.\n\nCuriosity about how operating systems, networks, storage, and runtimes work beneath their abstractions.\n\nThe ability to investigate difficult bugs, reason clearly about tradeoffs, and communicate what you learn.\n\nHigh agency, fast learning, thoughtful responses to feedback, and end-to-end ownership.\n\nEspecially strong signals\nA storage engine, scheduler, database, runtime, compiler, operating system, hypervisor, container system, or distributed service you built.\n\nExperience with virtualization, sandboxing, containers, or hypervisors.\n\nFamiliarity with distributed storage, replication, consensus, or consistency models.\n\nExperience profiling or optimizing latency, throughput, memory usage, or resource consumption.\n\nMeaningful contributions to systems-focused open-source projects.\n\nSystems research accompanied by a working implementation.\n\nTechnical writing that clearly explains architecture, failure modes, and engineering tradeoffs.\n\nA project where you encountered a difficult failure and can explain how you diagnosed it.\n\nTaste\nYou know the difference between code that merely works and code that’s built to last.\nYou care about elegant engineering, good abstractions, and understanding why systems behave the way they do.\nTips\nThe first thing we look at is your GitHub.\nShow us things you’ve built. Personal projects. Research. Hackathons. Operating systems projects. Infrastructure tooling. Homelabs. Open-source contributions.\nWe care far more about demonstrated curiosity and technical ability than your class year or prior internship experience.","description_format":"text","description_chars":5035,"description_truncated":false,"requirements":{"experience_years_min":null,"management_years_min":null,"team_size_min":null,"manages_managers":false,"education":null,"security_clearance":false,"languages":[]},"benefits":[],"hiring_locations":[],"hiring_excludes":[],"relocation_offered":false,"industries":["Cloud Platforms (IaaS & PaaS)","Virtualization & Containers"],"lifecycle":[{"event":"open","at":"2026-09-11T23:56:57Z"}],"liveness":{"score":7,"band":"cold","label":"Long shot","p_open":1,"p_active":0.255,"p_room":0.28,"age_days":85,"expected_fill_days":21,"reasons":["conf:0","win:tail","crowd:junior"],"computed_at":"2026-09-25T05:45:01Z"},"pay":null,"html_url":"https://alion.io/job/dedaluslabs-systems-engineer-intern","json_url":"https://alion.io/job/dedaluslabs-systems-engineer-intern.json","meta":{"generated_at":"2026-09-26T04:03:49Z","cache_seconds":300,"methodology":"https://alion.io/methodology","terms":"https://alion.io/terms","contact":"https://alion.io/contact","api":"https://alion.io/developers","usage":{"tier":"crawler","counted_by":"address","units_charged":1,"used_today":4407,"day_limit":5000,"remaining_today":593,"minute_limit":60,"resets_at":"2026-09-27T00:00:00Z"}}}