Security Engineer II, Application Security

We need to produce HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We need to parse the posting. Let's extract sections: - Location: Remote, United States (metadata). Could be placed in a short

maybe. - About Trail Of Bits: description. Could be "About the role"? Actually "About the role" heading is for role description. The posting includes "The Role" description. So we can put that under

About the role

with paragraphs. - What You'll Achieve: list of achievements. Could be under

Responsibilities

(or maybe "What You'll Achieve" is responsibilities). We'll map to Responsibilities. - What You'll Bring: requirements. Could be under

Requirements

(or Qualifications). The posting has "What You'll Bring" with bullet list of requirements. Also "Preferred Qualifications". So we can have Requirements (mandatory) and Qualifications (preferred). Or combine. - Skills: maybe not explicit separate; but we could include programming languages etc under Skills. However we have to avoid thin sections. Could embed skills within Requirements. - Benefits: there is a Benefits section with details. So include

Benefits

. - Pay: compensation section with salary range and bonus. So include

Pay

. - Schedule: not mentioned (remote, full-time). No explicit schedule. So we should not include Schedule heading. - Also there is location metadata; we can put in a

at top. We must not include boilerplate like "Trail of Bits, Inc. participates in E-Verify..." and EEO statement. Remove those. Also remove duplicated lines: there is a "Benefits" heading repeated later with details; we need to keep the details but not duplicate heading. We need to preserve all substantive info: that includes the description of Trail of Bits, the role description, what you'll achieve, what you'll bring (requirements), preferred qualifications, compensation, benefits details. We must not invent or summarize away detail. Must keep specifics like "2+ years of directly relevant experience", list of languages, etc. We need to format lists with

• . For prose use

  . We must not include markdown fences. Let's craft. Start with a

  for location: "Location: Remote, United States". Could be just "Remote, United States". We'll include as a short paragraph. Then

  About the role

  with paragraphs from "The Role" section. The Role paragraph: "Trail of Bits seeks a Security Engineer II for our Application Security practice. You will conduct security assessments of client software, independently own substantial components or workstreams, identify and validate vulnerabilities across the application and system levels, and develop custom tooling alongside the team. You will own your analysis from discovery through client delivery and help clients understand and fix the issues you find. This role bridges vulnerability research and applied security. Your work will be hands-on and autonomous: analyzing complex code, building custom tooling, conducting threat modeling and architecture reviews, and delivering findings that can withstand technical scrutiny. It is distinct from roles centered on security operations, SOC work, GRC, compliance, policy, audit, or general security programs. Candidates from broader or adjacent security backgrounds should be prepared to talk through sustained, hands-on code-level security work they have personally completed. At the Security Engineer II level, you should be able to take an ambiguous component, module, or attack surface, determine how to assess it, perform the analysis, and deliver clear findings with limited day-to-day direction. You will collaborate with a project lead and other security engineers while exercising independent technical judgment and improving the work of the team around you." We can split into maybe two paragraphs. Then

  Responsibilities

  with list from "What You'll Achieve". Items: - Security Assessment Ownership: Independently lead assessments of substantial components, modules, or systems within client engagements and own the work from scoping through delivery - Vulnerability Discovery and Analysis: Find and validate vulnerabilities, establish root causes and exploitation paths, assess impact, and develop proof-of-concept code when appropriate - Custom Security Tooling: Design and build targeted tools, harnesses, tests, or automation that expand assessment coverage and improve repeatability - Architecture and Threat Modeling: Review complex software architectures, identify attack surfaces, data flows, trust and privilege boundaries, and recommend practical mitigations - Client Communication: Produce clear, actionable findings, defend the evidence behind them, and lead technical discussions with client engineering teams - Team Contribution: Review other engineers' code and analysis, share techniques, and help improve the team's technical approach - Research and Innovation: Contribute new methods, open-source tools, and technical writing to Trail of Bits and the broader security community We'll make each as
• . Then

  Requirements

  with list from "What You'll Bring" (the mandatory requirements). Items: - Typically 2+ years of directly relevant experience in application security, vulnerability research, security-focused software engineering, or a closely related area. Relevant experience may include professional work, research, open-source contributions, or substantial academic or independent projects; demonstrated depth and independence matter more than a strict year count - Repeated vulnerability-discovery experience. You can talk through vulnerabilities you personally found or validated, including how you identified them, established exploitation paths and impact, and distinguished them from false positives or low-impact defects - Strong code-analysis skills across unfamiliar and complex codebases, including tracing execution and data flow, identifying logic and implementation flaws, and reviewing the security implications of system design - Strong programming and debugging ability in at least two relevant languages, such as Rust, Go, C, C++, Python, JavaScript, TypeScript, or similar languages used in security analysis and tool development - Working knowledge of memory-corruption vulnerabilities and mitigations, including the ability to reason about exploit primitives, defensive mechanisms, and the practical security impact of implementation choices - Strong systems knowledge, including operating systems, IPC, privilege boundaries, system internals, and how applications interact with the platform around them - Demonstrated ability to independently scope and execute a code-level security-assessment workstream, prioritize attack surfaces, build or adapt tooling, document evidence, and deliver findings - Clear written and verbal communication, including experience presenting technical conclusions to software engineers or clients and contributing effectively on a distributed team We'll list each as
• . Then

  Preferred Qualifications

  with list from "Preferred Qualifications". Items: - Active or recent CTF participation, competition results, or comparable hands-on security challenges - Published vulnerability research, CVEs, responsible disclosures, bug bounty findings, conference presentations, or technical writeups - Contributions to open-source security tools, libraries, or research - Experience with mobile application security, mobile system internals, or binary analysis on mobile platforms - Experience assessing cloud platforms or infrastructure and working with tools such as Kubernetes, Helm, Terraform, or Ansible - Experience with kernel code, drivers, reverse engineering, fuzzing, symbolic execution, or other low-level systems work - Experience building security tools used by other engineers or across multiple assessments - Experience leading client-facing technical discussions or mentoring other security engineers Then

  Pay

  with paragraph: "The base salary range for this full-time position is $140,000 to $180,000. This position is also eligible for a performance-based variable bonus. Compensation is informed by geographic location, relevant experience, and internal equity. These figures represent starting compensation for U.S.-based candidates. For specifics, please discuss with your recruiter during the hiring process." We should not include "Trail of Bits offers a comprehensive benefits package..." because that's in Benefits section. Then

  Benefits

  with list from Benefits section. The benefits description includes: - Empowered Living: Competitive salary complemented by performance-based bonuses - Fully company-paid insurance packages, including health, dental, vision, disability, and life - A solid 401(k) plan with a 5% match of your base salary - 20 days of paid vacation with flexibility for more, adhering to jurisdictional regulations - Nurturing New Beginnings: 4 months of parental leave to cherish the arrival of new family members - Our team is global and remote-first. However, if you are interested in moving to NYC, we offer $10,000 in relocation assistance to support your transition - Work & Life Enrichment: $1,000 Working-from-Home stipend to create a comfortable and productive home office - Annual $750 Learning & Development stipend for continuous personal and professional growth - Company-sponsored all-team celebrations, including travel and accommodation, to foster community and recognize achievements - Community Impact: Philanthropic contribution matching up to $2,000 annually We need to preserve all substantive info. The bullet points are already in the text; we can format as
  • . Some are sentences with colon; we can keep as is. We should not include the line "Trail of Bits is our people, not a place..." maybe we can keep as intro paragraph before list. But we can incorporate as a

    then list. We must not include boilerplate like "Trail of Bits, Inc. participates in E-Verify..." and EEO statement. Remove those. Also remove duplicated lines: there is a "Benefits" heading repeated later with details; we already captured details; we should not duplicate heading. Now ensure we don't include sections with filler like "commensurate with experience". Not present. We must not include Schedule section. Now produce HTML fragment. Let's craft:

    Location: Remote, United States

    About the role

    ...

    Responsibilities

    • ...
    ...

    Requirements

    • ...
    ...

    Preferred Qualifications

    • ...
    ...

    Pay

    ...

    Benefits

    Trail of Bits is our people, not a place. With over 100+ employees working from every time zone across the globe, our remote-first culture is built on autonomy and trust (and backed by smile-worthy benefits) for full-time employees:

    • Empowered Living: Competitive salary complemented by performance-based bonuses
    • Fully company-paid insurance packages, including health, dental, vision, disability, and life
    • A solid 401(k) plan with a 5% match of your base salary
    • 20 days of paid vacation with flexibility for more, adhering to jurisdictional regulations
    • Nurturing New Beginnings: 4 months of parental leave to cherish the arrival of new family members
    • Our team is global and remote-first. However, if you are interested in moving to NYC, we offer $10,000 in relocation assistance to support your transition
    • Work & Life Enrichment: $1,000 Working-from-Home stipend to create a comfortable and productive home office
    • Annual $750 Learning & Development stipend for continuous personal and professional growth
    • Company-sponsored all-team celebrations, including travel and accommodation, to foster community and recognize achievements
    • Community Impact: Philanthropic contribution matching up to $2,000 annually
    Check for any leftover