Senior Software Engineer (AM+ Auth)
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the posting.
Key content:
- Intro about Gravitee (company description). Could be "About the role"? Actually "About the role" is a heading for description of role. The intro about company could be part of "About the role" or maybe "About Gravitee"? But headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to use some of these.
We need to include sections only if there is real content.
We have:
- About the role: description of mission, momentum, DNA, why join us, the role description. Could be placed under "About the role". Should include prose.
- Responsibilities: bullet list of "What You Will Be Doing". That's a list.
- Requirements/Essential Skills: list of essential skills.
- Desired Skills: could be under "Skills" or "Qualifications". The headings allowed: Qualifications, Skills. We could put Essential Skills under "Requirements" or "Qualifications". Desired Skills under "Skills". Or we could combine.
- Benefits: there is a list under "Life at Gravitee" with salary, medical coverage, pension/401k, stock options, holidays, mental health days, wellness allowance, birthday off, professional development budget, hybrid work culture, quarterly team events, annual offsite, collaborative culture, opportunities to grow. Also mention Salary of $160,000. So we have Pay and Benefits. Pay: Salary of $160,000. Benefits: other items.
- Schedule: Not explicitly mentioned. There's mention of hybrid work culture, but not schedule specifics. So we should not create Schedule section unless posting actually states them. It does not give schedule like full-time, remote, etc. It mentions hybrid work culture but not explicit schedule. So we should omit Schedule.
- Also mention "US-hours Level 3 and Level 4 escalations" etc. That's part of responsibilities.
- Also mention "You will split your time roughly 80% feature delivery and 20% L3/L4 support and bug fixing (it varies week to week)". That's schedule-ish but not explicit schedule; could be considered schedule but it's about time split. Might be considered schedule? The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state time split, but not schedule like hours per week. Might be considered schedule? Safer to omit Schedule because it's not explicit like "Full-time", "40 hours/week". We'll omit.
- Also mention "Don't just watch the AI revolution..." etc. That's part of About the role.
- Also mention "At Gravitee, we invest in humans..." etc. That's part of Benefits/Life at Gravitee.
- Also mention EEO statement etc. Remove boilerplate.
- Also mention "By applying, you consent..." that's boilerplate; remove.
- Also mention "Gravitee is a 2025 Gartner® Magic Quadrant™ Leader..." that's company intro; could be part of About the role.
Thus sections:
About the role
with prose summarizing company mission, momentum, DNA, why join us, the role description (including that it's new role, establishing US-hours ownership, etc). Should preserve all substantive info; we need to not lose details. We'll need to include paragraphs.
Then Responsibilities
with - list of bullet points from "What You Will Be Doing". Need to preserve all bullet points.
Then
Requirements
(or Qualifications) for Essential Skills list.
Then Skills
for Desired Skills list.
Then Benefits
with list of benefits (including salary? Actually salary is Pay). We'll have Pay section separate: Pay
with Salary of $160,000
. Benefits: list other items.
We need to ensure we don't create sections with filler. All have content.
Check for duplication: Ensure we don't repeat same info.
Now craft HTML.
We'll need to escape any special characters? Not needed.
Let's extract bullet points for responsibilities:
From "What You Will Be Doing In this role, you will:" then list:
- Design and deliver features end to end, from discovery and technical design through implementation, testing, release, and iteration.
- Build and maintain identity and authorization features of Gravitee Access Management, across the AM runtime and the AM experience in Gamma.
- Implement and support OAuth 2.0 and OIDC flows (authorization code + PKCE, client credentials, token exchange), SAML 2.0 as both IdP and SP, SCIM, and FAPI/CIBA/UMA profiles.
- Work with token and session semantics — JWT, JWKS, key rotation, revocation, introspection, MFA and step-up, WebAuthn/FIDO2, and IdP federation and social login.
- Keep security behavior and upgrades safe: standards compliance, secure defaults, certificate and secret handling, consent, audit logs, and defenses against token replay, SSRF, and account takeover.
- Own safe migrations and backward compatibility across MongoDB and JDBC, and support multi-domain, multi-region deployments and login/token endpoint performance.
- Own US-hours Level 3 and Level 4 escalations for AM customers as part of the L3 pager duty rotation.
- Use LLMs and AI-assisted development tools thoughtfully for prototyping, implementation, testing, debugging, and exploration, applying sound engineering judgment to validate AI-generated work.
- Write meaningful automated tests and contribute to reliable delivery practices.
- Collaborate with product managers, designers, engineers, and technical leaders — including the AM team based in Europe — to discover effective solutions and improve them through code and design reviews.
- Share what you learn and help the team make practical choices as identity standards and protocols evolve.
Now essential skills list:
- 5+ years building and running production backend software, on a team that ships and supports its own product; you have personally resolved production incidents.
- Strong Java experience (C# accepted if the object-oriented depth is there), with Maven and a reactive stack such as Vert.x/RxJava.
- Deep working knowledge of identity standards: OAuth 2.0 and OIDC flows (authorization code + PKCE, client credentials, token exchange), SAML 2.0, SCIM, and FAPI/CIBA/UMA profiles.
- Solid grasp of token and session semantics: JWT, JWKS, rotation, revocation, introspection, MFA/step-up, WebAuthn/FIDO2, and IdP federation.
- A security-first mindset: secure defaults, certificate and secret handling, audit logging, and awareness of token replay, SSRF, and account-takeover risks.
- Experience with safe migrations and backward compatibility across persistent data stores such as MongoDB or JDBC-backed relational databases.
- Git-based workflow, code review, and writing your own automated tests.
- Hands-on experience using LLMs or AI coding assistants as part of an engineering workflow, combined with the judgment to review and improve their output.
- Clear communication, collaborative problem-solving, and the ability to take an ambiguous problem through to production.
Desired skills list:
- Experience at an API gateway, proxy, or service-mesh vendor, or on the API platform team of a large company (e.g., Kong, Google Apigee, MuleSoft, Tyk, Solo.io, Traefik, WSO2).
- Kubernetes operators and CRDs; OpenAPI tooling; service mesh or Envoy experience.
- Docker, Kubernetes, and cloud-native application delivery.
- Model Context Protocol (MCP), Agent2Agent (A2A), tool calling, LLM proxies, or other emerging AI protocols and standards. Prior production experience is not required.
- Building or operating LLM-powered applications, RAG systems, or agentic workflows — especially their security, governance, and observability needs.
- Open-source software or enterprise developer platforms.
Now benefits list (Life at Gravitee):
- Salary of $160,000 (we will put in Pay)
- Competitive medical coverage.
- Pension / 401(k) program options.
- Stock options - you build it, you own it.
- 25 days of holiday plus in-country national holidays.
- Three mental health days and a wellness allowance.
- Your birthday off. 🎉
- A professional development budget to support your growth.
- A hybrid work culture with hubs across regions.
- Quarterly team events and an annual company offsite.
- A collaborative, international company culture.
- Opportunities to grow your scope and career as Gravitee grows.
Also mention "At Gravitee, we believe diverse perspectives make better products and stronger teams." plus EEO statement (remove). Also mention "By applying, you consent..." (remove).
Now About the role prose: need to include company description, mission, momentum, DNA, why join us, the role description (including that it's new role, establishing US-hours ownership, etc). Let's craft a paragraph that includes all that info without losing details.
We'll need to preserve all substantive information: The mission: "We are the first to bridge traditional API Management with the new frontier of AI Agent Security". Momentum: "A high-growth Leader - combining market credibility with startup speed". DNA: "We hire people who Hold Nothing Back - passionate builders who want to redefine digital infrastructure". Don't just watch the AI revolution... Build the infrastructure that controls and secures it. The Role: "We are looking for a Senior Software Engineer to build and maintain the identity and authorization features of Gravitee Access Management (AM) — across the AM runtime and the access-management experience in Gamma, Gravitee's next generation product surface. This is a new role. Today, AM engineering is based entirely in Europe. This hire establishes US-hours ownership of Level 3 and Level 4 authentication and authorization incidents, and adds delivery capacity toward AM parity in Gamma — part of building sustainable L3/L4 engineering capability in the US. You will split your time roughly 80% feature delivery and 20% L3/L4 support and bug fixing (it varies week to week), working as an embedded member of the AM team, which is based in Europe."
Also earlier: "Gravitee is a 2025 Gartner® Magic Quadrant™ Leader, on a mission to govern the world’s intelligence. We deliver the industry’s most advanced platform for Any API, Any Event, and Any AI Agent, trusted by global leaders like Michelin, Roche, and Blue Yonder."
We'll combine.
Now produce HTML.
We'll need to ensure we don't include any stray text outside HTML fragment.
Let's craft:
About the role
Gravitee is a 2025 Gartner® Magic Quadrant™ Leader, on a mission to govern the world’s intelligence. We deliver the industry’s most advanced platform for Any API, Any Event, and Any AI Agent, trusted by global leaders like Michelin
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Key content: - Intro about Gravitee (company description). Could be "About the role"? Actually "About the role" is a heading for description of role. The intro about company could be part of "About the role" or maybe "About Gravitee"? But headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to use some of these. We need to include sections only if there is real content. We have: - About the role: description of mission, momentum, DNA, why join us, the role description. Could be placed under "About the role". Should include prose. - Responsibilities: bullet list of "What You Will Be Doing". That's a list. - Requirements/Essential Skills: list of essential skills. - Desired Skills: could be under "Skills" or "Qualifications". The headings allowed: Qualifications, Skills. We could put Essential Skills under "Requirements" or "Qualifications". Desired Skills under "Skills". Or we could combine. - Benefits: there is a list under "Life at Gravitee" with salary, medical coverage, pension/401k, stock options, holidays, mental health days, wellness allowance, birthday off, professional development budget, hybrid work culture, quarterly team events, annual offsite, collaborative culture, opportunities to grow. Also mention Salary of $160,000. So we have Pay and Benefits. Pay: Salary of $160,000. Benefits: other items. - Schedule: Not explicitly mentioned. There's mention of hybrid work culture, but not schedule specifics. So we should not create Schedule section unless posting actually states them. It does not give schedule like full-time, remote, etc. It mentions hybrid work culture but not explicit schedule. So we should omit Schedule. - Also mention "US-hours Level 3 and Level 4 escalations" etc. That's part of responsibilities. - Also mention "You will split your time roughly 80% feature delivery and 20% L3/L4 support and bug fixing (it varies week to week)". That's schedule-ish but not explicit schedule; could be considered schedule but it's about time split. Might be considered schedule? The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state time split, but not schedule like hours per week. Might be considered schedule? Safer to omit Schedule because it's not explicit like "Full-time", "40 hours/week". We'll omit. - Also mention "Don't just watch the AI revolution..." etc. That's part of About the role. - Also mention "At Gravitee, we invest in humans..." etc. That's part of Benefits/Life at Gravitee. - Also mention EEO statement etc. Remove boilerplate. - Also mention "By applying, you consent..." that's boilerplate; remove. - Also mention "Gravitee is a 2025 Gartner® Magic Quadrant™ Leader..." that's company intro; could be part of About the role. Thus sections:
About the role
with prose summarizing company mission, momentum, DNA, why join us, the role description (including that it's new role, establishing US-hours ownership, etc). Should preserve all substantive info; we need to not lose details. We'll need to include paragraphs. ThenResponsibilities
with- list of bullet points from "What You Will Be Doing". Need to preserve all bullet points.
Then
Requirements
(or Qualifications) for Essential Skills list. ThenSkills
for Desired Skills list. ThenBenefits
with list of benefits (including salary? Actually salary is Pay). We'll have Pay section separate:Pay
withSalary of $160,000
. Benefits: list other items. We need to ensure we don't create sections with filler. All have content. Check for duplication: Ensure we don't repeat same info. Now craft HTML. We'll need to escape any special characters? Not needed. Let's extract bullet points for responsibilities: From "What You Will Be Doing In this role, you will:" then list: - Design and deliver features end to end, from discovery and technical design through implementation, testing, release, and iteration. - Build and maintain identity and authorization features of Gravitee Access Management, across the AM runtime and the AM experience in Gamma. - Implement and support OAuth 2.0 and OIDC flows (authorization code + PKCE, client credentials, token exchange), SAML 2.0 as both IdP and SP, SCIM, and FAPI/CIBA/UMA profiles. - Work with token and session semantics — JWT, JWKS, key rotation, revocation, introspection, MFA and step-up, WebAuthn/FIDO2, and IdP federation and social login. - Keep security behavior and upgrades safe: standards compliance, secure defaults, certificate and secret handling, consent, audit logs, and defenses against token replay, SSRF, and account takeover. - Own safe migrations and backward compatibility across MongoDB and JDBC, and support multi-domain, multi-region deployments and login/token endpoint performance. - Own US-hours Level 3 and Level 4 escalations for AM customers as part of the L3 pager duty rotation. - Use LLMs and AI-assisted development tools thoughtfully for prototyping, implementation, testing, debugging, and exploration, applying sound engineering judgment to validate AI-generated work. - Write meaningful automated tests and contribute to reliable delivery practices. - Collaborate with product managers, designers, engineers, and technical leaders — including the AM team based in Europe — to discover effective solutions and improve them through code and design reviews. - Share what you learn and help the team make practical choices as identity standards and protocols evolve. Now essential skills list: - 5+ years building and running production backend software, on a team that ships and supports its own product; you have personally resolved production incidents. - Strong Java experience (C# accepted if the object-oriented depth is there), with Maven and a reactive stack such as Vert.x/RxJava. - Deep working knowledge of identity standards: OAuth 2.0 and OIDC flows (authorization code + PKCE, client credentials, token exchange), SAML 2.0, SCIM, and FAPI/CIBA/UMA profiles. - Solid grasp of token and session semantics: JWT, JWKS, rotation, revocation, introspection, MFA/step-up, WebAuthn/FIDO2, and IdP federation. - A security-first mindset: secure defaults, certificate and secret handling, audit logging, and awareness of token replay, SSRF, and account-takeover risks. - Experience with safe migrations and backward compatibility across persistent data stores such as MongoDB or JDBC-backed relational databases. - Git-based workflow, code review, and writing your own automated tests. - Hands-on experience using LLMs or AI coding assistants as part of an engineering workflow, combined with the judgment to review and improve their output. - Clear communication, collaborative problem-solving, and the ability to take an ambiguous problem through to production. Desired skills list: - Experience at an API gateway, proxy, or service-mesh vendor, or on the API platform team of a large company (e.g., Kong, Google Apigee, MuleSoft, Tyk, Solo.io, Traefik, WSO2). - Kubernetes operators and CRDs; OpenAPI tooling; service mesh or Envoy experience. - Docker, Kubernetes, and cloud-native application delivery. - Model Context Protocol (MCP), Agent2Agent (A2A), tool calling, LLM proxies, or other emerging AI protocols and standards. Prior production experience is not required. - Building or operating LLM-powered applications, RAG systems, or agentic workflows — especially their security, governance, and observability needs. - Open-source software or enterprise developer platforms. Now benefits list (Life at Gravitee): - Salary of $160,000 (we will put in Pay) - Competitive medical coverage. - Pension / 401(k) program options. - Stock options - you build it, you own it. - 25 days of holiday plus in-country national holidays. - Three mental health days and a wellness allowance. - Your birthday off. 🎉 - A professional development budget to support your growth. - A hybrid work culture with hubs across regions. - Quarterly team events and an annual company offsite. - A collaborative, international company culture. - Opportunities to grow your scope and career as Gravitee grows. Also mention "At Gravitee, we believe diverse perspectives make better products and stronger teams." plus EEO statement (remove). Also mention "By applying, you consent..." (remove). Now About the role prose: need to include company description, mission, momentum, DNA, why join us, the role description (including that it's new role, establishing US-hours ownership, etc). Let's craft a paragraph that includes all that info without losing details. We'll need to preserve all substantive information: The mission: "We are the first to bridge traditional API Management with the new frontier of AI Agent Security". Momentum: "A high-growth Leader - combining market credibility with startup speed". DNA: "We hire people who Hold Nothing Back - passionate builders who want to redefine digital infrastructure". Don't just watch the AI revolution... Build the infrastructure that controls and secures it. The Role: "We are looking for a Senior Software Engineer to build and maintain the identity and authorization features of Gravitee Access Management (AM) — across the AM runtime and the access-management experience in Gamma, Gravitee's next generation product surface. This is a new role. Today, AM engineering is based entirely in Europe. This hire establishes US-hours ownership of Level 3 and Level 4 authentication and authorization incidents, and adds delivery capacity toward AM parity in Gamma — part of building sustainable L3/L4 engineering capability in the US. You will split your time roughly 80% feature delivery and 20% L3/L4 support and bug fixing (it varies week to week), working as an embedded member of the AM team, which is based in Europe." Also earlier: "Gravitee is a 2025 Gartner® Magic Quadrant™ Leader, on a mission to govern the world’s intelligence. We deliver the industry’s most advanced platform for Any API, Any Event, and Any AI Agent, trusted by global leaders like Michelin, Roche, and Blue Yonder." We'll combine. Now produce HTML. We'll need to ensure we don't include any stray text outside HTML fragment. Let's craft:About the role
Gravitee is a 2025 Gartner® Magic Quadrant™ Leader, on a mission to govern the world’s intelligence. We deliver the industry’s most advanced platform for Any API, Any Event, and Any AI Agent, trusted by global leaders like Michelin