Platform Engineer

We need to output HTML fragment with sections: About Authorium, About Position, What You'll Be Doing, Requirements (maybe split into Must Have and Nice to Have?), Compensation & Benefits. Use

for each section heading. Use

• for lists. Use

  for prose. No duplicate headings. No job title heading. No Job ID. Remove boilerplate. Ensure we preserve all substantive info. We need to include sections only if posting has real specific content. We have content for About Authorium, About Position, What You'll Be Doing, Requirements (must have and nice to have), Compensation & Benefits (salary, equity, benefits, 401k, PTO, home office stipend, wellness benefits, commuter stipend). Also note hybrid work requirement: "If the job posting is listed as hybrid or an employee is located within 30 miles of one of our hub cities (San Francisco and Washington, DC), hybrid work is required." That's a condition; we could include in Compensation & Benefits or maybe a separate note. But we can include as a paragraph under Compensation & Benefits or maybe under About Position? It's about work arrangement. Could be a separate section "Work Arrangement" but not in allowed headings list; allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: About Authorium -> maybe "About the role"? Actually "About Authorium" is company description, not role. Could be "About the role"? But they said use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings when appropriate. We have content that maps: About Authorium could be "About the role"? Not exactly. But maybe we treat "About Authorium" as "About the role"? However they said do NOT repeat the job title as a heading. They didn't forbid other headings. The examples are just examples; we can use those headings if they match content. We have: About Authorium (company overview). Could be "About the role"? Not ideal. Could use "About Authorium" as heading? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to use those headings where applicable. Let's map: - About Authorium: could be "About the role"? Actually "About the role" would be about the position, not company. We have "About Position" separate. So we could have two sections: "About the role" (maybe combine About Authorium and About Position?). But we need to preserve all info. Could do:

  About the role

  Authorium is transforming the way agencies manage complex, document-centric workflows...

  About Position While Authorium is a distributed company...

  But that mixes company and position. Might be okay. Alternatively we could have separate headings: "About Authorium" and "About Position". The instruction didn't forbid other headings, just gave examples. I'd lean to keep them as they are for clarity. The important is to use

  for section headings. So we can use

  About Authorium

  ,

  About Position

  , etc. We must not include Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation and benefits, so we can include Benefits and Pay. Could combine into one section "Compensation & Benefits" but heading examples include Benefits and Pay separate. We could have

  Benefits

  and

  Pay

  . But we have both salary range and benefits list. Could split. Better:

  Pay

  with salary range and equity.

  Benefits

  with list of benefits. Also note hybrid work requirement: could be under Schedule? Not exactly schedule. Could be under "Schedule" heading? Not really. Could be under "Benefits" as a note? Or we could add a short paragraph under About Position about hybrid requirement. Since it's not a standard heading, we can just include as a paragraph. We must not include filler like "commensurate with experience". Not present. Now produce HTML fragment. Structure:

  About Authorium

  ...

  About Position

  ...

  What You'll Be Doing

  • ...
  ...

  Requirements

  Maybe split into Must Have and Nice to Have as subheadings? Could use

  but not allowed? Only

  for section headings. Could embed as Must Have within

  or

  . Better: Use

  Requirements

  then

  Must Have:

  then
  ... then

  Nice to Have:

  then
  ... That preserves info.

  Pay

  Salary: $148,750 - $201,250
  Offers equity

  Benefits

  • 100% benefits coverage for employee
  ... etc.
  Also include note about hybrid work requirement maybe under About Position or as a separate paragraph after Benefits. Let's extract exact text. About Authorium paragraph: "Authorium is transforming the way agencies manage complex, document-centric workflows. Our unified platform integrates essential administrative functions, from Budgeting to Procurement to Contracting, streamlining government operations. By consolidating data from documents, emails, and spreadsheets into a unified data layer, we drive insights and visibility. We believe in the power of collaboration and data to transform government operations. Come innovate with us and drive positive change!" About Position paragraph: "While Authorium is a distributed company, our SF office is where we tackle our most intricate "war room" challenges — from modularizing our core domain to whiteboarding the next generation of our workflow engine. You will be a primary driver of the technical integrity of our platform, setting the quality bar and shipping the features that will power our next major phase of expansion. We have deep product market fit and are scaling to meet the demands of the world's most complex government agencies." What You'll Be Doing bullet points: The text: "Architecting the Platform: Own the most complex platform work — permissions, authentication, enterprise integrations, CI/CD pipelines, and API management.High-Bandwidth Collaboration: Work with engineering leadership to design platform capabilities, resolve production incidents, and translate engineering pain points into infrastructure solutions.Technical Excellence: Set the standard for platform reliability. You'll lead infrastructure code reviews, define SLOs, and drive improvements to observability, automated testing, and deployment safety.AI-Native Workflow: Use Cursor and Claude to automate infrastructure toil and focus on high-leverage platform design. You'll define our AI-first patterns for platform engineering — from AI-assisted runbooks to automated incident triage." We need to split into list items. Each bullet seems separated by a period? Actually after each colon there is a description, then next starts with capital letter. We'll split at each bolded heading? We'll make each as
  • containing the full sentence. Thus list items: - Own the most complex platform work — permissions, authentication, enterprise integrations, CI/CD pipelines, and API management. - Work with engineering leadership to design platform capabilities, resolve production incidents, and translate engineering pain points into infrastructure solutions. - Set the standard for platform reliability. You'll lead infrastructure code reviews, define SLOs, and drive improvements to observability, automated testing, and deployment safety. - Use Cursor and Claude to automate infrastructure toil and focus on high-leverage platform design. You'll define our AI-first patterns for platform engineering — from AI-assisted runbooks to automated incident triage. But need to keep the leading phrase "Architecting the Platform:" etc. Could include as part of item. We'll produce items like:
  • Architecting the Platform: Own the most complex platform work — permissions, authentication, enterprise integrations, CI/CD pipelines, and API management.
  • High-Bandwidth Collaboration: Work with engineering leadership to design platform capabilities, resolve production incidents, and translate engineering pain points into infrastructure solutions.
  • Technical Excellence: Set the standard for platform reliability. You'll lead infrastructure code reviews, define SLOs, and drive improvements to observability, automated testing, and deployment safety.
  • AI-Native Workflow: Use Cursor and Claude to automate infrastructure toil and focus on high-leverage platform design. You'll define our AI-first patterns for platform engineering — from AI-assisted runbooks to automated incident triage.
  Now Requirements Must Have list: "Must Have 3+ years of professional experience in platform, infrastructure, or DevOps engineering, with strong fundamentals in distributed systems, networking, and cloud architecture.Systems Thinker: Proven track record designing and operating reliable, scalable infrastructure — including service meshes, internal tooling, and developer-facing APIs or abstractions.Security Minded: You treat security as a first-class platform concern — deep understanding of secrets management, network policies, IAM models, and supply chain security.Quality Obsessed: A history of high-quality infrastructure-as-code, runbooks, and a drive to build self-service systems that reduce toil for the entire engineering org." We need to split into list items. Each seems separated by a period after each heading? Actually after each colon there is description then next heading starts with capital letter. We'll split similarly: - 3+ years of professional experience in platform, infrastructure, or DevOps engineering, with strong fundamentals in distributed systems, networking, and cloud architecture. - Systems Thinker: Proven track record designing and operating reliable, scalable infrastructure — including service meshes, internal tooling, and developer-facing APIs or abstractions. - Security Minded: You treat security as a first-class platform concern — deep understanding of secrets management, network policies, IAM models, and supply chain security. - Quality Obsessed: A history of high-quality infrastructure-as-code, runbooks, and a drive to build self-service systems that reduce toil for the entire engineering org. Now Nice to Have list: "AWS Depth: Hands-on experience with ECS/EKS, CloudWatch, IAM, VPC design, Parameter Store, and modern IaC tooling (Terraform, Pulumi, CDK).Developer Experience Focus: Experience building internal platforms, golden paths, or self-service deployment tooling that measurably improves engineering velocity.Regulated Industry Experience: Previous work in compliance-heavy environments such as GovTech, FinTech, or HealthTech (FedRAMP, SOC 2, HIPAA) — ideally with a focus on infrastructure compliance controls.Observability & Reliability: Experience owning SLOs/SLAs, building out logging/metrics/tracing stacks (Datadog, OpenTelemetry, etc.), and leading incident response.Startup Experience: Previous experience at a company in the $5M–$30M ARR range.If the job posting is listed as hybrid or an employee is located within 30 miles of one of our hub cities (San Francisco and Washington, DC), hybrid work is required." We need to split items similarly: - AWS Depth: Hands-on experience with ECS/EKS, CloudWatch, IAM, VPC design, Parameter Store, and modern IaC tooling (Terraform, Pulumi, CDK). - Developer Experience Focus: Experience building internal platforms, golden paths, or self-service deployment tooling that measurably improves engineering velocity. - Regulated Industry Experience: Previous work in compliance-heavy environments such as GovTech, FinTech, or HealthTech