Staff Engineer, Backend Developer

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.

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

• Proven experience designing, building, and owning production-grade REST APIs  have been the engineer responsible for the full lifecycle. You have defined API contracts that other teams depend on, handled breaking change management, and built services that handle real production load. You have owned APIs, the decisions behind it, and everything that happened to it in production.
• Hands-on production experience with cloud infrastructure across AWS, GCP, or Azure. On AWS this looks like ECS, RDS, Lambda, S3, SQS, and IAM. On GCP or Azure, equivalent managed compute, storage, messaging, and identity services. Experience should be with enterprise-grade cloud platforms, not developer-tier or hobbyist hosting solutions.
• Demonstrated ability to make and own architectural decisions on production backend systems, including trade-off analysis and long-term maintainability. You have been the person in the room who decides how something gets built, not just the person who implements the decision. You can articulate why you made a choice, what you gave up to make it, and what you would change if you were doing it again.
  
  You think about what a system looks like two years from now, not just whether it works today.
• Proficient with recent, continuous production experience using Python as a primary language- not occasional scripting or secondary usage. Python has been your primary production language for at least five years and it is what you reach for first. You have built and maintained production backend services in Python, not just written automation scripts or contributed Python to a codebase that is primarily something else.
  
  FastAPI in production is required.
• Proficient in working with SQL databases in production environments. You write queries that perform well under real load, design schemas that hold up as requirements change, and understand how indexes, query plans, and connection pooling actually work in production. PostgreSQL is the primary database here and you should be comfortable with migrations, row-level security, and debugging slow queries when something goes wrong at 2am.

• Familiarity with CI/CD pipelines and tools including Git Hub Actions, Jenkins, or equivalent. You have worked within them, understood how they affect your team's ability to ship safely, and had a voice in how they are configured or improved.
• Demonstrated…