Developer Relations

AI is making it dramatically easier to generate code. The harder problem is understanding whether that code is correct, safe, and consistent with the rest of a codebase. RubberDuck is building tools to help developers reason about complex codebases, investigate changes, validate AI-generated code, and make better engineering decisions with evidence. We’re looking for a Developer Relations Engineer who can help turn RubberDuck’s technical capabilities into developer adoption. This is a hands‑on role at the intersection of engineering, technical content, social media, benchmarks, and developer community. You should be technical enough to open a repo, test the product, understand what happened, and explain it clearly — whether that means a benchmark, a demo, a technical post, or a sharp X thread. What you’ll do Own RubberDuck’s technical presence Own and grow RubberDuck’s presence on X/Twitter Publish consistently around product updates, benchmarks, demos, technical insights, and relevant developments in AI and software engineering Turn engineering work into concise, high-signal content developers actually want to read and share Join relevant technical conversations rather than simply broadcasting company announcements Help develop a recognizable technical voice for RubberDuck Create technical content Write technical posts, tutorials, threads, demos, videos, and launch content Translate complex product capabilities into clear, compelling developer stories Create examples using real repositories and realistic engineering problems Produce content across X, the RubberDuck blog, documentation, GitHub, and other developer channels Build benchmarks and technical proof Work closely with the founder and engineering team to design meaningful benchmarks and product evaluations Compare RubberDuck against relevant AI coding tools, models, and developer workflows Create reproducible experiments that developers can inspect for themselves Turn benchmark results into strong technical narratives without overselling what the results prove Continuously look for interesting edge cases, failures, and examples that demonstrate where the product is valuable Work directly with developers Talk to developers using RubberDuck and understand what they are trying to accomplish Identify common use cases, friction points, and product gaps Bring developer feedback directly into product and engineering discussions Help early users get value from the product and turn successful workflows into examples for the broader community Work alongside engineering on feature launches Create demos, documentation, technical examples, benchmark results, and social content around new releases Help determine how technical launches should be positioned to developer audiences Make sure new capabilities are not just shipped, but understood Build community Engage with engineers, AI researchers, technical founders, and developer‑tool communities Participate in relevant online communities, events, hackathons, livestreams, podcasts, and conferences Build relationships with developers who can become early users, contributors, advocates, or partners What we’re looking for You are highly technical, but you also enjoy communicating. You can go from reading code to running an experiment to writing a strong X post about what you discovered. Ideally, you have: Strong software engineering fundamentals Experience working with real production codebases Familiarity with modern AI coding tools such as Claude Code, Cursor, Codex, or similar products The ability to quickly understand unfamiliar repositories and technical systems Excellent technical writing and communication skills Strong instincts for social media, especially X/Twitter The ability to explain technical ideas clearly without flattening the nuance Experience creating technical demos, tutorials, documentation, or developer‑facing content Curiosity about AI agents, AI‑assisted software development, code intelligence, and developer tools Comfort working in an early‑stage startup where responsibilities will evolve quickly You do not need to already have a large personal audience. Previous DevRel or Developer Advocate experience Experience with AI coding agents or LLM infrastructure Experience designing benchmarks or technical evaluations Background in static analysis, program analysis, compilers, code intelligence, or security tooling Open‑source contributions Experience growing a technical account or audience on X Experience producing technical video content Existing relationships within developer or AI communities What success looks like In your first few months, RubberDuck should have: A consistent and recognizable technical presence on X A growing library of compelling product demos and technical content Credible benchmarks and comparisons developers can inspect themselves Clear examples showing why and when developers should use RubberDuck More developers discovering and trying the product organicall