Staff Full Stack Engineer

We need to output HTML fragment with sections: About the role (maybe "About Xpoint" but they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for section headings. We need to include sections only if posting has real specific content. We have About Xpoint (description). That can be "About the role" maybe? The posting includes "About Xpoint:" and "Job Summary:" etc. We can combine into About the role. We'll include About the role section with content from About Xpoint and Job Summary? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can have About the role with paragraphs summarizing about Xpoint and job summary. Responsibilities: we have Job Responsibilities list. Requirements: we have Job Requirements (Required and Preferred). Could split into Requirements and maybe Qualifications? They said we can have Requirements, Qualifications, Skills sections. We need to decide which to include. The posting has Required and Preferred. Could treat Required as Requirements, Preferred as Qualifications or Skills. But we should not create thin sections. We have substantial content for both. Could make Requirements (Required) and Qualifications (Preferred). Or combine into Requirements and Skills. Let's see: They said "Prefer a few substantive sections over many thin ones." So maybe we have About the role, Responsibilities, Requirements (including both required and preferred), Benefits. No Pay or Schedule as not specified. So we output those four sections. We must use

• for any list of duties/requirements/benefits. For prose, use

  . For headings,

  . We need to preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists. We must remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to include Benefits Package details as list. We must not include Pay or Schedule sections because not specified. We need to ensure we don't create empty sections. Let's extract content. About Xpoint: paragraph about Xpoint builds geolocation compliance layer etc. Then "It is a genuinely hard engineering problem..." etc. Then "We’re small enough..." etc. Job Summary: paragraph about seeking Staff Full Stack Engineer, building features end-to-end, etc. We can combine these into About the role section. Responsibilities: list of bullet points. Job Responsibilities bullet list: - Design, build, test, and ship features end-to-end across the stack, from SDK and Portal through APIs, backend services, and the data pipeline. - Take a customer problem from report to verified fix regardless of which component it originates in, following the behaviour across system boundaries rather than handing it off. - Contribute production code to our Java/Spring backend services, our Kotlin Multiplatform SDK and its native layers, and our Angular/TypeScript Portal and JavaScript Web SDK. - Ensure consistent behaviour and feature parity across platforms, including naming, metrics, and semantics shared between native and web implementations. - Raise the technical standard through code review, pairing, and documenting architectural decisions and their rationale. - Own what you ship in production, including performance, on-call participation, incident response, and root-cause resolution. - Partner with Product, QA, SRE, and Compliance to define requirements, scope testing, and deliver reliable production releases. - Ensure releases meet regulatory and compliance requirements, including appropriate testing, documentation, change controls, and evidence requirements. - Drive effective async collaboration across the distributed organization, clearly communicating technical decisions, progress, risks, and recommended solutions. - Use modern AI development tools to improve engineering efficiency and quality, applying appropriate judgment and guardrails. - Stay current with relevant backend, client-side, cloud, and AI technologies and identify opportunities to improve Xpoint’s engineering practices. Job Requirements: Required list (many bullet points). Preferred list. We need to decide how to split. Could have Requirements (Required) and Qualifications (Preferred). Or combine into Requirements and Skills. Since they said we can have Skills section. Let's do Requirements (Required) and Qualifications (Preferred). Or Skills (Preferred). I'd choose Requirements (Required) and Qualifications (Preferred). Both are substantive. We must preserve all details. Let's list Required bullets: - Staff-level engineering experience delivering complex features end-to-end across multiple layers of a production system - Strong backend expertise in Java and Spring/Spring Boot, including REST APIs and microservices - Strong client-side expertise in TypeScript and JavaScript, including production experience with a modern framework such as Angular - Hands-on experience with client SDK development, whether mobile, desktop, or browser, including Kotlin, Kotlin Multiplatform, or equivalent native platform experience - Experience building or maintaining SDKs consumed by third-party applications, including session lifecycle, configuration and feature-flag delivery, and integration ergonomics for client developers - Experience building and operating low-latency, high-throughput, mission-critical systems: capacity planning, load testing, rate limiting, connection and thread management, and diagnosing latency at the tail rather than the mean - Strong cloud infrastructure experience, including containers, orchestration, multi-region and multi-tenant environments - Experience with NoSQL data modeling, streaming and messaging/queueing technologies - Strong knowledge of observability, system reliability, performance optimization and production troubleshooting - Security-conscious engineering experience, including TLS, token management, certificate validation, request/response signing, and device attestation such as Play Integrity or App Attest - Strong testing practices across units, integration and automated regression testing, plus modern CI/CD and Git workflows, including branching strategy, release cutting and merge discipline - Fluency with modern AI development tools, including the ability to validate, review and override AI-generated work - Strong ownership mindset with the ability to troubleshoot across systems and drive issues through root cause and resolution - Excellent written communication and the ability to explain complex system behavior clearly to engineers, product partners, and customer-facing teams. Preferred bullets: - Experience with fraud detection, anti-abuse, device fingerprinting, anti-spoofing, or trust & safety systems - Experience with remote-desktop, virtualization, or emulator detection techniques, including side-channel and fingerprinting approaches - Familiarity with Kotlin Multiplatform and native interop layers, or with React Native and Flutter bridging layers - Familiarity with geospatial technologies, positioning systems and boundary logic - Experience with real-time stream processing, or with backtesting rules or models against historical production data - Experience in regulated or audited environments - iGaming or sports betting industry experience - Experience building AI-powered product features - Start-up experience and comfort operating in a fast-moving environment Benefits Package: list: - Competitive, people-first benefits designed to support your health, financial future, and work-life balance. Xpoint is committed to investing in employees and their families with a comprehensive U.S. benefits package, including: - Comprehensive medical, dental, and vision insurance - 100% employer-paid employee health premiums - 50% employer-paid premiums for eligible dependents - 3 weeks of paid vacation starting in the first year - Paid sick time and company holidays - 401(k) retirement plan with strong company match - 100% company-paid life insurance, AD&D, and short-term disability We need to keep the introductory sentence maybe as a paragraph before the list. Now produce HTML. Structure:

  About the role

  ... (combined About Xpoint and Job Summary)

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Benefits

  Competitive, people-first benefits designed to support your health, financial future, and work-life balance. Xpoint is committed to investing in employees and their families with a comprehensive U.S. benefits package, including:

  • ...
  ...
  We must not include Pay or Schedule. Check that we didn't repeat job title. Good. Now ensure we preserve all substantive information. Did we miss any? The "How We Work — Remote and Distributed:" section includes details about remote work, time zones, written communication, travel internationally a few times each year, travel regularly to Philadelphia for in-person working sessions. Also "AI-Forward By Default:" section about AI tools usage. Also "Operating Principles:" section about eight core principles. These are substantive and should be included somewhere. Where to put? Could be part of About the role or maybe a separate section like "How we work" but we only have allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could incorporate those details into About the role or Responsibilities? The instructions: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". We can add a section like "How we work" but not in allowed list? The list is examples, not strict? It says: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But they say "Prefer a few substantive sections over many thin ones." So we could add a section like "How we work" if it's substantive. However, to be safe, we could incorporate those details into About the role or Responsibilities. The "How We Work — Remote and Distributed:" and "AI-Forward By Default:" and "Operating Principles:" are important. We should include them. We could add a section "How we work" as

  How we work

  with paragraphs covering remote work, AI usage, operating principles. That seems reasonable and not too thin. But the instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but they gave examples. Safer to stick to those examples? The phrase "e.g." indicates examples, not exclusive. However, they also say "Prefer a few substantive sections over many thin ones." Adding a new section may increase count but still okay if substantive. But we already have About the role, Responsibilities, Requirements, Qualifications, Benefits. That's five sections. Adding How we work makes six. Still few. Alternatively, we could merge How we work into About the role (makes About the role longer). That may be okay. Let's decide to include How we work as a separate section to keep clarity. The heading "How we work" is not in the examples but seems reasonable. However, the instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might be interpreted that we should only use those headings. To be safe, I'll incorporate those details into About the role and maybe Responsibilities. Where does "How We Work — Remote and Distributed:" fit? Could go under About the role as additional paragraphs. "AI-Forward By Default:" could go under Responsibilities (since it's about using AI tools) or About the role. "Operating Principles:" could go under About the role. Thus we can keep only the four sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. That's five sections. Let's incorporate all details into About the role: include description of Xpoint, job summary, how we work (remote, time zones, written communication, travel), AI-forward, operating principles. That will be a long paragraph but okay. We must not invent or summarize away detail; we need to preserve all specifics. We'll need to include each bullet point from those