Senior​/Platform Engineer

Radar Platform Engineer

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

We're looking for Platform Engineers to help us build and operate Radar's infrastructure, developer platform, and data systems in order to make Radar the most reliable and trusted location platform in the world. Our daily traffic is 1 Billion API calls / day (15,000 requests / second), so you will be operating at scale in helping our engineers deliver features quickly and at high quality.

This role can either be in our NYC HQ or remote in the US.

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.

The stack:

• The API layer is a Node.js + Type Script app.
• We ship SDKs for iOS, Android, React Native, and more.
• Our main backend service is a geospatial database written in Rust that we call HorizonDB.
• We use MongoDB, S3/Athena, Redis, and Airflow.
• 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.

How we use AI:

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

The hiring process:

After a call with our Technical Recruiter, you'll do several technical Zoom calls with members of our engineering team: code screen, coding round, and system design round. If those go well we'll invite you to our NYC HQ for a final round interview. You'll meet one of our co-founders, someone from outside engineering, and meet more people from Radar. We'll go into more depth about how we work to see if there is a match.

What you'll do:

• Work on core Radar products using Type Script, Rust, Python and Scala
• Build highly available systems with 99.99%+ monthly uptime
• Work with SRE and data teams to enable self-serve capabilities, including build/test/deploy infrastructure, observability improvements, data pipeline investments, and automation.
• Build and support core product capabilities like IAM, feature flagging, application rate limiting, and more.
• Own internal development platform, including supporting our server, frontend, mobile, and desktop frameworks, and integrating safe AI-enabled development practices throughout our SDLC.
• With QA, enable test automation and coverage for developers throughout our application, data, and infrastructure stack.
• Help integrate security and compliance practices into every stage of the development lifecycle, from design to deployment.
• Have your work power 1 Billion API calls / day
• Talk to Radar customers and prospects, hear their feedback, incorporate it into your work and make them successful

You should:

• Think of yourself as a generalist engineer first, not tied to any particular stack
• Are…