The role
We are seeking a Developer Relations Lead to help QuEra's QPU and software ecosystem become the platform that serious quantum developers reach for when they want to understand, prototype, emulate, and eventually run programs on neutral-atom quantum computers. You will be responsible for managing and growing a developer community of advanced quantum scientists and engineers, while helping users move from first contact with QuEra's tools to productive software workflows. You will also work closely with the Scientific Software, Applications, QEC, Education, Solutions, and Product teams to ensure that QuEra's developer-facing materials and community programs remain technically accurate, useful, and aligned with the evolution of the platform.
What you will do- Own the open-source developer community: Manage and grow the community around QuEra's open-source software tools. Help users ask better questions, file better issues, contribute examples, understand project direction, and become repeat users or contributors.
- Build examples and reference workflows: Develop and maintain code examples that help developers move beyond NISQ-era workflows and begin working with the primitives needed for fault-tolerant quantum computing, including logical qubits, atom shuttling, QEC, and hardware-aware emulation.
- Maintain software tutorials, how-to guides, and documentation paths: Own the practical developer-facing materials that help users install QuEra's SDKs, run examples, debug common issues, understand workflows, and connect software concepts to working code.
- Run developer-facing programs: Represent QuEra at conferences, hackathons, tutorials, customer trainings, open-source events, and academic programs. Organize hands-on activities that help technical users engage with QuEra's software in practical ways.
- Bring developer feedback back into the company: Collect structured feedback from GitHub issues, workshops, customer interactions, community channels, and direct user conversations. Create representative user stories, issue summaries, and minimal reproducible examples that help our team understand real developer workflows.
What we are looking for- Experience in developer relations, developer advocacy, scientific software, technical education, open-source community building, or a closely related technical role.
- Hands-on experience writing code in Python, preferably in scientific or research computing contexts.
- Quantum computing background sufficient to communicate credibly with researchers, application scientists, and advanced users. You do not need to be the world expert in every subfield, but you should be able to learn new quantum concepts quickly and explain them accurately.
- A track record of creating high-quality technical content such as tutorials, documentation, example repositories, blog posts, workshops, lectures, demos, or conference talks.
- Ability to read and modify nontrivial codebases, reproduce bugs, create minimal examples, and collaborate with engineers through GitHub or similar workflows.
- Comfort operating in ambiguity, especially when software APIs, product direction, and hardware capabilities are still evolving.
- A user-centered mindset and willingness to push back when a workflow, API, tutorial, or release process is confusing.
Nice to have- Exposure to compiler concepts, intermediate representations, circuit compilation, or hardware-aware quantum programming.
- Practical understanding of APIs, versioning, backwards compatibility, documentation systems, testing, CI/CD, and release communication.
- Experience with quantum algorithms, quantum error correction, neutral-atom systems, or related research workflows.
- Awareness of the modern tooling landscape for fault-tolerant quantum computing research, including circuit simulators, QEC decoders, resource estimation tools, logical compilation workflows, and hardware-aware emulation tools.
- Ability to reason about AI-assisted or agent-oriented developer workflows, especially in scientific computing, research software, notebooks, documentation, debugging, or experiment orchestration.
#LI-NB1
