Senior Cloud Security Engineer

At Lilly, the work is demanding because patients are waiting. We unite caring with discovery to help make life better for people around the world, knowing that every decision, every detail, and every day matters. Headquartered in Indianapolis, Indiana, our over 50,000 employees around the globe take on complex challenges to discover and deliver life-changing medicines, strengthen how health is understood and managed, and support the communities we serve. This is hard, urgent, selfless work—but it’s work worth doing. If you’re driven by purpose and ready to bring your best to work that truly matters for patients, we invite you to join us.

Cloud Security Engineer

Lilly's Security Architecture and Engineering team is looking for a Cloud Security Engineer who is, first and foremost, a builder. Most of your time will go to designing and writing the automation behind CloudSec as a Service, working alongside the engineers who build and maintain it, and helping hunt down the manual, repetitive work that slows the team down. You'll have support and guidance as you grow into the role, but you should be the kind of engineer who enjoys figuring things out rather than waiting to be told exactly how.

What You'll Be Doing

You'll help drive automation across the CloudSec team, designing, testing, and deploying automated solutions in line with Lilly SDLC practices, and following them through to production rather than handing off once something's built.

You'll help maintain the Feature Request backlog for CloudSec services and tooling, tracking requests and helping spot opportunities for continuous improvement, including hunting down repetitive manual work worth automating.

You'll work with the teams consuming what you build, helping design, test, and implement new security controls across the organisation, and staying close enough to real use cases to understand what actually works for the people using it. You'll also support the wider Lilly development community with strong development controls and practices, and contribute ideas to the CloudSec service roadmap.

How You'll Succeed

You're comfortable working with some ambiguity. Not every task comes with step-by-step instructions, and you're willing to work through a problem and ask good questions along the way rather than needing everything handed to you. You look for repetitive manual work worth automating, and with guidance, you can spot opportunities within existing tools and processes to build something useful.

You're building the habit of treating infrastructure changes with the same care as application code, testing your automation before it reaches production, and thinking about how a deployment could fail safely rather than assuming it won't. You deliver visible progress at regular intervals rather than disappearing and reappearing with a finished thing, and you're developing the habit of documenting your work as you go, so someone else could pick it up if they needed to.