Lead Backend Software Engineer
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We have content for About Xpoint (company description), Job Summary, How We Work - Remote and Distributed, AI-Forward By Default, Operating Principles, Job Responsibilities, Job Requirements, Benefits Package. Also maybe "Our Stack" but not a required heading; we could include as part of Responsibilities or Requirements? The instruction: Use headings for those specific section names. We can map content accordingly.
We need to avoid repeating job title as heading. No Job ID etc.
We need to output only HTML fragment, no /, no markdown fences.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate (cookie/navigation/legal/EEO etc). There's none.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated, so we include Benefits section. Pay not mentioned, so omit. Schedule not mentioned, omit.
We need to decide which headings to use: About the role (maybe corresponds to About Xpoint + Job Summary?), Responsibilities (Job Responsibilities), Requirements (Job Requirements), Qualifications (maybe not separate; could combine with Requirements?), Skills (maybe not separate), Benefits (Benefits Package). We could also include "How We Work" as part of About the role or Responsibilities? But instruction: Use headings for those specific names; we can include only those that have content. We could include About the role (covering About Xpoint and Job Summary). Responsibilities (Job Responsibilities). Requirements (Job Requirements). Benefits (Benefits Package). Possibly also Skills? Not explicit separate list; we could omit.
We must not emit heading followed by filler/placeholder text. Ensure each heading has substantive content.
We need to format content: For prose, use
. For lists, use
- .
We need to preserve all substantive information: That includes details about location, remote, travel, etc. Should we include location info? It's at top: "Location: Philadelphia, PA / Northern New Jersey / New York, NY (Remote, US)". That's location metadata; we could fold into a short
under About the role maybe. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So location is minor metadata; we can include a short
maybe.
We need to include all substantive info: The description of Xpoint, job summary, how we work, AI-forward, operating principles, responsibilities, requirements, benefits package, our stack (maybe include under Responsibilities or Requirements? It's technical stack; could be part of Responsibilities or Requirements. Since we have no specific heading for Stack, we could include it as a
under Responsibilities or Requirements. Probably under Responsibilities as part of describing work.
We must not invent or summarize away detail: So we need to keep details like "Java and Spring Boot on AWS, across multiple regions and tenants. Kubernetes and Docker, with horizontal and node autoscaling. DynamoDB, Kinesis, Firehose, Kafka and SQS. Apache Flink for real-time rules. Athena, Glue, OpenSearch and Airflow on the data side. OpenTelemetry, Prometheus and Grafana for observability, with Sentry and PagerDuty. GitLab for source control and CI/CD." Keep that.
We need to ensure we don't repeat content.
Let's structure:
Location: Philadelphia, PA / Northern New Jersey / New York, NY (Remote, US)
About the role
About Xpoint: Xpoint builds the geolocation compliance layer for regulated online sports betting and gaming. Before an operator can accept a wager, they must prove the player is physically where the law says they must be, and prove it to a regulator, on demand. That is the problem we solve, in real time, at scale, for some of the largest betting operators in the US and internationally. It is a genuinely hard engineering problem, and an unusually interesting one: Every request is a decision, not a lookup. We fuse GPS, Wi-Fi, network, and device-integrity signals into a single allow/deny call under a hard latency budget, at volumes that spike significantly around live sports. The problem is adversarial. People actively try to defeat us through spoofed locations, VPNs and proxies, remote desktops, virtualized devices, and tampered attestation. The work sits at the intersection of distributed systems, fraud detection, and security engineering. Every decision must be explainable. Our releases are filed with state gaming regulators before they can reach production. That raises the bar for correctness, traceability, and testing in a way that most consumer engineering never has to meet. We’re small enough that your decisions have a real impact. Xpoint is gaining market share by building better technology. You’ll be one of a handful of people helping set the direction of our backend platform, with direct access to the executives making decisions about what we build.
Job Summary: Xpoint is seeking a Lead Backend Software Engineer to own the architecture, quality, and delivery of our core backend platform. This includes the Java services that process location checks, run decision and fraud rules, and return results in milliseconds. This is a hands-on engineering role, with most of your time spent writing, reviewing, and debugging production code. As the Lead, you’ll help set the technical direction, maintain high standards through code review, and mentor backend engineers by working alongside them rather than managing them. You’ll also serve as the senior backend engineer in the U.S. time zone, partnering directly with Product, QA, SRE, and Compliance to move work from planning through production.
How We Work - Remote and Distributed
maybe not a standard heading; but we could incorporate into About the role? However instruction says use headings for those specific names; but we could still include a heading not in list? 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? It says use for section headings (e.g. ...). Likely they expect only those headings. Safer to stick to those. So we should not create a heading like "How We Work - Remote and Distributed". Instead we can fold that content under About the role or Responsibilities. Probably under About the role as part of role description.
Similarly "AI-Forward By Default" and "Operating Principles" could be folded under About the role or Responsibilities.
But we need to preserve all substantive info; we can include them as paragraphs under About the role.
Thus About the role will be lengthy but okay.
Then Responsibilities: list of responsibilities.
Then Requirements: list of required and preferred.
Then Benefits: list of benefits.
We need to ensure we don't create Pay or Schedule sections.
Now craft HTML.
We'll start with location paragraph.
Then About the role: include paragraphs for About Xpoint, Job Summary, How We Work, AI-Forward, Operating Principles, Our Stack maybe.
We need to use - for any list of duties/requirements/benefits. For prose, use
.
Thus for About the role we can have multiple
elements.
Now Responsibilities: we have a list of bullet points from Job Responsibilities. We'll convert each to
- .
Requirements: we have Required and Preferred. We'll maybe separate into two
or combine with headings inside? But we cannot add extra headings besides the main ones. Could include a stating "Required:" then list, then another
"Preferred:" then list. That's okay.
Benefits: list.
Let's extract details.
Location: "Location: Philadelphia, PA / Northern New Jersey / New York, NY (Remote, US)" We'll put as
Location: Philadelphia, PA / Northern New Jersey / New York, NY (Remote, US)
About Xpoint paragraph: copy the paragraph.
Job Summary paragraph: copy.
How We Work - Remote and Distributed: we need to incorporate that content. It includes: "You will work remotely in the U.S. Most of the backend team you lead sits roughly 8 hours ahead of U.S. Eastern, with the rest of Engineering, QA, and Product spread across several countries. Because there are only a couple of hours of live overlap on a typical day, strong written communication and the ability to work effectively in a distributed environment are essential. This means: Written communication is key. You’ll create clear specifications, tickets, review comments, and decisions that allow work to move forward across time zones. You’ll anticipate questions and potential blockers so the team can continue making progress outside of U.S. working hours. Live overlap will be focused on conversations that benefit most from real-time collaboration, including technical discussions, escalations, and mentoring. You’ll travel internationally a few times each year for team planning, onboarding, and team building. You’ll also travel regularly to Philadelphia for in-person working sessions with U.S.-based leadership, Product, and Commercial teams."
We'll put as a paragraph.
AI-Forward By Default: paragraph.
Operating Principles: paragraph.
Our Stack: paragraph.
Now Responsibilities list:
- Own the technical direction, architecture, quality, and delivery of Xpoint’s core backend platform, including documenting key architectural decisions and rationale.
- Lead and mentor a distributed team of backend engineers through hands-on development, code review, and technical guidance.
- Design, develop, test, and maintain high-performance, scalable, and secure Java services using strong engineering and design practices.
- Establish and uphold standards for code quality, testing, documentation, observability, and maintainability.
- Own backend services in production, including performance optimization, on-call participation, incident response, and root-cause resolution.
- Partner with Product, QA, SRE, Compliance, and other stakeholders to define requirements, manage customer and rollout impacts, 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 while establishing appropriate standards and guardrails for their use.
- Stay current with relevant Java, cloud, and AI technologies and identify opportunities to improve Xpoint’s engineering practices.
Now Requirements:
Required:
- Senior-level backend engineering experience with ownership of architecture and production systems
- Deep Java and Spring/Spring Boot expertise, including REST APIs and microservices
- 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 and request/response signing
- 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 demonstrated technical leadership through mentoring, code review and cross-functional collaboration
Preferred:
- Experience with real-time stream processing, fraud detection, anti-abuse, device integrity or trust & safety systems
- Familiarity with geospatial technologies
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate (cookie/navigation/legal/EEO etc). There's none. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated, so we include Benefits section. Pay not mentioned, so omit. Schedule not mentioned, omit. We need to decide which headings to use: About the role (maybe corresponds to About Xpoint + Job Summary?), Responsibilities (Job Responsibilities), Requirements (Job Requirements), Qualifications (maybe not separate; could combine with Requirements?), Skills (maybe not separate), Benefits (Benefits Package). We could also include "How We Work" as part of About the role or Responsibilities? But instruction: Use headings for those specific names; we can include only those that have content. We could include About the role (covering About Xpoint and Job Summary). Responsibilities (Job Responsibilities). Requirements (Job Requirements). Benefits (Benefits Package). Possibly also Skills? Not explicit separate list; we could omit. We must not emit heading followed by filler/placeholder text. Ensure each heading has substantive content. We need to format content: For prose, use
. For lists, use
- .
We need to preserve all substantive information: That includes details about location, remote, travel, etc. Should we include location info? It's at top: "Location: Philadelphia, PA / Northern New Jersey / New York, NY (Remote, US)". That's location metadata; we could fold into a short
under About the role maybe. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So location is minor metadata; we can include a short
maybe. We need to include all substantive info: The description of Xpoint, job summary, how we work, AI-forward, operating principles, responsibilities, requirements, benefits package, our stack (maybe include under Responsibilities or Requirements? It's technical stack; could be part of Responsibilities or Requirements. Since we have no specific heading for Stack, we could include it as a
under Responsibilities or Requirements. Probably under Responsibilities as part of describing work. We must not invent or summarize away detail: So we need to keep details like "Java and Spring Boot on AWS, across multiple regions and tenants. Kubernetes and Docker, with horizontal and node autoscaling. DynamoDB, Kinesis, Firehose, Kafka and SQS. Apache Flink for real-time rules. Athena, Glue, OpenSearch and Airflow on the data side. OpenTelemetry, Prometheus and Grafana for observability, with Sentry and PagerDuty. GitLab for source control and CI/CD." Keep that. We need to ensure we don't repeat content. Let's structure:
Location: Philadelphia, PA / Northern New Jersey / New York, NY (Remote, US)
About the role
About Xpoint: Xpoint builds the geolocation compliance layer for regulated online sports betting and gaming. Before an operator can accept a wager, they must prove the player is physically where the law says they must be, and prove it to a regulator, on demand. That is the problem we solve, in real time, at scale, for some of the largest betting operators in the US and internationally. It is a genuinely hard engineering problem, and an unusually interesting one: Every request is a decision, not a lookup. We fuse GPS, Wi-Fi, network, and device-integrity signals into a single allow/deny call under a hard latency budget, at volumes that spike significantly around live sports. The problem is adversarial. People actively try to defeat us through spoofed locations, VPNs and proxies, remote desktops, virtualized devices, and tampered attestation. The work sits at the intersection of distributed systems, fraud detection, and security engineering. Every decision must be explainable. Our releases are filed with state gaming regulators before they can reach production. That raises the bar for correctness, traceability, and testing in a way that most consumer engineering never has to meet. We’re small enough that your decisions have a real impact. Xpoint is gaining market share by building better technology. You’ll be one of a handful of people helping set the direction of our backend platform, with direct access to the executives making decisions about what we build.
Job Summary: Xpoint is seeking a Lead Backend Software Engineer to own the architecture, quality, and delivery of our core backend platform. This includes the Java services that process location checks, run decision and fraud rules, and return results in milliseconds. This is a hands-on engineering role, with most of your time spent writing, reviewing, and debugging production code. As the Lead, you’ll help set the technical direction, maintain high standards through code review, and mentor backend engineers by working alongside them rather than managing them. You’ll also serve as the senior backend engineer in the U.S. time zone, partnering directly with Product, QA, SRE, and Compliance to move work from planning through production.
How We Work - Remote and Distributed
maybe not a standard heading; but we could incorporate into About the role? However instruction says use headings for those specific names; but we could still include a heading not in list? It says "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive? It says use
for section headings (e.g. ...). Likely they expect only those headings. Safer to stick to those. So we should not create a heading like "How We Work - Remote and Distributed". Instead we can fold that content under About the role or Responsibilities. Probably under About the role as part of role description. Similarly "AI-Forward By Default" and "Operating Principles" could be folded under About the role or Responsibilities. But we need to preserve all substantive info; we can include them as paragraphs under About the role. Thus About the role will be lengthy but okay. Then Responsibilities: list of responsibilities. Then Requirements: list of required and preferred. Then Benefits: list of benefits. We need to ensure we don't create Pay or Schedule sections. Now craft HTML. We'll start with location paragraph. Then About the role: include paragraphs for About Xpoint, Job Summary, How We Work, AI-Forward, Operating Principles, Our Stack maybe. We need to use
- for any list of duties/requirements/benefits. For prose, use
. Thus for About the role we can have multiple
elements. Now Responsibilities: we have a list of bullet points from Job Responsibilities. We'll convert each to
- .
Requirements: we have Required and Preferred. We'll maybe separate into two
- or combine with headings inside? But we cannot add extra headings besides the main ones. Could include a
stating "Required:" then list, then another
"Preferred:" then list. That's okay. Benefits: list. Let's extract details. Location: "Location: Philadelphia, PA / Northern New Jersey / New York, NY (Remote, US)" We'll put as
Location: Philadelphia, PA / Northern New Jersey / New York, NY (Remote, US)
About Xpoint paragraph: copy the paragraph. Job Summary paragraph: copy. How We Work - Remote and Distributed: we need to incorporate that content. It includes: "You will work remotely in the U.S. Most of the backend team you lead sits roughly 8 hours ahead of U.S. Eastern, with the rest of Engineering, QA, and Product spread across several countries. Because there are only a couple of hours of live overlap on a typical day, strong written communication and the ability to work effectively in a distributed environment are essential. This means: Written communication is key. You’ll create clear specifications, tickets, review comments, and decisions that allow work to move forward across time zones. You’ll anticipate questions and potential blockers so the team can continue making progress outside of U.S. working hours. Live overlap will be focused on conversations that benefit most from real-time collaboration, including technical discussions, escalations, and mentoring. You’ll travel internationally a few times each year for team planning, onboarding, and team building. You’ll also travel regularly to Philadelphia for in-person working sessions with U.S.-based leadership, Product, and Commercial teams." We'll put as a paragraph. AI-Forward By Default: paragraph. Operating Principles: paragraph. Our Stack: paragraph. Now Responsibilities list: - Own the technical direction, architecture, quality, and delivery of Xpoint’s core backend platform, including documenting key architectural decisions and rationale. - Lead and mentor a distributed team of backend engineers through hands-on development, code review, and technical guidance. - Design, develop, test, and maintain high-performance, scalable, and secure Java services using strong engineering and design practices. - Establish and uphold standards for code quality, testing, documentation, observability, and maintainability. - Own backend services in production, including performance optimization, on-call participation, incident response, and root-cause resolution. - Partner with Product, QA, SRE, Compliance, and other stakeholders to define requirements, manage customer and rollout impacts, 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 while establishing appropriate standards and guardrails for their use. - Stay current with relevant Java, cloud, and AI technologies and identify opportunities to improve Xpoint’s engineering practices. Now Requirements: Required: - Senior-level backend engineering experience with ownership of architecture and production systems - Deep Java and Spring/Spring Boot expertise, including REST APIs and microservices - 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 and request/response signing - 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 demonstrated technical leadership through mentoring, code review and cross-functional collaboration Preferred: - Experience with real-time stream processing, fraud detection, anti-abuse, device integrity or trust & safety systems - Familiarity with geospatial technologies
- for any list of duties/requirements/benefits. For prose, use