{"schemaVersion":"jobsearcher.job.v1","id":"1cbb49e6a74ba8371fca5371","url":"https://jobsearcher.com/jobs/1cbb49e6a74ba8371fca5371","canonicalUrl":"https://jobsearcher.com/jobs/1cbb49e6a74ba8371fca5371","title":"Remote Developer Relations Engineer","description":"Developer Relations Engineer Location: North America Remote/SF-Hybrid · Full-Time\r\nAbout Andromeda Andromeda Cluster was founded by Nat Friedman and Daniel Gross to give early-stage startups access to the kind of scaled AI infrastructure once reserved only for hyperscalers.\r\nWe began with a single managed cluster — but it filled almost instantly. Since then, we've been quietly building the systems, network, and orchestration layer that makes the world's AI infrastructure more accessible.\r\nToday, Andromeda works with leading AI labs, data centers, and cloud providers to deliver compute when and where it's needed most. Our platform routes training and inference jobs across global supply, unlocking flexibility and efficiency in one of the fastest-growing markets on earth.\r\nOur long-term vision is to build the liquidity layer for global AI compute. We are expanding to new frontiers to find the brightest that work in AI infrastructure, research and engineering.\r\nThe Role This is an engineering role, not a marketing one. The output is other people's success on our platform.\r\nToday the fastest path to a first successful run at scale on Andromeda is a conversation with one of our engineers. That works for our largest accounts and will keep working. It does not scale, and the knowledge from those conversations stays in Slack threads where a stranger cannot find it at 2am. Your job is to turn that knowledge into artifacts: benchmarks that hold up to scrutiny, reference architectures people deploy, documentation an engineer trusts, and a developer community where the answer is already there before someone has to ask us.\r\nYou will write code the whole time. The reference implementation for multi-node training on our platform, the preflight script someone runs before their first big job, the integration that makes a popular orchestration framework work cleanly on heterogeneous supply: those are your deliverables. When you write that a configuration gets a certain MFU, you ran it.\r\nThree audiences need different things from you. Frontier and AI lab engineering teams want depth and honesty, and they will catch you if you round a number in your favor. Early-stage teams want the shortest path from signup to a run that works, and they are unforgiving of friction. Providers and tooling partners want the platform to be legible enough to build against.\r\nYou are our first DevRel hire, reporting to the Head of Product. Day to day the role is cross-functional engineering. You work with our product engineers and our solutions team on live customer runs, which gives you a direct line to real workloads and real failures. Reporting into product also puts you next to the people who decide what we build next, so when you find a rough edge you argue for the fix with them directly. You decide what this function becomes.\r\nWhat You'll Do Technical content: Benchmarks, deep-dive posts, performance write-ups, postmortems worth publishing, and reference architectures for common training and serving stacks. Every claim is reproducible and every number is one you measured.\r\nDeveloper documentation, end to end: Quickstarts, orchestration guides (Slurm, Kubernetes, direct SSH), storage and checkpointing patterns, and troubleshooting runbooks. Docs are a product with users, and you own the roadmap for them.\r\nThe developer community: The public channels, the GitHub presence, and the office hours. Set the tone, answer the hard questions yourself, and make it a place experienced infra engineers want to be.\r\nCode that lowers the floor for new users: Example repos, container images, reference configs, and integrations with the frameworks and schedulers people already use.\r\nWhat we learn from live workloads: Work with our solutions team on onboardings and incidents, work with our product engineers on the fixes, and turn what you learn into public artifacts so the next team avoids the same wall.\r\nThe developer's case internally: You will see our rough edges first. File the hard bugs, argue for the roadmap changes, and build the missing pieces yourself when that is the fastest path.\r\nPartner and provider enablement: Integration guides, onboarding material, and the technical explanation that lets them build against the platform without a call.\r\nWhat We're Looking For You have run distributed training or large-scale inference in production. You have debugged a stalled multi-node run, and you know the difference between a fabric problem and a dataloader problem because you have been wrong about it before.\r\nStrong Python, with Go or Bash a plus. You build and maintain production-grade tools and libraries, and you are comfortable owning a repo other people depend on.\r\nFluency across the modern stack: PyTorch, NCCL, containers, Kubernetes and/or Slurm, CUDA-adjacent tooling, and at least one serving framework (vLLM, SGLang, TensorRT-LLM, or equivalent).\r\nExcellent technical writing. You explain something hard to a smart audience without condescension or hedging, and people share what you write without being asked.\r\nPublic work we can read or watch: blog posts, benchmarks, OSS contributions, docs you owned, talks you gave. A portfolio matters more than a title here.\r\nJudgment about what to build. You can tell which artifact unblocks a hundred teams and which one only looks impressive, and you pick the first.\r\nYou ship in ambiguity: No playbook, no team to inherit, and the expectation that you define what good looks like and then hit it.\r\nNot A Fit DevRel as a speaking career: You measure the job in talks given and followers gained.\r\nYou need an established program: Here, you are the program.\r\nYou want to manage first: This is an IC role and will stay one for a while.\r\nStrong Candidates May Have Time embedded with external engineering teams: solutions architecture, professional services, deployed engineering, or technical account ownership at an infrastructure company.\r\nPerformance engineering depth: profiling distributed jobs, reasoning about MFU, interconnect behavior, and checkpoint I/O bottlenecks.\r\nWhat Success Looks Like By the end of your first year\r\nTime-to-first-successful-run for new teams is measurably shorter, and you can point to the docs, tooling, and reference configs that did it.\r\nAndromeda has a body of public technical work that engineers cite and share, and that our own team links to instead of re-explaining.\r\nCustomers reach for our documentation before they reach for us, and our solutions team spends its time on novel problems instead of repeat questions.\r\nThere is a real developer community around Andromeda with real technical discussion in it, and increasingly the answers come from members rather than from you.\r\nAt least one integration or OSS contribution you shipped is in active use by customers or partners.\r\nAt least one developer experience change you argued for made the roadmap and shipped.\r\nThe function has a shape: a content cadence, a docs process, and a clear view of what the next hire on this team should own.\r\nWhy You'll Love It Here You define what developer relations means at Andromeda, and the first version of it is yours.\r\nWe are a unicorn, and our customers are leading AI labs and data centers in one of the fastest-growing markets on earth.\r\nSmall senior team, a seat at the table with leadership, and impact measured in days, not quarters.\r\nCross-functional by design: you work with our product engineers and our solutions team, with a direct line to frontier customers and the roadmap.\r\nNorth America remote, competitive pay, and meaningful equity. Healthcare, dental, and vision coverage for you and your dependents, plus 401(k) and unlimited PTO.\r\nAndromeda Cluster is an equal opportunity employer. We celebrate diversity and are committed to creating an inclusive environment for all employees. We do not discriminate on the basis of race, religion, color, national origin, gender, sexual orientation, age, marital status, veteran status, or disability status.","company":"GrabJobs","rawCompany":"grabjobs","city":"Clovis","state":"CA","isRemote":true,"isActive":false,"createdAt":"2026-09-08T13:40:29.679Z","occupations":[{"code":"15-1252.00","title":"Software Developers","slug":"software-developers"},{"code":"15-1299.08","title":"Computer Systems Engineers/Architects","slug":"computer-systems-engineers-architects"},{"code":"15-1221.00","title":"Computer and Information Research Scientists","slug":"computer-and-information-research-scientists"}],"industries":[{"code":"513210","title":"Software Publishers","slug":"software-publishers"},{"code":"541511","title":"Custom Computer Programming Services","slug":"custom-computer-programming-services"},{"code":"541512","title":"Computer Systems Design Services","slug":"computer-systems-design-services"}],"jobPosting":{"@context":"https://schema.org","@type":"JobPosting","title":"Remote Developer Relations Engineer","description":"Developer Relations Engineer Location: North America Remote/SF-Hybrid · Full-Time\r\nAbout Andromeda Andromeda Cluster was founded by Nat Friedman and Daniel Gross to give early-stage startups access to the kind of scaled AI infrastructure once reserved only for hyperscalers.\r\nWe began with a single managed cluster — but it filled almost instantly. Since then, we've been quietly building the systems, network, and orchestration layer that makes the world's AI infrastructure more accessible.\r\nToday, Andromeda works with leading AI labs, data centers, and cloud providers to deliver compute when and where it's needed most. Our platform routes training and inference jobs across global supply, unlocking flexibility and efficiency in one of the fastest-growing markets on earth.\r\nOur long-term vision is to build the liquidity layer for global AI compute. We are expanding to new frontiers to find the brightest that work in AI infrastructure, research and engineering.\r\nThe Role This is an engineering role, not a marketing one. The output is other people's success on our platform.\r\nToday the fastest path to a first successful run at scale on Andromeda is a conversation with one of our engineers. That works for our largest accounts and will keep working. It does not scale, and the knowledge from those conversations stays in Slack threads where a stranger cannot find it at 2am. Your job is to turn that knowledge into artifacts: benchmarks that hold up to scrutiny, reference architectures people deploy, documentation an engineer trusts, and a developer community where the answer is already there before someone has to ask us.\r\nYou will write code the whole time. The reference implementation for multi-node training on our platform, the preflight script someone runs before their first big job, the integration that makes a popular orchestration framework work cleanly on heterogeneous supply: those are your deliverables. When you write that a configuration gets a certain MFU, you ran it.\r\nThree audiences need different things from you. Frontier and AI lab engineering teams want depth and honesty, and they will catch you if you round a number in your favor. Early-stage teams want the shortest path from signup to a run that works, and they are unforgiving of friction. Providers and tooling partners want the platform to be legible enough to build against.\r\nYou are our first DevRel hire, reporting to the Head of Product. Day to day the role is cross-functional engineering. You work with our product engineers and our solutions team on live customer runs, which gives you a direct line to real workloads and real failures. Reporting into product also puts you next to the people who decide what we build next, so when you find a rough edge you argue for the fix with them directly. You decide what this function becomes.\r\nWhat You'll Do Technical content: Benchmarks, deep-dive posts, performance write-ups, postmortems worth publishing, and reference architectures for common training and serving stacks. Every claim is reproducible and every number is one you measured.\r\nDeveloper documentation, end to end: Quickstarts, orchestration guides (Slurm, Kubernetes, direct SSH), storage and checkpointing patterns, and troubleshooting runbooks. Docs are a product with users, and you own the roadmap for them.\r\nThe developer community: The public channels, the GitHub presence, and the office hours. Set the tone, answer the hard questions yourself, and make it a place experienced infra engineers want to be.\r\nCode that lowers the floor for new users: Example repos, container images, reference configs, and integrations with the frameworks and schedulers people already use.\r\nWhat we learn from live workloads: Work with our solutions team on onboardings and incidents, work with our product engineers on the fixes, and turn what you learn into public artifacts so the next team avoids the same wall.\r\nThe developer's case internally: You will see our rough edges first. File the hard bugs, argue for the roadmap changes, and build the missing pieces yourself when that is the fastest path.\r\nPartner and provider enablement: Integration guides, onboarding material, and the technical explanation that lets them build against the platform without a call.\r\nWhat We're Looking For You have run distributed training or large-scale inference in production. You have debugged a stalled multi-node run, and you know the difference between a fabric problem and a dataloader problem because you have been wrong about it before.\r\nStrong Python, with Go or Bash a plus. You build and maintain production-grade tools and libraries, and you are comfortable owning a repo other people depend on.\r\nFluency across the modern stack: PyTorch, NCCL, containers, Kubernetes and/or Slurm, CUDA-adjacent tooling, and at least one serving framework (vLLM, SGLang, TensorRT-LLM, or equivalent).\r\nExcellent technical writing. You explain something hard to a smart audience without condescension or hedging, and people share what you write without being asked.\r\nPublic work we can read or watch: blog posts, benchmarks, OSS contributions, docs you owned, talks you gave. A portfolio matters more than a title here.\r\nJudgment about what to build. You can tell which artifact unblocks a hundred teams and which one only looks impressive, and you pick the first.\r\nYou ship in ambiguity: No playbook, no team to inherit, and the expectation that you define what good looks like and then hit it.\r\nNot A Fit DevRel as a speaking career: You measure the job in talks given and followers gained.\r\nYou need an established program: Here, you are the program.\r\nYou want to manage first: This is an IC role and will stay one for a while.\r\nStrong Candidates May Have Time embedded with external engineering teams: solutions architecture, professional services, deployed engineering, or technical account ownership at an infrastructure company.\r\nPerformance engineering depth: profiling distributed jobs, reasoning about MFU, interconnect behavior, and checkpoint I/O bottlenecks.\r\nWhat Success Looks Like By the end of your first year\r\nTime-to-first-successful-run for new teams is measurably shorter, and you can point to the docs, tooling, and reference configs that did it.\r\nAndromeda has a body of public technical work that engineers cite and share, and that our own team links to instead of re-explaining.\r\nCustomers reach for our documentation before they reach for us, and our solutions team spends its time on novel problems instead of repeat questions.\r\nThere is a real developer community around Andromeda with real technical discussion in it, and increasingly the answers come from members rather than from you.\r\nAt least one integration or OSS contribution you shipped is in active use by customers or partners.\r\nAt least one developer experience change you argued for made the roadmap and shipped.\r\nThe function has a shape: a content cadence, a docs process, and a clear view of what the next hire on this team should own.\r\nWhy You'll Love It Here You define what developer relations means at Andromeda, and the first version of it is yours.\r\nWe are a unicorn, and our customers are leading AI labs and data centers in one of the fastest-growing markets on earth.\r\nSmall senior team, a seat at the table with leadership, and impact measured in days, not quarters.\r\nCross-functional by design: you work with our product engineers and our solutions team, with a direct line to frontier customers and the roadmap.\r\nNorth America remote, competitive pay, and meaningful equity. Healthcare, dental, and vision coverage for you and your dependents, plus 401(k) and unlimited PTO.\r\nAndromeda Cluster is an equal opportunity employer. We celebrate diversity and are committed to creating an inclusive environment for all employees. We do not discriminate on the basis of race, religion, color, national origin, gender, sexual orientation, age, marital status, veteran status, or disability status.","datePosted":"2026-09-08T13:40:29.679Z","dateModified":"2026-09-08T13:40:29.679Z","hiringOrganization":{"@type":"Organization","name":"GrabJobs","sameAs":"https://jobsearcher.com"},"jobLocationType":"TELECOMMUTE","applicantLocationRequirements":{"@type":"Country","name":"US"},"jobLocation":{"@type":"Place","address":{"@type":"PostalAddress","addressLocality":"Clovis","addressRegion":"CA","addressCountry":"US"}},"identifier":{"@type":"PropertyValue","name":"JobSearcher","value":"1cbb49e6a74ba8371fca5371"},"url":"https://jobsearcher.com/jobs/1cbb49e6a74ba8371fca5371"}}