Eli Lilly and Company logo

Software Product Engineering - Development Lead - Silicon Valley Hub

Eli Lilly and Company
August 21, 2026
Remote friendly (San Francisco, CA)
United States
IT
The SPE Development Lead will be responsible for developing and leading technical solutions supporting one or more Digital Health platforms. Engage multiple teams to define technical requirements, develop designs, and align technology enabling platform architecture while meeting medical device regulatory expectations. Lead across SPE projects influencing other tech leads and driving the platform innovation roadmap.

What You’ll Be Doing
- Develop and drive adoption of platform development standards and architecture patterns
- Enable technical delivery of SPE software components, addressing risk, privacy, cybersecurity, and legal constraints
- Design new features that are scalable and resilient
- Align SPE technical solutions with Lilly supported technologies
- Evaluate project ideas, software changes, and future product releases
- Drive platform innovation roadmap; create working proof of concept models in new technology spaces
- Mentor junior team members
- Build relationships with key technical resources and architects to influence SPE systems
- Guide Lilly and non-Lilly software delivery teams in best practice Agile delivery
- Apply medical device delivery models and quality systems to meet regulatory expectations and timelines
- Apply Lilly business processes and technology to ensure deliveries align to strategy/roadmap

Your Basic Requirements
- Bachelor’s Degree in computer science, engineering, or related technical field
- 7+ years delivering software across the lifecycle (design, development, testing, deployment, support)
- 5+ years technical leadership experience delivering software projects

What You Should Bring
- Manage multiple software development and integration efforts
- Lead software design and architecture (examples)
- Propose new ideas and influence peers
- Learn new technologies and apply them
- Agile development knowledge
- Architected asynchronous systems (e.g., Kafka)
- AWS, Azure, and other cloud providers
- Identity management/authentication (preferably Okta)
- GitHub; CI/CD experience and best practices
- Atlassian (Jira/Confluence) or similar tools

Additional Information
- San Francisco, CA hybrid; relocation required