Security Engineer (Application Security)

Join Trail of Bits, a leading cybersecurity firm, as a Security Engineer 1. In this role, you will contribute to security assessments of client software, identify vulnerabilities, and develop tools. You will own pieces of client engagements, drive your own vulnerability analysis, and conduct threat modeling. This hands-on and autonomous position requires strong code analysis skills, hands-on coding proficiency, and clear technical communication. Benefits include health insurance, 401k with company matching, competitive salaries, and remote work flexibility.

• Contribuer aux évaluations de sécurité des logiciels des clients, identifier les vulnérabilités et développer des outils.
• Diriger les évaluations de sécurité pour des composants spécifiques, identifier les vulnérabilités et posséder votre analyse.
• Concevoir et construire des outils de test de sécurité et d'automatisation pour la détection des vulnérabilités.
• Systems knowledge - Deep familiarity with operating systems, IPC, privilege boundaries, and how applications interact with system internals. This isn't theoretical, you've worked with this stuff
• Autonomous problem-solving - You drive your own work. You own pieces of engagements. You ask good questions, debug issues, and reach conclusions without hand-holding
• Strong code analysis skills - You can read complex code, trace execution, identify logic flaws, and explain why something is exploitable. You understand the difference between a tool flagging something and it actually being a vulnerability
• Hands-on coding proficiency - Fluent in at least two of: Rust, Go, C, C++, Python, JavaScript, TypeScript, or similar. You write code for security analysis and tool development, not just consume it
• Memory safety understanding - You understand memory corruption vulnerabilities (buffer overflows, use-after-free, etc.) and modern mitigations (ASLR, DEP, CFI). You can reason about exploit primitives
• Clear technical communication - You can explain complex security findings to engineers. Your reports get read because they're clear and actionable. You can defend your analysis
• Demonstrable vulnerability research capability - Proven ability to find and validate real vulnerabilities. This means: CTF wins, published CVEs, bug bounty finds, or security research that shows you can actually discover exploitable issues
• Published vulnerability research - CVEs, bug bounties, responsible disclosures, or security writeups. Shows you've found real issues and validated them
• Active CTF participation - Current or recent CTF team participation, CTF wins, or rankings. Shows you can solve hard security problems under pressure
• Open source security contributions - Tools, libraries, or research contributions to open source projects. Shows you can ship security work
• Mobile security experience - Android, iOS, or macOS internals. Binary analysis on mobile platforms
• Published technical writing - Blog posts, security research writeups, conference talks, or technical documentation
• Cloud security experience - AWS, GCP, or Azure security assessment and architecture review
• Kernel or low-level development - Experience with kernel code, drivers, or system-level programming
• You're 0–2 years into your security career, or you're coming from software engineering with a strong security foundation. You have proven ability to find vulnerabilities and understand how systems break. You're autonomous, you own your work, you drive your own analysis, and you don't need someone looking over your shoulder
• We're looking for people who've already proven they can do this work: CTF players, people with CVE disclosures, bug bounty hunters, strong engineering grads who've built security tools. You should be capable of owning a piece of a security engagement and driving it to completion
• Years of experience don't matter. Demonstrated ability matters. Can you find vulnerabilities? Can you understand complex code and systems? Can you own your work? If yes, let's talk