Senior Software Engineer, Compute

Other Jobs To Apply

No other job posts for this day.

<p style="min-height:1.5em"><strong>About Persona</strong></p><p style="min-height:1.5em"><a target="_blank" rel="noopener noreferrer nofollow" href="https://withpersona.com/"><u>Persona</u></a> is the configurable identity platform built for businesses in a digital-first world. Verifying individuals and organizations is harder — but more important — than ever, with AI enabling fraudsters to launch sophisticated accounts at scale and regulations evolving rapidly.</p><p style="min-height:1.5em">We’ve built Persona to support practically every use case and industry — that’s why we’re able to serve a wide range of leading companies. For example, Reddit relies on Persona for age assurance and verification to comply with online safety regulations, protecting younger users while maintaining a seamless experience. Meanwhile, OpenAI relies on Persona to keep bad actors out, protecting one of the world’s most powerful AI platforms from large-scale abuse in a time when AI is reshaping the way we work and live.</p><p style="min-height:1.5em">We’re growing rapidly and looking for exceptional people to join us!</p><p style="min-height:1.5em"></p><h2>About the role</h2><p style="min-height:1.5em">The Compute team's mission: any engineer, using AI, should be able to stand up and operate a stateful service at production scale with no meaningful infrastructure knowledge required. We build the tiering zones, guardrails, and AI skills that make this possible. Reliable, observable, and self-service by design.</p><p style="min-height:1.5em">This is a software engineering role. You'll spend real time writing code: platform APIs, internal tooling, deployment pipelines, automation that replaces the support tickets. Infrastructure fluency matters; infrastructure specialization is not the lead. What matters most is product instinct: understanding your users (product engineers), measuring whether they're getting unblocked, and treating developer experience as a feature acceptance criterion.</p><p style="min-height:1.5em">The platform is yours to own, not just build. When ArgoCD fails and every team's deploy is blocked, that's your page. When a product engineer can't figure out why their service is OOMKilling and there's no useful error surface, that's your design failure to fix.</p><p style="min-height:1.5em">A Senior engineer will help define the platform's interfaces and own how product teams interact with compute infrastructure. The team is still establishing its patterns, and you'll have real influence over what they become.</p><p style="min-height:1.5em"></p><h2>What you'll do at Persona</h2><ul style="min-height:1.5em"><li><p style="min-height:1.5em">Build internal platform tooling and APIs that product engineers use to deploy, scale, and observe services, with developer experience as a first-class requirement</p></li><li><p style="min-height:1.5em">Own and evolve the Kubernetes platform, ArgoCD deployment pipeline, and Terraform IaC that underpin every service at Persona</p></li><li><p style="min-height:1.5em">Improve platform observability so "why is my service slow" and "why did my deploy fail" have self-service answers. Instrumentation is a platform primitive, not a per-service afterthought.</p></li><li><p style="min-height:1.5em">Drive Cloud Run-to-Kubernetes migration, working directly with product teams to remove blockers and hand off operational ownership cleanly</p></li><li><p style="min-height:1.5em">Design self-service workflows to reduce the Compute interrupt load. Success means product engineers can do more without filing a ticket.</p></li><li><p style="min-height:1.5em">Define the interfaces and abstractions the platform exposes to product teams. What does "easy to use correctly" look like for a deployment workflow or platform API?</p></li></ul><p style="min-height:1.5em"></p><h2>What you'll bring to Persona</h2><ul style="min-height:1.5em"><li><p style="min-height:1.5em">Strong SWE fundamentals: shipped production services, writes readable and operable code, can debug distributed system failures across layers you don't fully own</p></li><li><p style="min-height:1.5em">Product instinct: you measure adoption, treat low usage as a design failure, and change things based on user feedback rather than your own assumptions</p></li><li><p style="min-height:1.5em">Developer experience sensibility: you identify friction in CLIs, APIs, and deployment workflows and design for clear affordances, actionable error states, and progressive disclosure</p></li><li><p style="min-height:1.5em">Kubernetes in practice: you've operated services on K8s, can debug scheduling failures, write RBAC policies, and work out why a pod won't start. You're willing to be paged for the platform you build.</p></li><li><p style="min-height:1.5em">Infrastructure as code in a team context: you've modified production IaC alongside other engineers and understand why declarative infrastructure and change safety matter</p></li><li><p style="min-height:1.5em">Senior candidates: we look for production-level Terraform ownership, including state, module composition, and clean infrastructure refactors.</p></li></ul><p style="min-height:1.5em"></p><h2>Nice to haves</h2><ul style="min-height:1.5em"><li><p style="min-height:1.5em">Deep K8s internals: cluster lifecycle, admission controllers, custom controllers/operators</p></li><li><p style="min-height:1.5em">ArgoCD or another GitOps tool in production</p></li><li><p style="min-height:1.5em">GKE or managed Kubernetes at scale</p></li><li><p style="min-height:1.5em">Ruby or Rails (we integrate with Ruby systems)</p></li><li><p style="min-height:1.5em">Experience in a regulated or high-trust environment</p></li></ul><p style="min-height:1.5em"></p><p style="min-height:1.5em"><strong>Full-time Employee Benefits and Perks</strong></p><p style="min-height:1.5em">For full-time employees (excluding internship and contractor opportunities), Persona offers a wide range of benefits, including medical, dental, and vision, 3% 401(k) contribution, unlimited PTO, quarterly mental health days, family planning benefits, professional development stipend, wellness benefits, among others. While we believe competitive compensation and benefits are a critical aspect of you deciding to join us, we do hope you consider why our core values and culture are right for you. If you’d like to better understand what it’s like working at Persona, feel free to check out our reviews on <a target="_blank" rel="noopener noreferrer nofollow" href="https://www.glassdoor.com/Overview/Working-at-Persona-Identities-EI_IE4135645.11,29.htm"><u>Glassdoor</u></a>.</p>

Back to blog

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...