Software Engineer - Infrastructure Security
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. We have content for About WorkOS (company description) maybe not needed? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". The job title is not given explicitly but we can ignore. We need to decide which sections to include. The posting includes: About WorkOS (company overview), About The Security Platform Team (team description), Who we're looking for (candidate profile), Responsibilities, Qualifications, Benefits and Perks (US Only), Compensation Range. There's no explicit "Skills" separate; maybe "Who we're looking for" covers skills. Could map to "About the role" maybe combine About WorkOS and About The Security Platform Team? But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content to these headings where appropriate. However we must not create sections with filler. So we need to see if we have content for each.
- About the role: could be description of role/team. We have "About The Security Platform Team" and maybe "About WorkOS". Could combine into About the role.
- Responsibilities: we have Responsibilities section.
- Requirements: we have Qualifications section (could be Requirements). But we also have Qualifications separate. The instruction lists both Requirements and Qualifications as possible headings. We need to decide which to use. Since we have "Qualifications" heading in posting, we can use that. Could also have "Requirements" but we don't have separate. Better to use Qualifications.
- Skills: we have "Who we're looking for" which lists desired traits/skills. Could map to Skills.
- Benefits: we have Benefits and Perks.
- Pay: we have Compensation Range.
- Schedule: not mentioned; we should not include Schedule.
Thus we will output sections: About the role (combining About WorkOS and About The Security Platform Team), Skills (Who we're looking for), Responsibilities, Qualifications, Benefits, Pay.
We must not repeat job title. Use for each heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes Equal Opportunity Employer paragraph and AI tools note; we should remove that. Also "Unlimited token usage! Please inquire directly with our recruiting team for benefits available to those working outside the US." That's part of benefits? It's a note about benefits for US only; we can keep it as part of benefits? It's about benefits for US only; we can keep but maybe it's not boilerplate. It's a note about benefits for non-US; we can keep as part of benefits paragraph.
We need to preserve all substantive information: So we need to include the details about WorkOS, the team, who we're looking for, responsibilities, qualifications, benefits, compensation.
We must not invent or summarize away detail: So we need to keep specifics like "5+ years of experience", "JWTs, X.509 certificates", etc. Also benefits list: healthcare coverage, parental leave, PTO, fully remote, 401k matching, Competitive Equity, Healthcare dental vision, FSA, ST/LT Disability, Voluntary Life, Carrot fertility benefits, 20 days paid vacation + 10 holidays + unlimited sick leave, 12 weeks fully paid parental leave, Fitness stipend, Wellness stipend, Commuter benefits for hybrid employees in SF/NYC, Unlimited token usage! (maybe keep). Also note about inquiring for non-US.
We need to format lists appropriately.
Let's extract each section.
About the role: combine About WorkOS and About The Security Platform Team.
About WorkOS paragraph: "WorkOS builds modern developer tools and APIs that make it easy for companies to become Enterprise Ready. Our platform powers authentication, identity, authorization, and other critical infrastructure that developers need to securely scale their products to large organizations. We recently raised a $100M Series C, valuing the company at $2B, led by Meritech and Sapphire with participation from Greenoaks, Craft, Abstract, and Audacious. WorkOS powers enterprise features for many of the fastest-growing AI companies, including OpenAI, Cursor, and Perplexity, Sierra, and Plaid. As AI reshapes software, WorkOS is at the frontier of Human and Agent Authentication, Identity, and Access Control helping companies answer a new critical question: who are your agents, and what are they allowed to do? Our fast-growing customer base includes hundreds of modern software companies building the next generation of enterprise-ready products."
About The Security Platform Team: "The Infrastructure Security team provides and supports the primitives that enable engineering to securely build applications and meet compliance obligations, while abstracting away the underlying complexity for the best possible developer experience. Our work centers on workload identity and authorization: how internal applications authenticate to each other and to the services they depend on, and how that access is granted and enforced. We're replacing static secrets with short-lived identity credentials, bringing identity-based authentication to the services engineers use every day, and unifying how authorization is managed across the company. We're a platform engineering team with a security mission. We measure success by the security outcomes we enable and by how much engineers enjoy building on what we ship — the secure path should be the easiest path."
We can combine into a single
or maybe two
s. Use
for prose.
Skills (Who we're looking for): list of bullet points? The posting has bullet-like sentences each starting with bold? Actually it's sentences: "A platform builder. You love building infrastructure that other engineers rely on every day, and you sweat the developer experience details that make adoption effortless. Fluent in service-to-service auth. You know authentication and authorization deeply: JWTs, X.509 certificates, and when to reach for each. A systems thinker. You reason carefully about bootstrapping, circular dependencies, availability, and failure modes, especially for infrastructure that everything else depends on. A pragmatic migrator. You know that shipping the primitive is half the job. You can drive adoption across many teams, meet them where they are, and retire the legacy path. A strong partner to engineering. You build trust with engineers by understanding their priorities and making security frictionless. Excited about AI. You're embracing AI and automation to scale platform work and reduce toil. Curious and humble. You ask the basic questions, enjoy untangling complex systems, and bring others along with you."
We can turn each into
- items. Use
- .
Responsibilities: list of bullet points: "Build workload identity infrastructure. Make short-lived identity credentials a default part of every application's runtime environment, in partnership with application platform owners. Bring identity-based authentication to internal services. Work with the owners of major internal dependencies to support identity certificates, make them the golden path for newly onboarding applications, and drive migration of existing ones. Eliminate static secrets. Replace all static passwords and service tokens with short-lived identity credentials, and build identity-authenticated egress proxies and API abstractions that inject and automatically rotate managed secrets for the external dependencies that still require them. Unify authorization. Build a single interface and framework through which authorization policies are centrally managed and enforced."
We can make each sentence as
- .
Qualifications: list: "5+ years of experience in software engineering, with a focus on security-related platform, infrastructure, or distributed systems. Strong working knowledge of secrets management, fine-grained authorization, and workload identity systems. Familiarity with the Kubernetes ecosystem and authentication/authorization technologies such as JWTs, X.509 certificates, PKI, cert-manager, SPIFFE/SPIRE, and OPA. Experience building and operating production infrastructure that other teams depend on, with attention to availability and failure modes. Proven ability to drive cross-team adoption of platform capabilities or lead large-scale migrations."
Make each as
- .
Benefits: list: "We offer healthcare coverage for you and your family, including medical, dental, and vision. We offer parental leave, paid-time off and fully remote working arrangements. 401k matching Competitive Equity Healthcare, dental and vision coverage FSA, ST/LT Disability, Voluntary Life Carrot fertility benefits 20 days paid vacation + 10 holidays + unlimited sick leave 12 weeks fully paid parental leave Fitness: Monthly stipend for gyms, yoga classes, race registrations or whatever keeps you active Wellness: Monthly stipend for a massage, meditations class, therapy, or activities that enhance your well-being Commuter benefits for hybrid employees in SF/NYC Unlimited token usage! Please inquire directly with our recruiting team for benefits available to those working outside the US."
We need to parse into items. Some are phrases. We'll make each sentence or clause as
- . Might be many items; okay.
Pay: Compensation Range: "$175K - $275K". We'll put in
.
We must not include sections like Requirements (we have Qualifications). We'll not duplicate.
Now produce HTML fragment:
About the role
...combined text...
Skills
- ...
...
Responsibilities
...
Qualifications
...
Benefits
...
Pay
$175K - $275K
Make sure no extra whitespace? It's fine.
Now craft the combined About the role paragraph: maybe two paragraphs? Could be one with both paragraphs separated by a space. We'll just put both sentences in one
but it's long; still okay.
Let's write:
WorkOS builds modern developer tools and APIs that make it easy for companies to become Enterprise Ready. Our platform powers authentication, identity, authorization, and other critical infrastructure that developers need to securely scale their products to large organizations. We recently raised a $100M Series C, valuing the company at $2B, led by Meritech and Sapphire with participation from Greenoaks, Craft, Abstract, and Audacious. WorkOS powers enterprise features for many of the fastest-growing AI companies, including OpenAI, Cursor, and Perplexity, Sierra, and Plaid. As AI reshapes software, WorkOS is at the frontier of Human and Agent Authentication, Identity, and Access Control helping companies answer a new critical question: who are your agents, and what are they allowed to do? Our fast-growing customer base includes hundreds of modern software companies building the next generation of enterprise-ready products. The Infrastructure Security team provides and supports the primitives that enable engineering to securely build applications and meet compliance obligations, while abstracting away the underlying complexity for the best possible developer experience. Our work centers on workload identity and authorization: how internal applications authenticate to each other and to the services they depend on, and how that access is granted and enforced. We're replacing static secrets with short-lived identity credentials, bringing identity-based authentication to the services engineers use every day, and unifying how authorization is managed across the company. We're a platform engineering team with a security mission. We measure success by the security outcomes we enable and by how much engineers enjoy building on what we ship — the secure path should be the easiest path.
Now Skills list items: each bullet corresponds to each trait.
We'll extract each:
- A platform builder. You love building infrastructure that other engineers rely on every day
- for any list of duties/requirements/benefits. Use
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes Equal Opportunity Employer paragraph and AI tools note; we should remove that. Also "Unlimited token usage! Please inquire directly with our recruiting team for benefits available to those working outside the US." That's part of benefits? It's a note about benefits for US only; we can keep it as part of benefits? It's about benefits for US only; we can keep but maybe it's not boilerplate. It's a note about benefits for non-US; we can keep as part of benefits paragraph. We need to preserve all substantive information: So we need to include the details about WorkOS, the team, who we're looking for, responsibilities, qualifications, benefits, compensation. We must not invent or summarize away detail: So we need to keep specifics like "5+ years of experience", "JWTs, X.509 certificates", etc. Also benefits list: healthcare coverage, parental leave, PTO, fully remote, 401k matching, Competitive Equity, Healthcare dental vision, FSA, ST/LT Disability, Voluntary Life, Carrot fertility benefits, 20 days paid vacation + 10 holidays + unlimited sick leave, 12 weeks fully paid parental leave, Fitness stipend, Wellness stipend, Commuter benefits for hybrid employees in SF/NYC, Unlimited token usage! (maybe keep). Also note about inquiring for non-US. We need to format lists appropriately. Let's extract each section. About the role: combine About WorkOS and About The Security Platform Team. About WorkOS paragraph: "WorkOS builds modern developer tools and APIs that make it easy for companies to become Enterprise Ready. Our platform powers authentication, identity, authorization, and other critical infrastructure that developers need to securely scale their products to large organizations. We recently raised a $100M Series C, valuing the company at $2B, led by Meritech and Sapphire with participation from Greenoaks, Craft, Abstract, and Audacious. WorkOS powers enterprise features for many of the fastest-growing AI companies, including OpenAI, Cursor, and Perplexity, Sierra, and Plaid. As AI reshapes software, WorkOS is at the frontier of Human and Agent Authentication, Identity, and Access Control helping companies answer a new critical question: who are your agents, and what are they allowed to do? Our fast-growing customer base includes hundreds of modern software companies building the next generation of enterprise-ready products." About The Security Platform Team: "The Infrastructure Security team provides and supports the primitives that enable engineering to securely build applications and meet compliance obligations, while abstracting away the underlying complexity for the best possible developer experience. Our work centers on workload identity and authorization: how internal applications authenticate to each other and to the services they depend on, and how that access is granted and enforced. We're replacing static secrets with short-lived identity credentials, bringing identity-based authentication to the services engineers use every day, and unifying how authorization is managed across the company. We're a platform engineering team with a security mission. We measure success by the security outcomes we enable and by how much engineers enjoy building on what we ship — the secure path should be the easiest path." We can combine into a single
or maybe two
s. Use
for prose. Skills (Who we're looking for): list of bullet points? The posting has bullet-like sentences each starting with bold? Actually it's sentences: "A platform builder. You love building infrastructure that other engineers rely on every day, and you sweat the developer experience details that make adoption effortless. Fluent in service-to-service auth. You know authentication and authorization deeply: JWTs, X.509 certificates, and when to reach for each. A systems thinker. You reason carefully about bootstrapping, circular dependencies, availability, and failure modes, especially for infrastructure that everything else depends on. A pragmatic migrator. You know that shipping the primitive is half the job. You can drive adoption across many teams, meet them where they are, and retire the legacy path. A strong partner to engineering. You build trust with engineers by understanding their priorities and making security frictionless. Excited about AI. You're embracing AI and automation to scale platform work and reduce toil. Curious and humble. You ask the basic questions, enjoy untangling complex systems, and bring others along with you." We can turn each into
- items. Use
- . Responsibilities: list of bullet points: "Build workload identity infrastructure. Make short-lived identity credentials a default part of every application's runtime environment, in partnership with application platform owners. Bring identity-based authentication to internal services. Work with the owners of major internal dependencies to support identity certificates, make them the golden path for newly onboarding applications, and drive migration of existing ones. Eliminate static secrets. Replace all static passwords and service tokens with short-lived identity credentials, and build identity-authenticated egress proxies and API abstractions that inject and automatically rotate managed secrets for the external dependencies that still require them. Unify authorization. Build a single interface and framework through which authorization policies are centrally managed and enforced." We can make each sentence as
- . Qualifications: list: "5+ years of experience in software engineering, with a focus on security-related platform, infrastructure, or distributed systems. Strong working knowledge of secrets management, fine-grained authorization, and workload identity systems. Familiarity with the Kubernetes ecosystem and authentication/authorization technologies such as JWTs, X.509 certificates, PKI, cert-manager, SPIFFE/SPIRE, and OPA. Experience building and operating production infrastructure that other teams depend on, with attention to availability and failure modes. Proven ability to drive cross-team adoption of platform capabilities or lead large-scale migrations." Make each as
- . Benefits: list: "We offer healthcare coverage for you and your family, including medical, dental, and vision. We offer parental leave, paid-time off and fully remote working arrangements. 401k matching Competitive Equity Healthcare, dental and vision coverage FSA, ST/LT Disability, Voluntary Life Carrot fertility benefits 20 days paid vacation + 10 holidays + unlimited sick leave 12 weeks fully paid parental leave Fitness: Monthly stipend for gyms, yoga classes, race registrations or whatever keeps you active Wellness: Monthly stipend for a massage, meditations class, therapy, or activities that enhance your well-being Commuter benefits for hybrid employees in SF/NYC Unlimited token usage! Please inquire directly with our recruiting team for benefits available to those working outside the US." We need to parse into items. Some are phrases. We'll make each sentence or clause as
- . Might be many items; okay.
Pay: Compensation Range: "$175K - $275K". We'll put in
. We must not include sections like Requirements (we have Qualifications). We'll not duplicate. Now produce HTML fragment:
About the role
...combined text...
Skills
- ... ...
Responsibilities
- ...
Qualifications
- ...
Benefits
- ...
Pay
$175K - $275K
Make sure no extra whitespace? It's fine. Now craft the combined About the role paragraph: maybe two paragraphs? Could be onewith both paragraphs separated by a space. We'll just put both sentences in one
but it's long; still okay. Let's write:
WorkOS builds modern developer tools and APIs that make it easy for companies to become Enterprise Ready. Our platform powers authentication, identity, authorization, and other critical infrastructure that developers need to securely scale their products to large organizations. We recently raised a $100M Series C, valuing the company at $2B, led by Meritech and Sapphire with participation from Greenoaks, Craft, Abstract, and Audacious. WorkOS powers enterprise features for many of the fastest-growing AI companies, including OpenAI, Cursor, and Perplexity, Sierra, and Plaid. As AI reshapes software, WorkOS is at the frontier of Human and Agent Authentication, Identity, and Access Control helping companies answer a new critical question: who are your agents, and what are they allowed to do? Our fast-growing customer base includes hundreds of modern software companies building the next generation of enterprise-ready products. The Infrastructure Security team provides and supports the primitives that enable engineering to securely build applications and meet compliance obligations, while abstracting away the underlying complexity for the best possible developer experience. Our work centers on workload identity and authorization: how internal applications authenticate to each other and to the services they depend on, and how that access is granted and enforced. We're replacing static secrets with short-lived identity credentials, bringing identity-based authentication to the services engineers use every day, and unifying how authorization is managed across the company. We're a platform engineering team with a security mission. We measure success by the security outcomes we enable and by how much engineers enjoy building on what we ship — the secure path should be the easiest path.
Now Skills list items: each bullet corresponds to each trait. We'll extract each: - A platform builder. You love building infrastructure that other engineers rely on every day