🎁 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 →
Navii is an AI recruiter, running this search on behalf of Gallop Intelligence. HERE'S HOW IT WORKS Rather than your resume sitting in a queue, you have a conversation with Navii about your experience and what you want next. What you say reaches Gallop Intelligence's hiring team in your own words. It is a required step, takes about 25 minutes, and there is nothing to schedule. NEXT STEP A conversation with Navii about this role: https://app.heynavii.ai/careers/founding-engineer-enterprise-secure-ai-platform-8d453c8a ABOUT GALLOP INTELLIGENCE Gallop Intelligence is an SF Bay Area AI startup and one of the early leaders in enterprise legacy code modernization. We work with Fortune 500 customers across several industries who choose Gallop products to replace their legacy internal IT systems, because it is faster, cheaper and more modern than anything else on the market. Our co-founders spent many years as senior leaders at Google and Lovable, where they developed the approach. With production deployments and strong customer demand, we are on an accelerated growth trajectory. You’ll help build the secure enterprise foundation for an AI platform—where reliability, trust, and real-world integration matter as much as model performance. If you like turning ambiguous requirements into working systems, this is a rare chance to shape the technical direction from day one. Also a fit if you call yourself: Security-minded AI Engineer, Platform Engineer, Applied AI Engineer The Work • Own the secure platform foundation for enterprise AI: design and implement the core services that make secure deployments possible (auth, data handling, access controls, and operational safety). • Drive end-to-end integration ownership across the stack—turning requirements into working flows that connect product needs to engineering reality (APIs, services, infrastructure, and deployment). • Build reliability into the system, not around it: add verification, monitoring, and pragmatic safeguards so issues are caught early and failures are diagnosable. • Handle ambiguity with evidence: when requirements are fuzzy, you propose a path, validate it quickly, and iterate based on what you learn. • Collaborate to translate enterprise expectations into engineering decisions: keep security and enterprise constraints clear as requirements evolve, and align on practical next steps. Who you are (fit) • You’ve shipped production systems end-to-end (not just components) and can explain the tradeoffs you made to get to a reliable release. • You have strong security engineering instincts—you know how to think about access control, data boundaries, and safe-by-default design. • You can turn unclear requirements into concrete plans and deliver the first working version without waiting for perfect clarity. • You’ve built verification/observability into your work (tests, instrumentation, runbooks, or other practical mechanisms that reduce “mystery failures”). • You’re comfortable working through shifting priorities while keeping quality high. Success in this role • You deliver enterprise-secure, customer-facing integrations end-to-end, with clear operational behavior (so teams can trust what’s happening). • You establish customer-relevant reliability and diagnosability for the areas you own—verification and observability that make issues actionable. • You consistently apply a security-first mindset (least privilege, safe failure modes, and clear data boundaries) while moving from requirements to production. What you’ll need • Production engineering experience: you’ve shipped and operated real systems, and you can talk through the reliability and security tradeoffs you made. • Security-first platform thinking: you understand access control, data boundaries, and safe-by-default design patterns. • Execution under ambiguity: you can propose a path, validate quickly, and iterate based on evidence. • Pragmatic verification/observability: you add the checks and instrumentation that make outcomes visible. • Strong collaboration habits: you align quickly, document decisions when needed, and follow through. • Experience building with Python/TypeScript/React. • Ability to work Sunnyvale in-office. Even Better If • You’ve worked on enterprise integrations (SSO/SAML, RBAC, audit logging, compliance-adjacent workflows, or similar). • You’ve built systems where security requirements were non-negotiable and you had to earn trust through measurable reliability. Constraints / Requirements • You’ll be expected to operate with a security mindset: assume data is sensitive, default to least privilege, and design for safe failure modes. • You’ll need to move fast without sacrificing quality—priorities may shift, but you’re responsible for keeping reliability and security intact. • You should be comfortable owning work end-to-end, including integration details and operational readiness. Who Thrives Here • You ask crisp clarifying questions, then move—preferring concrete next steps over open-ended debate. • You communicate in a friendly, direct, facilitative way: you surface what’s known, what’s uncertain, and what you’ll do next to close the gap. • You take ownership of reliability—not by promising, but by adding the checks and instrumentation that make outcomes visible. • You enjoy shaping the work as you go: you help define the role’s boundaries and then deliver inside them. The Team You’ll work closely with the team that’s building the enterprise secure AI platform—people who care about getting the details right and keeping momentum. The collaboration style is practical and iterative: quick alignment, clear next steps, and steady follow-through. You’ll have room to influence how the platform is built, and you’ll be expected to bring evidence when requirements are unclear. Comp and Benefits Compensation is competitive and based on experience. The hiring team will share specifics directly. Benefits include: • Health insurance • Dental insurance • Vision insurance • Paid time off • Parental leave • Professional development support Non-Traditional Backgrounds If you’ve built and shipped secure, reliable systems in any environment—startup or enterprise—we’d still love to hear from you. The key is evidence of end-to-end ownership and reliability, not a specific background label. How to Apply Interested? You’ll start with a conversation with Navii, the hiring team’s AI—it's a chance for us to learn about you beyond your resume.
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.