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 doOwn RubberDuck’s technical presenceOwn and grow RubberDuck’s presence on X/TwitterPublish consistently around product updates, benchmarks, demos, technical insights, and relevant developments in AI and software engineeringTurn engineering work into concise, high-signal content developers actually want to read and shareJoin relevant technical conversations rather than simply broadcasting company announcementsHelp develop a recognizable technical voice for RubberDuckCreate technical contentWrite technical posts, tutorials, threads, demos, videos, and launch contentTranslate complex product capabilities into clear, compelling developer storiesCreate examples using real repositories and realistic engineering problemsProduce content across X, the RubberDuck blog, documentation, GitHub, and other developer channelsBuild benchmarks and technical proofWork closely with the founder and engineering team to design meaningful benchmarks and product evaluationsCompare RubberDuck against relevant AI coding tools, models,



and developer workflowsCreate reproducible experiments that developers can inspect for themselvesTurn benchmark results into strong technical narratives without overselling what the results proveContinuously look for interesting edge cases, failures, and examples that demonstrate where the product is valuableWork directly with developersTalk to developers using RubberDuck and understand what they are trying to accomplishIdentify common use cases, friction points, and product gapsBring developer feedback directly into product and engineering discussionsHelp early users get value from the product and turn successful workflows into examples for the broader communityWork alongside engineering on feature launchesCreate demos, documentation, technical examples, benchmark results, and social content around new releasesHelp determine how technical launches should be positioned to developer audiencesMake sure new capabilities are not just shipped, but understoodBuild communityEngage with engineers, AI researchers, technical founders, and developer‑tool communitiesParticipate in relevant online communities, events, hackathons, livestreams, podcasts, and conferencesBuild relationships with developers who can become early users, contributors, advocates, or partnersWhat we’re looking forYou 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 fundamentalsExperience working with real production codebasesFamiliarity with modern AI coding tools such as Claude Code, Cursor, Codex,



or similar productsThe ability to quickly understand unfamiliar repositories and technical systemsExcellent technical writing and communication skillsStrong instincts for social media, especially X/TwitterThe ability to explain technical ideas clearly without flattening the nuanceExperience creating technical demos, tutorials, documentation, or developer‑facing contentCuriosity about AI agents, AI‑assisted software development, code intelligence, and developer toolsComfort working in an early‑stage startup where responsibilities will evolve quicklyYou do not need to already have a large personal audience.Previous DevRel or Developer Advocate experienceExperience with AI coding agents or LLM infrastructureExperience designing benchmarks or technical evaluationsBackground in static analysis, program analysis, compilers, code intelligence, or security toolingOpen‑source contributionsExperience growing a technical account or audience on XExperience producing technical video contentExisting relationships within developer or AI communitiesWhat success looks likeIn your first few months, RubberDuck should have:A consistent and recognizable technical presence on XA growing library of compelling product demos and technical contentCredible benchmarks and comparisons developers can inspect themselvesClear examples showing why and when developers should use RubberDuckMore developers discovering and trying the product organicallyStronger feedback loops between users and the engineering teamA growing community of developers who understand what RubberDuck is building and want to follow its progressThe kind of person who will love this roleYou see a technical claim and your first reaction is:"How do we prove that?"You run the experiment.Then you figure out how to explain the result in a way that makes thousands of developers care.#J-18808-Ljbffr

📌 Developer Relations (Madrid)
🏢 RubberDuck
📍 Madrid