Staff Engineer

About the role

At 360 Privacy, we build proactive digital security tools to protect high‑risk individuals, from senior executives to public figures and their families. Our platform removes personal data exposure across the open web, deep web, and dark web through a combination of human expertise and large‑scale automation. Trusted by 40 of the Fortune 100, we're scaling rapidly and investing heavily in our core engineering platform: the backend systems, APIs, and AI‑integrated infrastructure that power discovery, monitoring, and removal workflows at scale. We're hiring a Staff Backend Engineer on our Core team to design, build, and own the backend systems and APIs that power our platform. This is a senior individual contributor role with a Principal trajectory, meaning real architectural ownership, not implementation of someone else's decisions. The right candidate thinks in systems and consequences. You've owned backend platforms where the data was genuinely sensitive, you've made architectural decisions you had to live with, and you're comfortable saying "we should not do this" when necessary. You write Python continuously and recently, you know AWS deeply, and you have strong opinions about reliability earned through experience.

Responsibilities

• Design, build, and own production‑grade REST APIs and backend services.
• Architect and maintain scalable, secure backend systems with clear ownership of trade‑off decisions and long‑term maintainability.
• Ensure high performance and responsiveness of applications across the platform.
• Collaborate with front‑end developers and cross‑functional teams to integrate user‑facing elements with server‑side logic.
• Mentor engineers and contribute to engineering standards, documentation, and architectural direction in a collaborative, low‑ego environment.
• Troubleshoot and resolve production issues as they arise.
• Partner with Product, Security, and Data teams to translate ambiguous requirements into durable backend platforms.
• Make principled decisions about when architectural approaches are inappropriate, particularly in security‑ or compliance‑sensitive areas.

Requirements

• Proven experience designing, building, and owning production‑grade REST APIs at scale; full lifecycle ownership, defining API contracts, handling breaking changes, and services handling real production load.
• Hands‑on production experience with cloud infrastructure across AWS, GCP, or Azure (e.g., ECS, RDS, Lambda, S3, SQS, IAM on AWS; equivalent managed services on GCP/Azure). Experience must be with enterprise‑grade platforms, not developer‑tier or hobbyist hosting.
• Demonstrated ability to make and own architectural decisions on production backend systems, including trade‑off analysis and long‑term maintainability; able to articulate choices, compromises, and future‑state thinking.
• Proficient