🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
This is the product side of Abnormal AI's email security platform. When a security operations team finds a malicious message in a customer's environment, the search, quarantine and remediation workflows that clean it up across a multi tenant enterprise mailbox estate are what this team builds. The work is backend service design plus the REST APIs that SOC teams call directly, with unit and integration testing and production observability treated as part of the job rather than an afterthought. The stack is listed as a nice to have rather than a gate: Python, Go, AWS, Kubernetes and Django. At three years with real backend and distributed systems experience, this is a reasonable step into security tooling without needing a security background first. Who it is for: MUST HAVES, AS PUBLISHED - A BS in computer science, applied sciences, information systems or a related engineering field. - 3+ years of industry experience in backend development and distributed systems. - Experience building features and components from scratch and operating them in production, balancing feature work against operational reliability. - Experience working with distributed teams, and proficiency in asynchronous and written communication. - Experience improving service reliability, resiliency and observability in production. - Strong fundamentals in computer science, data structures and system design. NICE TO HAVE - The team's stack: Python, Go, AWS, Kubernetes, Django. - Search systems, remediation workflows or operational tooling used by SOC teams. - SIEM or SOAR integrations, or platform APIs. - Exposure to email security and authentication standards such as DMARC and DKIM. WHAT THE JOB ACTUALLY IS DAY TO DAY Designing and building backend services behind search, remediation and quarantine across multi tenant enterprise email environments. Scoping and delivering features end to end with the tech lead, engineering manager and product manager. Owning reliability of what you build, including unit tests, integration testing and production observability. Contributing to API design for customer facing REST endpoints used by security operations teams. Participating in on call and providing technical support to resolve customer issues. Mentoring junior engineers through code review. LOCATION AND WORKING PATTERN Hybrid in Bangalore, with an async first culture and on call rotation. HIRING PROCESS NOTE, DISCLOSED BY THE EMPLOYER Abnormal states that AI assisted tools help recruiters prepare interview questions, that they do not screen candidates automatically, and that a person makes every decision. HONEST FIT GUIDANCE The degree requirement is stated as a must have here, which is worth knowing if you came through a non traditional route. Everything about the specific domain, email security and SOC tooling, sits in the nice to have list, so general backend depth is what is really being tested. .
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.