DevRel Engineer
Job description
About the role
Connecting developers and AI agents to the E2B platform happens through live examples and integration pattern guidance. Experiments and open-source projects show what builders can create with the infrastructure.
Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.
Key facts
What you'll do
The team maintains the E2B Cookbook repository, adding projects and documentation for users. Research identifies AI trends and generates project ideas that turn concepts into shipped products. New feature information becomes clear through recorded demos about workflows and capabilities. AI companies in the ecosystem collaborate on examples, content, and events that showcase platform use. Meetups and conferences host demos that showcase live experiments with E2B in front of technical audiences. Followers on X and LinkedIn receive updates about AI dev tools, LLMs, and agents, building excitement around the product. Developers online and offline receive communication that answers questions and shows what is possible with the product. Open-source projects move from initial concept to release, establishing ownership and long-term stewardship.
Requirements
The posting states a bachelor's degree requirement. 5+ years of engineering experience ensures familiarity with production workflows. Proficiency in Python, TypeScript, and Next.js supports full-stack implementation of examples. Familiarity with AI SDK, LangChain, Claude Code SDK, and similar toolchains accelerates project delivery. A history of previously built open-source projects demonstrates the ability to ship high-quality code independently. Great taste guides decisions in design, architecture, and user experience for public deliverables. Fast execution under time pressure delivers projects from 0 to 1 without sacrificing quality. The ability to organize yourself manages priorities, roadmap items, and shifting demands in a startup context. Detail orientation prevents regressions and keeps examples accurate and trustworthy. Communication skills present complex technical topics clearly in writing, speaking, and video. Daily communication with users provides feedback that shapes future examples and priorities. An ownership mindset drives projects from initial idea through launch and maintenance in the open-source ecosystem.
Practical notes
Typical interview steps
Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.
Good to know
DevRel work combines product education, content creation, and community engagement. The role relies on strong programming fundamentals and fluency with modern AI tooling. Open-source contribution is a core expectation for visible impact. Clear presentation skills matter for both technical and non-technical audiences. Remote collaboration across time zones is common across the team. Continuous learning keeps examples aligned with fast-moving AI tools and platforms.
Career growth
Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.