Remote Lead Platform Developer

We need to output HTML fragment with sections: About the role? The description includes company intro, then description of role, responsibilities, required skills, qualifications, benefits, etc. We need to follow rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include. The posting includes: - Company description (Synergy Business Innovation & Solutions) – could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have "About the role" for description of role and company? Might be okay. - Responsibilities: list of key responsibilities (bulleted). Use

  • . - Required Skills and Qualifications: includes many bullet points. Could be split into "Requirements" and "Qualifications" or "Skills". The instruction says we can have sections Requirements, Qualifications, Skills. We need to decide based on content. The posting has "Required Skills and Qualifications" with many bullet points. Also "Required Education, certification & Experience:" with bullet points. Also "Preferred Education & Experience:" with vague text "Commensurate experience..." which is filler; we should not include a section for that if it's just filler. Also compensation details: they give a pay range: $102,298.00-$146,140 (though missing .00? Actually "$102,298.00-$146,140" missing cents on high end). They also have a lot of boilerplate about compensation varying etc. The actual posted pay range is given: "A reasonable estimate of the current pay range is: $102,298.00-$146,140". That is specific content, so we should include a Pay section with that range. However we must not include filler like "commensurate with experience". The pay range is specific, so we can include Pay. - Benefits: they list benefits in the company description paragraph: "Synergy offers its employees a generous portfolio of core and voluntary benefits including: group medical, dental, and vision insurance, company paid life, short-term, and long-term disability insurance; HSA, FSA; 401(k) with immediately vested company match; PTO/Sick Leave, 11 paid federal holidays, parental leave; tuition and training reimbursement; a referral bonus program; and life management programs." Also later: "company-funded certification opportunities, education reimbursement, and a general open-door policy". Also earlier: "dedicated career coaches available for every employee". So we have benefits content. Should include Benefits section. - Schedule: they mention "This position is designated as work-from-home." That's schedule/location info. Could be Schedule section (remote). It's specific: work-from-home. So we can include Schedule. - Also there is "Essential Job Function Physical Requirements:" with details. That could be under Requirements or Qualifications? Might be considered Requirements. But we already have many skill bullets. Could include a separate section for "Physical Requirements" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put physical requirements under Requirements or Qualifications. Probably under Requirements. We must not repeat the job title as heading. So no heading for Lead Platform Developer. We need to preserve all substantive information. Must not invent or summarize away detail. So we need to include all bullet points from responsibilities, required skills, required education, benefits, etc. However we must avoid duplication: there are duplicated lines (compensation paragraph repeated). We should include only once. We must remove boilerplate: EEO, legal, etc. Also remove duplicated lines. We need to format as HTML fragment: use

    for each section heading, then content: either

    for prose or

    • for lists. We need to decide how to split content into sections. Potential sections: - About the role: includes company description and role overview (first paragraphs). Could combine company synergy description and role description: "Synergy Business Innovation & Solutions is a premier implementer..." and "This position is designated as work-from-home." and "We’re looking for a Lead Platform Developer to own the architecture, scalability, and reliability of our core platform." That's prose. - Responsibilities: list of key responsibilities (the bullet list after "Key Responsibilities"). - Requirements: could include Required Skills and Qualifications bullet list (the long list). Also maybe Required Education, certification & Experience bullet list. Could combine both under Requirements. - Qualifications: maybe we could split skills vs qualifications, but we have limited headings. Could use Skills for the technical skill bullets, and Qualifications for education/certification. But we have many bullets overlapping. Let's see: The "Required Skills and Qualifications" bullet list includes both skills and qualifications (experience, languages, cloud, etc). Then "Required Education, certification & Experience:" includes degree requirement, Security+ if no degree, etc. Then "Preferred Education & Experience:" is filler; we skip. We could make two sections: Skills (for the technical skill bullets) and Qualifications (for education/certification). Or we could make Requirements (for skills) and Qualifications (for education). The instruction says we can use those headings. Let's do: - Skills: list of technical skills from "Required Skills and Qualifications" bullet list. - Qualifications: list from "Required Education, certification & Experience:" bullet list. But we also have "Physical Requirements" which could be under Qualifications or Requirements. Could add a subsection under Qualifications as a list? But we must not create new headings not in list. Could add a

      under Qualifications for physical requirements. That's okay. - Benefits: list from benefits paragraph. - Pay: the pay range. - Schedule: work-from-home. We need to ensure we don't create sections with filler. All sections have real content. Now we need to extract the exact content. Let's parse the posting. Company description: "Synergy Business Innovation & Solutions is a premier implementer of cutting-edge software solutions. Synergy brings the experience and expertise necessary to deliver capability that provides tangible ROI to our customers. Synergy’s core areas of expertise are in the fields of Digital Transformation, Cloud Solutions, SaaS and Low-Code/No-Code solutions, Emerging Technologies, Data analytics and Visualization, Information Assurance, and Business Process Re-Engineering." Then benefits paragraph: "Synergy offers its employees a generous portfolio of core and voluntary benefits including: group medical, dental, and vision insurance, company paid life, short-term, and long-term disability insurance; HSA, FSA; 401(k) with immediately vested company match; PTO/Sick Leave, 11 paid federal holidays, parental leave; tuition and training reimbursement; a referral bonus program; and life management programs." Then: "At Synergy, you’ll be challenged and given the opportunity to grow in your career path. In fact, growth is such a big deal to us that you will have dedicated career coaches available for every employee, company-funded certification opportunities, education reimbursement, and a general open-door policy so that you have support when you need it. Our team is eager to learn, fast-paced, and quality-driven—if that sounds like you, Synergy has a position for you!" Then: "This position is designated as work-from-home." Then description: "Description: We’re looking for a Lead Platform Developer to own the architecture, scalability, and reliability of our core platform. You’ll lead a small team of engineers, define platform standards and patterns, and build highly available services and tooling that accelerate product teams. This role is part hands-on development, part technical leadership, and part cross-functional influence." Then "Key Responsibilities" bullet list: - Own the platform architecture: Design and evolve cloud-native, multi-tenant, secure platform components (APIs, services, eventing, data pipelines, shared libraries). - Lead the team: Mentor engineers, lead code/design reviews, improve engineering practices, and drive continuous improvement. - Build platform capabilities: Authentication/authorization, service discovery, configuration, observability, feature flags, rollout/rollback tooling, and developer experience (DX) pipelines. - Reliability at scale: Implement SLOs/SLIs, error budgets, and chaos/resiliency testing; drive performance benchmarking and capacity planning. - Security by design: Champion secure coding, secrets management, dependency hygiene, and compliance needs (e.g., SOC 2, HIPAA, PCI—depending on domain). - Cloud & infra automation: Infrastructure as Code (IaC), CI/CD pipelines, environment strategy, container orchestration, ephemeral environments. - Data platform collaboration: Partner with data teams on streaming (e.g., Kafka), warehousing, schema governance, and data contracts. - Technical strategy: Evaluate build vs. buy, set platform roadmaps, deprecate legacy systems, and guide modernization. - Cross-functional collaboration: Work closely with product engineering, SRE, security, QA, and architecture to deliver platform capabilities that product teams love. - Incident leadership: Lead severity incidents, postmortems, and drive preventive improvements. Then "Required Skills and Qualifications" bullet list (the long list). Let's extract each bullet: - 7–10+ years of software engineering experience, with 2–4+ years in platform, infrastructure, or distributed systems roles referred - Expert in at least one backend language (e.g., C#/.NET, Java/Kotlin, Go, Node.js, Python). - Strong with cloud (AWS/Azure/GCP), containers (Docker, Kubernetes), CI/CD (GitHub Actions/Azure DevOps/GitLab CI/Jenkins). - Hands-on with IaC (Terraform, Pulumi, or ARM/Bicep) and environment management. - Solid understanding of distributed systems concepts: idempotency, backpressure, eventual consistency, retries/circuit breakers, caching. - Proven experience designing observability (logging, metrics, tracing) with tools like OpenTelemetry, Prometheus/Grafana, ELK, Datadog, or New Relic. - Experience leading projects, mentoring engineers, and collaborating across teams. - Clear, concise communication and stakeholder management. - Experience with event-driven architectures, Kafka/PubSub, or service mesh (Istio/Linkerd). - API design expertise (REST/GraphQL/gRPC), versioning, and contract testing (PACT). - Security depth: OAuth2/OIDC, mTLS, policy-as-code (OPA), secrets management (Vault/SM/Key Vault). - Data platform familiarity: CDC, streaming ETL, lakehouse/warehouse patterns. - Reliability practices: SRE, SLOs/error budgets, chaos engineering. - Regulated environments (e.g., SOC 2, HIPAA, PCI-DSS, FedRAMP) and audit-readiness. - Performance profiling and cost-optimization at scale. - Citizenship or Work Authorization Required: Ability to attain Federal Government Position of Trust. - Must