Senior Developer Relations Engineer (Security Advocate)

Trail of Bits is a cybersecurity company that advances security through research, custom engineering, public education, and open-source tools. The Senior Developer Relations Engineer will build relationships across security and open-source communities, amplify the firm's research and tooling, support events and conference talks, publish technical content, improve project adoption, and bring community insights back to the firm.

Responsibilities:

• Grow the relationships we already have across the security community, and start new ones. Show up where practitioners gather, contribute alongside maintainers and researchers, and become someone the community knows and trusts
• Own our baseline event presence. Attend and speak at the conferences and cybersecurity meetups that matter to our audiences, and help bring back successful meetups akin to Empire Hacking
• Support the open-source projects and maintainers we work with. Facilitate technical office hours that connect maintainers directly with our engineers, help contributions land upstream, and keep those relationships strong long after an engagement ends
• Turn our research and releases into practitioner staples. Work with Marketing and Technical Editing on advisories, co-authored writeups, and guidance other projects can reuse, and with Engineering on optimizing tools, skills, and plugins for adoption. Teach the methods behind the work through workshops and hands-on sessions, so others can apply them without us
• Publish under your own name, and be present where that work gets discussed. You'll write deep dives, tutorials, and technical write-ups that hold up to scrutiny from working security engineers
• Accelerate our conference and CFP motion. Partner with Marketing to identify speaking opportunities early, and help engineers get talks submitted, prepared, and delivered
• Use our own work the way the community does. Run what we publish against unfamiliar code, and give the teams behind it direct feedback on the research and the experience
• Make our work easy to adopt. Ship examples people can run and integrations that fit their workflows, and contribute to the skills and plugins our teams build with every day. Improve the front door to our projects alongside the teams that own them: better onboarding, clearer documentation, and a first run that works
• Attract contributors from outside Trail of Bits. Show where a first contribution goes, and give them a reason to make a second
• Route what you hear back into the firm: what practitioners struggle with, what they wish existed, where our research has gaps, and which ecosystems are heating up

Requirements:

• • Software people actually use. A tool, a library, an integration, a skill, or an agent, out in the world doing work. You can read unfamiliar code, run our analyzers against it, and open a pull request that gets merged. Everyone builds at Trail of Bits
• • Security depth. Deep, hands-on security experience, typically seven or more years, enough to hold your own with researchers and engineers. Published research, CVEs, and advisories all count
• • AI-native in practice. You build with agentic tooling: skills, agents, MCP servers, harnesses, and evals. If your AI experience stops at writing prompts, this is the wrong role
• • A public body of work. You've contributed where we can see it: talks, posts, upstream contributions, research, and documentation. We will look at your commit history rather than your follower count
• • Community credibility. You know how these communities work, where they gather, and how quickly they detect marketing wearing engineering's clothes
• • Writing and speaking that survive a skeptical audience. We speak to practitioners who can verify everything we say. This carries the same weight as the technical bar
• • Ownership under ambiguity. You'll decide what matters and defend the choice, to engineers and to leadership
• • Reluctance to travel. This role travels about a quarter of the year. Being in the right room is a large part of the job. You should want to be there, and you should know which rooms are worth the trip
• • Experience maintaining or contributing meaningfully to an open-source project
• • Depth in one of our domains: application security, blockchain and cryptography, AI/ML security, or low-level systems research. One is plenty
• • Experience running or programming a community venue at meaningful scale
• • Contributions to developer documentation that lives alongside the code and ships with it
• • Involvement with open-source foundations, grant programs, or maintainer-facing initiatives