Senior / Staff Backend Engineer, Maps
Radar · United States · 3 wk ago
RemoteRemoteEngineering$200k–$300k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Let's extract sections:
- About Radar (company description) maybe not needed as a heading? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include headings only for those categories if content exists. "About Radar" is not in list, but could be considered "About the role"? Actually "About The Role" is a heading in the posting. So we should have
for section headings (e.g. About the role, Responsibilities...). It implies we should use those headings only. Probably we should only output those headings if they have content. So we should not output "About Radar" as a heading. However we could incorporate that info into a paragraph under About the role? Might be okay but risk missing info. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine company description into About the role section.
Thus About the role section will contain: description of Radar (company), the role description, location, etc.
Let's gather:
About Radar: "Radar is the global leader in geolocation, with geofencing SDKs, maps APIs, and AI-enabled solutions for marketing, fraud, and operations teams. We're trusted by some of the world's best companies, from high-growth startups to the Fortune 500. We have incredible scale: We're processing over 1 billion API calls per day from hundreds of millions of devices. We're well-resourced, and we've raised $85.5M from world-class investors, including Accel and Insight Partners. We have a high-performance culture, with ambitious and entrepreneurial teammates in every role. We recently moved into an amazing new office in Flatiron, Manhattan, NYC. We were recently named a top 10 best place to work in NYC by Crain's. Despite our growth and scale, we're still just getting started."
About The Role: "We're looking for a Maps Product Engineer to strengthen the data foundation behind Radar's geocoding platform. Our daily traffic is over 1 Billion API calls / day (15,000 requests / second) so you will be operating at scale. You'll own the systems that bring many sources of location data together into something reliable, accurate, and fresh, with the opportunity to bring AI into how we enrich and scale it. It's a broad role with deep ownership of the data layer, reaching across the geocoding stack from ingestion to serving. This role will be in our NYC HQ."
How We Work: details about engineering culture, etc. Could be part of responsibilities or qualifications? Might be extra but we can include under About the role or maybe under Responsibilities? Might be considered part of "How We Work" which is not a standard heading; we could incorporate into About the role or maybe under Responsibilities? But we need to preserve all substantive info. Could add a paragraph under About the role describing work culture.
The Stack: details about technologies. Could be under Skills.
How We Use AI: could be under Skills or Responsibilities.
The Hiring Process: not needed for job description? Might be considered metadata; we could drop as minor metadata? It's not in headings list; we could drop or fold into a short p. Probably drop.
What You’ll Do: list of responsibilities.
You Should Think of yourself as a generalist engineer first...: qualifications.
Bonus Points If You: preferred qualifications.
You’ll Work With: list of teammates.
What We Offer: benefits.
Compensation Range: pay.
Thus we need to map:
- About the role: combine company description + role overview + location + maybe how we work? We'll include company description, role overview, location, and maybe how we work (culture) as part of this section.
- Responsibilities: from "What You’ll Do" bullet list.
- Requirements: maybe "You Should Think of yourself as a generalist engineer first..." plus maybe "You’ll Work With"? Actually "You’ll Work With" is about teammates, not requirement. Could be part of responsibilities? Might be better as "Requirements" (who you'll work with). But we can treat as part of responsibilities? Hmm.
- Qualifications: maybe "Bonus Points If You" as preferred qualifications.
- Skills: maybe list of technologies from The Stack and How We Use AI.
- Benefits: from What We Offer.
- Pay: from Compensation Range.
- Schedule: none -> omit.
We must not create sections with filler. So we will only output sections that have substantive content.
Let's extract each.
**About the role** content:
Paragraphs:
- Radar is the global leader in geolocation, with geofencing SDKs, maps APIs, and AI-enabled solutions for marketing, fraud, and operations teams. We're trusted by some of the world's best companies, from high-growth startups to the Fortune 500. We have incredible scale: We're processing over 1 billion API calls per day from hundreds of millions of devices. We're well-resourced, and we've raised $85.5M from world-class investors, including Accel and Insight Partners. We have a high-performance culture, with ambitious and entrepreneurial teammates in every role. We recently moved into an amazing new office in Flatiron, Manhattan, NYC. We were recently named a top 10 best place to work in NYC by Crain's. Despite our growth and scale, we're still just getting started.
- We're looking for a Maps Product Engineer to strengthen the data foundation behind Radar's geocoding platform. Our daily traffic is over 1 Billion API calls / day (15,000 requests / second) so you will be operating at scale. You'll own the systems that bring many sources of location data together into something reliable, accurate, and fresh, with the opportunity to bring AI into how we enrich and scale it. It's a broad role with deep ownership of the data layer, reaching across the geocoding stack from ingestion to serving. This role will be in our NYC HQ.
- How We Work: Most of our engineering team are former technical co-founders or former Radar interns from schools like Waterloo and CMU. Most engineers at Radar fit one of two molds, technically: either Staff level expertise in one stack, or "Multi-Stack" at any level. We say "Multi-Stack" because "Full-Stack" has the connotation of "Frontend and Backend", but Radar Engineers might also work on Mobile or Data engineering. Not that you need to be an expert in all of those, but a desire to learn, jump around to different stacks, and get things done is the important part. We care a lot about shipping fast and talking to customers. We're committed to our product vision of full-stack location infrastructure, but we also know that customer feedback is a treasure map to gold. Even though Slack is the brain of our company, working together in-person in our NYC HQ is the fastest way for us to get things done. We meet on Mondays to plan out work for the week in small groups and use Linear for planning. To us, a week is a long time, and we expect to ship big things every week.
We could include that as part of About the role.
**Responsibilities** from "What You’ll Do":
- Own the data foundation under the geocoder including how location data is modeled, kept consistent, and served reliably, working across Scala, Python, and Rust
- Build the pipelines that bring many commercial and open data sources together, expanding coverage and quality across US and international data
- Help bring LLMs and agents into the data layer for enrichment, labeling, and quality, with the guardrails to keep them trustworthy
- Range across the geocoding stack when the work calls for it, from the serving path in HorizonDB to the Node.js/TypeScript API
- Have your work power over 1 Billion API calls / day
- Talk to Radar customers and prospects, hear their feedback, incorporate it into your work and make them successful
**Requirements** from "You Should Think of yourself as a generalist engineer first...":
- Think of yourself as a generalist engineer first, not tied to any particular stack
- Are interested in talking to customers or prospects and making them successful
- Are deeply curious about how things work, and have the tenacity to sit with hard problems and power through them
Maybe also include "Most engineers at Radar fit one of two molds..." but that's more about culture; could be part of About the role.
**Qualifications** maybe not needed separate; but we could treat "Bonus Points If You" as preferred qualifications.
**Skills**: Could list technologies: HorizonDB (Rust), Tantivy, RocksDB, FSTs, ML models, Scala, Python, Airflow, Node.js, TypeScript, MongoDB, S3/Athena, Redis, AWS, Kubernetes, EKS, Terraform, OpenStreetMaps, MapLibre, OpenAddresses, Claude, Codex, LLMs.
But we need to avoid thin sections; maybe we can combine Skills into Responsibilities or Requirements? However the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include headings only for those categories if content exists. "About Radar" is not in list, but could be considered "About the role"? Actually "About The Role" is a heading in the posting. So we should have About the role
with content from that section.
We also have "How We Work", "The Stack", "How We Use AI", "The Hiring Process", "What You’ll Do", "You Should Think of yourself as...", "Bonus Points If You", "You’ll Work With", "What We Offer". These could map to Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which content goes where.
Responsibilities: likely "What You’ll Do" bullet list.
Requirements: maybe "You Should Think of yourself as a generalist engineer first..." plus maybe "Bonus Points If You" as preferred qualifications.
Qualifications: maybe required qualifications? Not explicit. Could treat "You Should Think..." as qualifications. Bonus points as preferred qualifications.
Skills: maybe list of technologies? Could be from "The Stack" etc. But we need to avoid thin sections. Might combine.
Benefits: from "What We Offer" bullet list.
Pay: from "Compensation Range: $200K - $300K". Also maybe "Competitive salary" etc. So we have pay.
Schedule: maybe not mentioned. No schedule info. So we should not include Schedule section.
We also need to include "About the role" section with description from "About The Role" paragraph.
We must not include boilerplate like EEO etc. Remove that.
We must preserve all substantive info: need to include details like scale, traffic, location (NYC HQ), etc.
Let's extract substantive content:
About Radar: maybe not needed as heading but could be included as part of About the role? 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." It doesn't forbid other headings not in list, but says use