
Bengaluru
94 Candidates
About the role
We're hiring a Lead Security Engineer to own security for a defined area of our platform: the AWS infrastructure, applications and data behind a consumer fintech product that handles sensitive financial and personal data.
It's a hands-on role with a team attached. You'll do the work yourself, and you'll also hire, lead and grow a small team of security engineers. As Oolka grows, we expect to have several security leads like you, each owning a charter and working with our security leadership.
Two things make this role different. First, it covers the full stack: cloud, application and data, not just one of them. Second, we're shipping AI features into a product that touches real financial data. You'll be designing how those features stay secure while also running the foundations underneath them.
You'll work closely with engineering so security is part of how we build, not something added at the end. On a normal week you might be in the AWS console and Terraform, reviewing code, sitting in an AI feature design review, and occasionally writing a policy or answering an auditor.
What you'll do
Own your charter and build your team. You'll be accountable for security across your area: infrastructure, applications, risk prioritisation and audit responses. You'll agree the roadmap with engineering leadership, then hire and develop the engineers who help you deliver it. You'll set the hiring bar, decide how the team works, and make sure it can handle more as the business grows.
AI and LLM security. We put LLM-backed features in front of customer financial data, and the usual playbooks don't fully cover it. You'll look after:
Agent permissions: what tools and APIs the agent can reach, how credentials are handled when the model makes calls, and approval steps for high-impact actions that the model can't get around
Prompt injection: both direct attacks and indirect ones hidden in retrieved documents or user content, and testing that our defences actually hold
Data boundaries: what goes into the context window, keeping each customer's data separate during retrieval, keeping personal data out of prompts and logs, and never trusting model output blindly
Testing and vendor risk: adversarial testing before release, re-testing when prompts or models change, and checking how third-party model providers handle our data
We follow current OWASP LLM guidance, but we're looking for someone who has done this in production, not just read about it.
Cloud security and threat detection. You'll shape and maintain our AWS security baseline (account structure, network segmentation, least-privilege IAM) and run our detection tools (GuardDuty, Security Hub, CloudTrail, Config). When something looks off, you'll be among the first to look into it, and you'll improve the tooling that helps us spot problems early.
Data protection. You'll set how we encrypt and protect sensitive data: KMS key management, field-level encryption and tokenization for things like card and credit data, classifying data with Macie, and controlling access across RDS, MongoDB and S3. You'll also make sure real customer data never ends up in staging or QA.
Application security. You'll build and run our SAST, SCA and secrets scanning in CI/CD, work with engineers to fix what it finds, run or coordinate pen tests, and review code and designs for injection flaws, whether SQL, NoSQL or prompt injection in our AI features.
Perimeter and availability. WAF rules, DDoS protection (Shield, rate limiting) and API abuse protection, tuned so they stop bad traffic without hurting real users.
Governance and incident response. You'll keep our incident response plan up to date, run tabletop exercises alongside our DR drills, support ISO 27001, RBI and DPDP control documentation, and represent security in external audits. Your runbooks should also cover AI incidents: a prompt injection that works, an agent doing something it shouldn't, or personal data showing up in model output.
What we're looking for
6+ years in security engineering, with real depth in at least two of cloud security (ideally AWS), application security and data protection, and working knowledge of the rest
You've owned a security charter end to end for infrastructure and applications. It might have been a small company, a single product or a business unit within a bigger organisation. What matters is that you were accountable for the outcome.
You've hired engineers and helped them grow. You've set a hiring bar, run interviews, mentored people, and built a team that does great work without needing you in every decision.
Hands-on experience with AWS security services such as GuardDuty, Security Hub, IAM, KMS, WAF and Shield
You're comfortable reading application code. You don't need to be a full-time developer, but you should be able to spot an injection flaw or an over-privileged service account in a PR.
You've built or run a CI/CD security pipeline (SAST, SCA, secrets scanning)
A solid grasp of encryption, key management and handling credentials safely in production
You understand how LLM apps are put together (context windows, retrieval, tool calling) well enough to see where the trust boundaries are
What will make you stand out
You've secured an LLM or agentic feature in production. You scoped its permissions, added approval steps, and learned from what went wrong.
You've red-teamed AI systems or built test suites for adversarial inputs
You've worked under fintech or financial-services regulation (RBI cybersecurity framework, PCI-DSS or similar) and know how to get through an audit without slowing engineering down
You've worked with India's DPDP Act or another data protection law
People you've hired have gone on to do great work, and engineers want to work with you
Certifications like AWS Security Specialty, OSCP or CISSP are welcome, but we care much more about what you've actually built and run
How you'll work
You'll work as a partner to engineering leadership, not a gatekeeper. We want security that ships with the product, not security that holds it back. Expect a good amount of time in AWS and Terraform, code reviews, AI design discussions and the odd conversation with auditors. As your team grows, more of your time will go into hiring and developing people, but you'll stay hands-on enough to keep the technical bar high.
Interview process
Personal Interview 1 (60 mins)
Personal Interview 2 (60 mins)
Final round: team and culture (20 mins)
If this sounds like you, apply here or reach out to us directly.