Senior Software Engineer

We need to output HTML fragment with sections: About the role? Actually we have "Who we are" and "Job summary" and "What you will do", "What you will have", "Nice to have", "Benefits". Also there is compensation info (Base Salary). We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to map content. We have "Who we are" (company description) maybe could be "About the role"? Actually "About the role" is typical heading for role description. Could use "About the role" for job summary and who we are? But we need to not repeat job title as heading. We can put a short paragraph about company under "About the role"? Or maybe "About the role" is for role description; "Who we are" could be part of that. We'll include "About the role" with content from "Who we are" and "Job summary". Then "Responsibilities" from "What you will do". Then "Requirements" from "What you will have" (mandatory). Then "Nice to have" could be "Qualifications" or "Skills"? Actually we have separate sections: Qualifications, Skills. We could put "Nice to have" under "Qualifications" maybe? But we need to follow instruction: Use headings only when posting has real specific content. We have content for Nice to have, so we could create a section "Qualifications" for nice-to-have? Or "Skills"? The nice-to-have list includes experience with event-driven architectures, familiarity with digital certificates, PKI, agentic AI workflows, multi-tenant SaaS, AI-first practices, open-source contributions, advanced deployment patterns. That could be under "Qualifications" or "Skills". We'll decide: Use "Qualifications" for nice-to-have. Use "Skills" for required skills? But we already have "Requirements" for mandatory. Could also have "Skills" for technical skills list (Java, React, etc.) but those are in requirements. Might be redundant. Better to have sections: About the role, Responsibilities, Requirements, Benefits, Pay. Possibly also Skills? But we can combine. We must not create Pay/Schedule/Benefits unless posting actually states them. Benefits are stated (list). Pay is stated (Base Salary range). Schedule not mentioned, so omit. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, application instructions, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to extract content. Let's parse: Who we are: DigiCert is a global leader... (description). Job summary: The DigiCert Platform team... (description). Combine into About the role. What you will do: list of responsibilities (bullet points). We'll put each as

• . What you will have: list of mandatory qualifications (bullet points). We'll put as
• under Requirements. Nice to have: list of nice-to-have (bullet points). We'll put as
• under Qualifications. Benefits: list of benefits (bullet points). We'll put under Benefits. Pay: Base Salary range: $170,000 USD - $200,000 USD. We'll put as

  maybe. We must not include headings for empty sections. We must not include duplicated lines. We must not include application instructions like "To protect candidate information..." etc. We must not include EEO statements. We must not include "Compensation Transparency:" paragraph? That is about pay transparency; but we already have pay range. The paragraph includes details about compensation determination; could be considered part of Pay section? It's substantive but maybe we can include as part of Pay section as prose. However instruction: Prefer a few substantive sections over many thin ones. We could include that paragraph under Pay as well. But we must not include boilerplate like "Compensation Transparency: The annualized base salary range for this position is outlined below..." That's not boilerplate; it's specific to the posting. Could include. We must not include "For more information regarding our comprehensive benefits, see the benefits section." That's referencing benefits section; we can keep maybe but it's somewhat generic. Might be considered boilerplate? It's referencing internal; maybe we can drop. We must not include "If you would like more information about compensation or benefits, we are happy to provide additional details during the hiring process." That's generic; maybe drop. We'll keep the base salary range and maybe a short note that compensation determined based on experience etc. But that is somewhat generic; but it's still specific to the posting. I'd include it as part of Pay section. Now produce HTML. Structure:

  About the role

  ...combined who we are and job summary...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  Base Salary: $170,000 USD - $200,000 USD. Compensation offers will be determined based on experience, skills, qualifications, job duties, business needs, and location. Total compensation may include base pay, bonus, equity, or other incentives.

  We must not include schedule. Now we need to ensure we preserve all substantive information from the lists. Let's extract responsibilities list exactly: - Lead the design and development of Java backend services and RESTful APIs — driving architectural decisions, defining API contracts, and setting the bar for code quality across the team - Own complex full-stack features spanning Java backend services and React frontend, from requirements through production, including performance optimization and long-term maintainability - Architect and implement IAM flows — OAuth 2.0, OIDC, and SAML — with deep, production-tested knowledge of token lifecycle, session management, multi-tenant identity, and integration with Okta, Azure AD, or equivalent identity providers - Champion security engineering practices: secure-by-design architecture, threat modeling, RBAC/ABAC patterns, token security, and zero-trust principles applied in a platform context - Drive CI/CD maturity — own and improve pipelines using Jenkins, GitHub Actions, or similar; define deployment strategies (blue/green, canary) and reliability standards across services - Operate confidently with infrastructure: Docker, Kubernetes, and IaC tools (Terraform, Helm) at production scale, including cost-aware design and platform reliability - Use AI coding agents fluently (GitHub Copilot, Cursor, Claude Code, etc.) as a native part of your daily workflow — and help the team do the same; bring judgment on where AI accelerates delivery and where human review is non-negotiable - Integrate and ship AI/LLM capabilities into platform features: LLM API integration, prompt engineering, RAG patterns, and agentic workflows embedded into real product experiences - Mentor and grow junior and mid-level engineers through code reviews, design feedback, pairing sessions, and technical guidance - Own observability and incident response for the services you build — define SLOs, instrument with New Relic, Splunk, or Datadog, and lead post-mortems that improve the system - Partner closely with Product and Design to shape requirements, push back on scope when needed, and consistently deliver value on time Now requirements list (What you will have): - +5 years of professional software engineering experience, with meaningful tenure in a platform or identity-adjacent domain - Use AI coding agents (Cursor, GitHub Copilot, Claude, etc.) as a native part of your workflow — not occasionally, but daily and fluently - Identify where AI can accelerate delivery and advocate for AI-first practices within the team - Expert-level Java development: Spring Boot, RESTful API design, microservices patterns, performance tuning, and production reliability - Strong React engineering: hooks, component architecture, state management (Redux or equivalent), and experience building complex, accessible UIs - Deep, production-grade knowledge of OAuth 2.0, OIDC, and SAML — you've debugged token flows, handled edge cases in multi-tenant environments, and integrated with enterprise identity providers like Okta or Azure AD - Strong security engineering fundamentals: threat modeling, RBAC/ABAC, secure token handling, input validation, and security-first design in a platform context - Proficiency with CI/CD pipelines, Docker, Kubernetes, and IaC tools (Terraform or Helm); comfortable owning infrastructure, not just consuming it - Solid command of relational databases (PostgreSQL or MySQL): schema design, query optimization, indexing strategy, and performance at scale - Hands-on experience with cloud platforms (AWS, GCP, or Azure) and cloud-native design patterns - Strong communication skills — able to drive alignment across engineering, product, and security stakeholders; comfortable presenting design decisions and tradeoffs Now nice-to-have list: - Experience with event-driven architectures — Kafka or similar — for real-time security event processing or audit pipelines - Familiarity with digital certificates, PKI, or the broader DigiCert ONE trust platform - Familiarity with agentic AI workflows — building tools that use LLMs, function calling, or autonomous pipelines - Experience building or operating multi-tenant SaaS platforms with strict isolation requirements - Track record of introducing AI-first development practices to a team — beyond personal use, raising the floor for others - Contributions to open-source projects in identity, security, or platform infrastructure - Experience with advanced deployment patterns (feature flags, progressive rollouts) and experimentation frameworks in a platform context Now benefits list: - Competitive compensation and comprehensive health, dental, and vision coverage - Retirement savings programs with company matching (401(k) or RRSP) - Generous paid time off, including holidays, and vacation - Paid parental leave and family support benefits - Life and disability coverage - Flexible spending and health savings options (where applicable) - Health and wellness support, including gym reimbursement and wellness programs - Employee Assistance Program with 24/7 confidential support for employees and families - Education assistance and professional development opportunities - Access to LinkedIn Learning and continuous learning resources - Employee referral bonus program and additional company perks and discounts - Internal rewards and recognition platform (Motivosity) to celebrate and acknowledge project wins, milestone achievements, and the outstanding contributions of our colleagues - Business travel insurance and global employee support programs Now About the role content: combine Who we are and Job summary. Who we are: "DigiCert is a global leader in intelligent trust. We protect the digital world by ensuring the security, privacy, and authenticity of every interaction. Our AI-powered DigiCert ONE platform unifies PKI, DNS, and certificate lifecycle management, to secure infrastructure, software, devices, messages, AI content and agents. Learn why more than 100,000 organizations, including 90% of the Fortune 500, choose DigiCert to stop today’s threats and prepare for a quantum-safe future at www.digicert.com" Job summary: "The DigiCert Platform team is the foundation everything else runs on. We build and own the DigiCert One platform that powers every other DigiCert product — the shared infrastructure, services, and identity layer that product teams across DigiCert depend on to ship. Most critically, we own IAM for the entire DigiCert product portfolio: every login, every session, every access decision across DigiCert ONE flows through our team.This is high-leverage, high-stakes