Senior ​/ Staff Backend Engineer, Maps

About Radar

Radar is the global leader in geolocation, with geofencing SDKs, maps APIs, and AI-enabled solutions for marketing, fraud, and operations teams.

Why is Radar the best place to work?

• 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. That's where you come in.

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 '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.

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.

Our core backend service is HorizonDB, a geospatial database written in Rust that powers geocoding (see our blog posts here and here for a look at the internals)

We use Tantivy, RocksDB, and FSTs for indexing, with ML models for query understanding and ranking.

Our geospatial data pipelines are written in Scala and Python on Airflow, bringing many commercial and open data sources together.

The API layer is a Node.js Type Script app, and we use MongoDB, S3/Athena, and Redis.

Everything is deployed to AWS via Kubernetes on EKS using Terraform.

Most engineers are in the on‑call rotation.

We sponsor Open Street Maps , Map Libre, and Open Addresses.

• Engineers choose what AI tools they use, Claude and Codex being the most popular.
• We're actively building Claude skills - for example we've taught it how to debug HorizonDB, our geospatial database.
• All code changes are reviewed by an Engineer knowledgeable in that area. Claude and Codex also review all PRs.
• There is a range of how much engineers use AI. Most use it daily if not weekly.
• We are excited about what AI can do, but we also recognize the risks and don't compromise our coding standards.

After a call with our Technical Recruiter, you'll do several technical Zoom calls…