Head of Engineering

We need to output HTML fragment with sections: 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 like EEO, etc. We need to parse the posting. Sections present: - About Pi Security (company description) - not a required heading but could be included? The instruction says use headings for section headings like About the role, Responsibilities, etc. The posting includes "About Pi Security" and "About The Role". We should not repeat job title as heading. We can include "About the company" maybe but not required. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings if present. We have: About The Role: includes description of role, reporting, onsite, etc. That's "About the role". So we can put that under

About the role

. What You'll Do: that's responsibilities. So

Responsibilities

with list. What We're Looking For: that's requirements/qualifications/skills. Could split into Requirements (experience), Qualifications (background), Skills (technical). But we can combine? The instruction: prefer a few substantive sections over many thin ones. But we need to follow headings if content exists. We have content for Requirements, Qualifications, Skills. Could separate. What we offer: that's benefits. So

Benefits

. Pay and Schedule: not explicitly mentioned. The posting says "Competitive salary and meaningful equity." That's pay info (salary). So we can include Pay section with that sentence. Schedule: mentions "This role is 100% onsite at our San Francisco office." That's schedule/location. Could be Schedule section. So we can include Schedule. We must not include placeholder text like "commensurate with experience". We have concrete statements. We must not include boilerplate like EEO etc. Remove that line. We must preserve all substantive information. So include company description? Not required heading but could be included as a paragraph before sections? The instruction says output only HTML fragment, no extra. It didn't forbid extra paragraphs not under headings. But we should include all substantive info. The company description "About Pi Security" is substantive. We could include it as a

before headings, or maybe under a heading "About the company". But not in list of headings. Safer to include as a

before the sections. We must not repeat job title as heading. No job title given explicitly, but we can ignore. We must not put Job ID/requisition numbers as headings - none. Now craft HTML. Structure:

About Pi Security Pi is an agentic product security platform built to help engineering teams secure software as fast as they build it. As AI-assisted development accelerates the pace of shipping code, security review and remediation haven't kept up — Pi closes that gap. Instead of just flagging vulnerabilities, Pi ingests a company's codebases, past incidents, and pentest history to build institutional security memory, traces vulnerabilities back to their root cause across repositories, and delivers contextual, ready-to-merge fixes directly into developers' existing workflows. Prevention guardrails then stop the same class of issue from being reintroduced, and our AI assistant, Sloane, gives engineers instant answers about their codebase's security posture and history. We're already trusted by high-velocity engineering organizations — including Lemonade, Teramind, Navan, and several frontier AI labs — to cut manual triage time dramatically and block the vast majority of vulnerabilities before they ever reach production. We recently raised $35M to build out the team and product, backed by Brightmind Partners and Third Point Ventures, alongside investors including CrowdStrike CEO George Kurtz and Armis co-founders Yevgeny Dibrov and Nadir Izrael.

Then

About the role

with paragraph(s) from "About The Role". That includes: hiring Head of Engineering, report to CEO/co-founder, work shoulder-to-shoulder with small team (. Then

Responsibilities

with

• items from "What You'll Do". List each bullet. Then

  Requirements

  maybe from "What We're Looking For" first few sentences: Proven experience as a hands-on engineering leader (e.g., Head of Engineering, VP Engineering, or Staff/Principal Engineer moving into leadership) at an early- or growth-stage startup, ideally having helped scale a team from single digits. Strong full-stack or backend engineering background, with the technical depth to be a real contributor, not just a manager — you should be comfortable in the codebase, not just in planning docs. Experience building and shipping complex, data-intensive, or AI/ML-driven products, ideally involving large codebases, static/dynamic analysis, or developer tooling. A track record of hiring and developing strong engineers, and of building engineering culture and process from a small base. Comfort operating in a fast-moving, ambiguous startup environment, with the judgment to know when to move fast and when to slow down (especially given the security-critical nature of the product). Excellent communication skills — you'll work closely with founders, customers, and a growing team, often translating between technical and business context. Willingness and desire to work onsite in San Francisco full-time. We could split into Requirements and Qualifications and Skills, but we have a lot. Perhaps we can put all under Requirements. But we also have "Nice to Have" separate. Could make Qualifications for the nice-to-have? Actually nice-to-have is separate list. We could treat Requirements as the main qualifications, and Skills as technical skills? But we have many skill-like items. To follow instruction, we can create sections for Requirements, Qualifications, Skills if we can map content. Let's map: Requirements: proven experience as hands-on engineering leader at early/growth startup, scale team from single digits. Qualifications: strong full-stack or backend engineering background, technical depth to be contributor, comfortable in codebase; experience building/shipping complex data-intensive or AI/ML-driven products involving large codebases, static/dynamic analysis, developer tooling; track record of hiring/developing strong engineers, building engineering culture/process from small base; comfort in fast-moving ambiguous startup environment, judgment to know when to move fast/slow; excellent communication skills; willingness to work onsite SF full-time. Skills: maybe the nice-to-have list: background in application security, product security, vulnerability management; experience with developer-tooling integrations (GitHub/GitLab, CI/CD, IDE plugins) or with LLM/agentic systems in production; experience at security-focused company or working closely with security teams as customers; prior experience as early engineering hire or founding engineer. But also the "Strong full-stack or backend engineering background" could be skill. However we can keep as above. Now Benefits: from "What we offer": The opportunity to be one of the first engineering leaders at a well-funded, fast-growing security startup, with outsized ownership and impact on both product and team. Competitive salary and meaningful equity. Work directly alongside the founding team, backed by top investors and security industry leaders. A San Francisco office and a team that believes in building together, in person. Pay: we have "Competitive salary and meaningful equity." Already in Benefits but we could separate Pay. However we might duplicate. Better to keep Pay separate with that sentence, and Benefits with other items. But we risk duplication. The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we put competitive salary in both Benefits and Pay, that's duplication but still preserving. Might be okay but could be considered redundant. Perhaps better to put Pay section with that sentence, and Benefits section with the other items (opportunity, work alongside founding team, office, etc.). That avoids duplication. Schedule: from "This role is 100% onsite at our San Francisco office." Also "Willingness and desire to work onsite in San Francisco full-time." That's schedule/location. So Schedule section can include that. Now we need to ensure we don't include boilerplate like "Pi Security is an equal opportunity employer..." Remove. Now produce HTML. Let's craft. We'll start with company description paragraph. Then

  About the role

  ...

  Then

  Responsibilities

  • Own execution of the engineering roadmap end to end, working closely with the CEO/co-founder on product and technical strategy.
  • Stay hands-on — writing code, reviewing PRs, and making architecture and design decisions alongside the team, especially in the platform's core systems (codebase ingestion, root-cause analysis, remediation generation, and the Sloane assistant).
  • Recruit, hire, and onboard Pi's next engineers, and put in place the processes, standards, and culture that let a small team move fast without breaking things.
  • Set technical direction across the stack — backend services, AI/ML pipelines, integrations with customer developer workflows (source control, CI/CD, issue trackers) — balancing speed with the reliability and trust our security customers require.
  • Partner cross-functionally with founders on customer-facing technical conversations, including with security and engineering leaders at our customers.
  • Build engineering practices (testing, code review, on-call, incident response) that scale as the team and customer base grow, without over-engineering for a startup's current stage.
  • Champion security and quality in our own engineering practices — as a security company, how we build has to hold up to scrutiny.
  Then

  Requirements

  Proven experience as a hands-on engineering leader (e.g., Head of Engineering, VP Engineering, or Staff/Principal Engineer moving into leadership) at an early- or growth-stage startup, ideally having helped scale a team from single digits.

  Then

  Qualifications

  Strong full-stack or backend engineering background, with the technical depth to be a real contributor, not just a manager — you should be comfortable in the codebase, not just in planning docs. Experience building and shipping complex, data-intensive, or AI/ML-driven products, ideally involving large codebases, static/dynamic analysis, or developer tooling. A track record of hiring and developing strong engineers, and of building engineering culture and process from a small base. Comfort operating in a fast-moving, ambiguous startup environment, with the judgment to know when to move fast and when to slow down (especially given the security-critical nature of the product). Excellent communication skills — you'll work closely with founders, customers, and a growing team, often translating between technical and business context. Willingness and desire to work onsite in San Francisco full-time.

  Then

  Skills

  Nice to have: Background in application security, product security, vulnerability management, or a related security domain. Experience with developer-tooling integrations (GitHub/GitLab, CI/CD systems, IDE plugins) or with LLM/agentic systems in production. Experience at a security-focused company or working closely with security teams as customers. Prior experience as an early engineering hire or founding engineer.

  Then

  Pay

  Competitive salary and meaningful equity.

  Then

  Benefits

  • The opportunity to be one of the first engineering leaders at a well-funded, fast-growing security startup, with outsized ownership and impact on both product and