{"id":778839,"url":"https://alion.io/job/dedaluslabs-infrastructure-engineer-intern","title":"Infrastructure 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,"is_intermediary":false,"listed_via":null,"ats_vendor":"Ashby","truth_index":null},"role":"DevOps","role_family":"DevOps","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":null,"experience_years_min":null,"visa_sponsorship":true,"relocation_package":false,"has_equity":false,"technologies":[{"name":"AI Agents","optional":false},{"name":"C++","optional":false},{"name":"GitHub","optional":false},{"name":"Go","optional":false},{"name":"Rust","optional":false},{"name":"Kubernetes","optional":true}],"status":"live","first_seen_at":"2026-08-15T02:00:46Z","employer_posted_date":"2026-08-15","last_verified_at":"2026-09-24T03:38:26Z","board_verified":true,"closed_at":null,"days_open":40,"trust":{"level":"ok","repost_count":null,"flags":[],"days_open":40},"description":"Infrastructure Engineer Intern @ Dedalus Labs\nMission\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 distributed systems are one of computer science’s most beautiful subjects.\n\nWant to understand why systems fail-not merely how to make the happy path work.\n\nHave built something technically difficult relative to your experience.\n\nCan explain the hardest part of a project, what failed, and what you personally contributed.\n\nCare about consistency, fault tolerance, concurrency, latency, and system correctness.\n\nEnjoy learning how operating systems, storage engines, schedulers, networks, and runtimes work.\n\nRead technical papers, source code, or engineering postmortems because you are genuinely curious.\n\nPrefer building and experimenting over collecting credentials.\n\nLearn unusually quickly and act deeply on feedback.\n\nAre comfortable working through ambiguity and taking ownership without waiting for detailed instructions.\n\nBelieve simple systems are often harder to build than complicated ones.\n\nMeasure before optimizing, then optimize relentlessly.\n\nAre high agency and fiercely independent.\n\nAre a competitive teammate with a heart of gold.\n\nGo above and beyond in everything you do.\n\nWhat you’ll work on\nDepending on your strengths and the company’s needs, you may contribute to:\nDistributed infrastructure for large-scale AI agent workloads.\n\nPersistent compute and distributed storage systems.\n\nScheduling and orchestration platforms.\n\nVirtualization, containerization, and sandboxing infrastructure.\n\nReliable multi-tenant cloud systems.\n\nInternal developer platforms and infrastructure tooling.\n\nPerformance, reliability, observability, and failure recovery.\n\nProduction systems operating under real-world latency and fault-tolerance constraints.\n\nRepresentative projects\nYou might find yourself working on problems like:\nBuilding a component of a distributed storage system for persistent agent state.\n\nImproving the reliability or recovery behavior of a production service.\n\nDesigning scheduling infrastructure for concurrent, long-running agent workloads.\n\nInvestigating a bottleneck across storage, networking, scheduling, or runtime layers.\n\nBuilding internal tooling that makes infrastructure easier to operate and debug.\n\nDesigning tests that simulate partial failures, machine loss, or degraded networks.\n\nImproving observability for distributed workloads.\n\nPrototyping a new isolation, caching, or orchestration mechanism.\n\nReading a systems paper, implementing part of it, and comparing its tradeoffs with our architecture.\n\nYour project will be scoped to the internship, but it should matter to the company and be used by real engineers or systems.\nWhat we look for\nA public GitHub profile is required.\n\nDemonstrated programming ability in Rust, Go, C, C++, or a similar language.\n\nEvidence that you have built and completed technically meaningful projects.\n\nSolid computer-science fundamentals and a genuine interest in systems.\n\nThe ability to reason clearly about tradeoffs, failure modes, and debugging.\n\nSpecificity about what you personally built and why you made particular decisions.\n\nHigh agency, intellectual honesty, curiosity, and learning velocity.\n\nStrong written and verbal technical communication.\n\nThe ability to work full-time and in person from our San Francisco office for approximately three months.\n\nA specific reason you want to work on infrastructure for AI agents at Dedalus.\n\nWe evaluate candidates relative to their experience and opportunities. You do not need a prestigious employer, advanced degree, or long résumé.\nStudents, recent graduates, researchers, self-taught engineers, open-source contributors, and early-career engineers are all welcome to apply. What matters is the difficulty and quality of what you have done, what you personally owned, and how quickly you are improving.\nEspecially strong signals\nSelf-directed systems projects built beyond required coursework.\n\nMeaningful open-source contributions.\n\nA storage engine, scheduler, database, runtime, compiler, operating system, hypervisor, container system, or distributed service you built.\n\nA correct implementation of Raft, Paxos, replication, sharding, or another distributed-systems concept-with thoughtful testing and documentation.\n\nTechnical writing that explains architecture, failure modes, and tradeoffs.\n\nEvidence that other people use or depend on something you built.\n\nResearch accompanied by a working implementation.\n\nA project where you encountered a difficult failure and can explain how you diagnosed it.\n\nRepeated evidence of unusually fast learning and end-to-end ownership.\n\nClass projects can demonstrate baseline knowledge. Projects that you initiated, substantially extended, or pursued beyond their requirements are generally stronger signals.\nNice to have\nExperience with distributed storage systems.\n\nFamiliarity with consistency models, consensus algorithms, or replication protocols.\n\nExperience with Kubernetes or modern cloud infrastructure.\n\nExperience with virtualization, hypervisors, containers, or Firecracker.\n\nKernel, operating-systems, or low-level runtime experience.\n\nExperience with concurrency, networking, or performance engineering.\n\nContributions to systems-focused open-source projects.\n\nPublished or ongoing systems research.\n\nExperience operating infrastructure used by real users.\n\nFamiliarity with infrastructure for AI agents or long-running workloads.\n\nThese are advantages, not a checklist. We care more about demonstrated potential and ownership than whether you satisfy every item.\nTaste\nYou are beginning to understand the difference between a distributed system that works and one that continues working when everything goes wrong.\nYou care about simple architecture, principled tradeoffs, clear abstractions, and infrastructure that other engineers can trust.\nYou are not expected to know everything. You are expected to learn quickly, think deeply, and care about getting the details right.\nWhat success looks like\nBy the end of the internship, we hope you will have:\nOwned and shipped a meaningful infrastructure project.\n\nDeveloped a deeper understanding of production distributed systems.\n\nDemonstrated strong technical judgment and debugging ability.\n\nResponded thoughtfully and quickly to feedback.\n\nWritten clear code, tests, documentation, and architectural reasoning.\n\nMade Dedalus’s infrastructure meaningfully more reliable, performant, or usable.\n\nGiven the team enough evidence to assess possible long-term fit.\n\nLogistics\nRolling applications throughout the year.\n\nApproximately three months, with exact dates agreed upon individually.\n\nPaid, full-time internship.\n\nFive days per week in person in San Francisco.\n\nMeals and office benefits included.\n\nRelocation support may be available.\n\nVisa support may be considered depending on the candidate and circumstances.\n\nPossible consideration for full-time employment, without any guarantee of conversion.\n\nTips\nThe first thing we look at is your GitHub.\nShow us the best systems work you have built: infrastructure, research implementations, storage engines, schedulers, distributed services, runtimes, operating-systems projects, open-source contributions, or technically ambitious experiments.\nFor your strongest project, tell us:\nWhat you personally built.\n\nWhy it was difficult.\n\nThe hardest bug or failure you encountered.\n\nThe architectural tradeoffs you made.\n\nWhat you would do differently now.\n\nWhere we can inspect the code, documentation, or result.\n\nA smaller project you deeply understand is more compelling than a popular project where your contribution is unclear.\nWe care far more about what you have built, how well you understand it, and how quickly you are improving than the number of years on your résumé.","description_format":"text","description_chars":8913,"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":true,"industries":["Virtualization","AI Agents"],"lifecycle":[{"event":"open","at":"2026-09-11T23:56:57Z"}],"liveness":{"score":12,"band":"cold","label":"Long shot","p_open":1,"p_active":0.431,"p_room":0.28,"age_days":40,"expected_fill_days":20,"reasons":["conf:2","win:tail","crowd:junior"],"computed_at":"2026-09-24T05:45:00Z"},"pay":null,"html_url":"https://alion.io/job/dedaluslabs-infrastructure-engineer-intern","json_url":"https://alion.io/job/dedaluslabs-infrastructure-engineer-intern.json","meta":{"generated_at":"2026-09-24T16:05:21Z","cache_seconds":300,"methodology":"https://alion.io/methodology","terms":"https://alion.io/terms","contact":"https://alion.io/contact","api":"https://alion.io/developers"}}