Security Software Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. We must not repeat job title. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the posting. Key sections: - About the role: description of role: "We are hiring across seniority levels for a Founding Security Engineer to build the security foundation for a frontier AI platform serving enterprise customers — owning product/API security, enterprise security architecture, compliance readiness, and incident response as the company scales. You'll own and drive the systems, processes, and infrastructure that make Inception secure by default: cloud security, network isolation, access controls, incident response, compliance readiness, secure engineering workflows, and customer-facing security requirements. This role is ideal for someone who lives and breathes security, but is still a builder at heart — someone who can design secure systems, write production code, automate workflows, and partner deeply with engineering teams. This is not a narrow GRC, IT, AI safety, or policy-only role, and it is not AI-specific security research. We're looking for traditional enterprise/product security execution from an "inverted T" engineer: broad software engineering ability with a deep spike in security. You'll be the internal expert who helps us navigate enterprise security, privacy, compliance, and infrastructure risk as we scale — a technical leader, not a friction point for the engineering team." - What You'll Own: bullet list of responsibilities. - You Might Be a Fit If: bullet list of qualifications/requirements. - Nice to Have: bullet list of nice-to-have. - Compensation: salary range. - Perks & Benefits: bullet list. - About Us: description of company. We need sections: maybe "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We have Pay (Compensation). Benefits (Perks & Benefits). Schedule not mentioned, so omit. We need to decide which sections to include: About the role (yes). Responsibilities (What You'll Own). Requirements (You Might Be a Fit If). Qualifications (maybe combine with Requirements? Could separate but we have both). Skills (maybe from Nice to Have). Benefits (Perks & Benefits). Pay (Compensation). We'll include sections with real content. We must not include placeholder like "commensurate with experience". Not present. We need to use

for each section heading. Then content: either

for prose,

• for lists. We must not repeat job title. No Job ID. We must output only HTML fragment. Let's craft. First, About the role: combine the paragraph(s) into

  . Second, Responsibilities: list from "What You'll Own". Items: - Software engineering fundamentals: This is a software engineering role with a security specialization. Expect to spend 70%+ of your time writing code, building security tools, and automating security best practices. You'll need strong command of CS fundamentals, to design, build, and maintain secure software systems. - Enterprise security architecture & threat modeling. Design secure systems and guide backend, product, and platform engineers on security architecture and threat modeling for Inception's customer-facing API and enterprise deployments. - API / product security. Lead proactive threat protection for a public API product handling enterprise usage, analogous to companies exposing API surfaces like ChatGPT or Claude. - Compliance, certifications, and enterprise readiness. Lead or materially drive security compliance and certifications, including SOC 2 (including ongoing Type 2 readiness) and ISO 27001, plus data privacy and security best practices. - VPC, GDPR, incident response, and 24/7 security coverage. Operate as a staff-level "all-in-one specialist" across VPC design, network isolation, GDPR, incident response, security monitoring, and operational visibility for production systems. - Secure infrastructure and tooling. Build and maintain secure infrastructure, automation, and internal tools across Inception's product, platform, and enterprise systems — improving developer velocity while raising the security baseline. - Engineering practices. Establish and promote secure development, code review, release management, vulnerability management, and incident response practices. - Pragmatic partnership. Review systems and architectures for security risks and help engineers make pragmatic tradeoffs. Contribute beyond a narrow security lane when needed, especially across backend, infrastructure, platform, and developer tooling. We can keep each as

• . Third, Requirements (You Might Be a Fit If): list: - You've built security for enterprise-facing products, APIs, infrastructure, or compliance-heavy environments, and have worked with customers who have procurement, compliance, or customer-trust requirements. - You have hands-on experience with product/API security for customer-facing APIs. - You have driven or owned SOC 2, ISO 27001, GDPR, or comparable compliance and certification programs. - You've built or owned internal security systems, privacy infrastructure, identity and access management, encryption, cloud security controls, mTLS, policy systems, or security services exposed via APIs. - You're proficient in Python; comfort with at least one systems language such as Go, Rust, or C++ is a plus. - You're fluent with modern software development, CI/CD, deployment automation, Kubernetes/Docker, infrastructure as code, and cloud platforms such as AWS or Azure. - You can operate independently in a fast-moving startup without a large security organization around you, and bring startup pace rather than big-tech-only conservatism. - You partner with fast-moving engineering teams as an enabler, not a blocker, with strong empathy for customer experience and developer velocity. - BS/MS/PhD in Computer Science or a related field, or equivalent experience. We'll put as
  • . Fourth, Qualifications: maybe we could treat "Nice to Have" as Qualifications? But we already have Requirements. Could have Skills section for Nice to Have. Let's follow instruction: Use headings for Skills if we have content. Nice to Have list: - Experience as an early or founding security engineer at a startup or fast-growing engineering organization, helping scale towards 100+ org size. - Experience preparing companies for enterprise customers, security reviews, SOC 2 Type 2, ISO 27001, GDPR, or similar programs. - Background in backend engineering, platform engineering, infrastructure, or DevOps before specializing in security. - Experience building security tooling, developer platforms, or automation that engineers actually use. - Familiarity with monitoring, observability, vulnerability management, and incident response tooling. - Experience securing AI/ML infrastructure, GPU-intensive workloads, inference pipelines, serving APIs, or large-scale cloud environments. (Direct AI-specific security experience is not required.) - Experience with application security, threat modeling, secure SDLC, privacy engineering, or customer-facing security reviews. We'll put under

    Skills

    maybe. Fifth, Benefits: from "Perks & Benefits": - Competitive salary and equity in a rapidly growing startup - Flexible vacation and paid time off (PTO) - Health, dental, and vision insurance - 401k match - Catered meals (breakfast, lunch, & dinner) - Commuter subsidies - A collaborative and inclusive culture We'll put as
    • . Sixth, Pay: from Compensation: "The annual base salary range for this role is $200,000 – $350,000 USD. Final compensation is determined based on experience, skills, and qualifications. Equity and benefits are included in the total package." We'll put as

      . We should not include About Us? Could be part of About the role? The instruction says include sections only when posting has real specific content. About Us is substantive but not one of the prescribed headings. We could maybe include as "About the company" but not in list. Since not in allowed headings, we should omit. The allowed headings are limited to those; we should not add others. So we omit About Us. Now produce HTML. Make sure no extra text. Let's craft:

      About the role

      We are hiring across seniority levels for a Founding Security Engineer to build the security foundation for a frontier AI platform serving enterprise customers — owning product/API security, enterprise security architecture, compliance readiness, and incident response as the company scales. You'll own and drive the systems, processes, and infrastructure that make Inception secure by default: cloud security, network isolation, access controls, incident response, compliance readiness, secure engineering workflows, and customer-facing security requirements. This role is ideal for someone who lives and breathes security, but is still a builder at heart — someone who can design secure systems, write production code, automate workflows, and partner deeply with engineering teams. This is not a narrow GRC, IT, AI safety, or policy-only role, and it is not AI-specific security research. We're looking for traditional enterprise/product security execution from an "inverted T" engineer: broad software engineering ability with a deep spike in security. You'll be the internal expert who helps us navigate enterprise security, privacy, compliance, and infrastructure risk as we scale — a technical leader, not a friction point for the engineering team.

      Responsibilities

      • Software engineering fundamentals: This is a software engineering role with a security specialization. Expect to spend 70%+ of your time writing code, building security tools, and automating security best practices. You'll need strong command of CS fundamentals, to design, build, and maintain secure software systems.
      • Enterprise security architecture & threat modeling. Design secure systems and guide backend, product, and platform engineers on security architecture and threat modeling for Inception's customer-facing API and enterprise deployments.
      • API / product security. Lead proactive threat protection for a public API product handling enterprise usage, analogous to companies exposing API surfaces like ChatGPT or Claude.
      • Compliance, certifications, and enterprise readiness. Lead or materially drive security compliance and certifications, including SOC 2 (including ongoing Type 2 readiness) and ISO 27001, plus data privacy and security best practices.
      • VPC, GDPR, incident response, and 24/7 security coverage. Operate as a staff-level "all-in-one specialist" across VPC design, network isolation, GDPR, incident response, security monitoring, and operational visibility for production systems.
      • Secure infrastructure and tooling. Build and maintain secure infrastructure, automation, and internal tools across Inception's product, platform, and enterprise systems — improving developer velocity while raising the security baseline.
      • Engineering practices. Establish and promote secure development, code review, release management, vulnerability management, and incident response practices.
      • Pragmatic partnership. Review systems and architectures for security risks and help engineers make pragmatic tradeoffs. Contribute beyond a narrow security lane when needed, especially across backend, infrastructure, platform, and developer tooling.

      Requirements

      • You've built security for enterprise-facing products, APIs, infrastructure, or compliance-heavy environments, and have worked with customers who have procurement, compliance, or customer-trust requirements.
      • You have hands-on experience with product/API security for customer-facing APIs.
      • You have driven or owned SOC 2, ISO 27001, GDPR, or comparable compliance and certification programs.
      • You've built or owned internal security systems, privacy infrastructure, identity and access management, encryption, cloud security controls, mTLS, policy systems, or security services exposed via APIs.
      • You're proficient in Python; comfort with at least one systems language such as Go, Rust, or C++ is a plus.
      • You're fluent with modern software development, CI/CD, deployment automation, Kubernetes/Docker, infrastructure as code, and cloud platforms such as AWS or Azure.
      • You can operate independently in a fast-moving startup without