Senior Application Support Engineer – SPE
Eli Lilly and CompanyMatch Score
Against your primary resumeLogin to See Your Match Score
Create a free account or log in to unlock your CV match score across:
Protocol Intelligence
Data-driven signals on your job's competitivenessTier-1 brand, mid-level generalist role, metro location, and broad skillset increase candidate competition.
Regulated life-sciences context and compliance knowledge required make background fit sensitivity high.
Explicit 4–6 years requirement, regulated-industry experience, and specific cloud/monitoring skills enforce strict filtering.
Job Description
Structured overview of role & requirementsAbout This Role
Provide advanced L2 technical support and incident resolution for a suite of software products, focusing on application functionality, integrations, performance, and security.
Collaborate with development and cross-functional teams to analyze root causes, reproduce issues, and implement timely fixes or workarounds.
Monitor application health using tools like AWS CloudWatch, maintain documentation, participate in incident management including RCA, and support deployment activities including validation and rollback.
Minimum Requirements
4-6 years experience in application support, technical troubleshooting, or software engineering.
Bachelor’s degree in computer science, engineering, or related field (or equivalent practical experience).
Experience supporting products in regulated industries such as Life Sciences or Healthcare.
Willingness to work flexible shifts including non-standard hours, weekends, and holidays (shifts: 6AM–2PM or 2PM–11PM).
Ideal Candidate Profile
Experienced in troubleshooting web applications covering frontend (React, Material-UI) and backend (Node.js, Express.js) technologies in a regulated industry environment.
Proficient with monitoring, logging, alerting tools (e.g., AWS CloudWatch, Winston), incident management workflows (e.g., Jira, ServiceNow), and supporting CI/CD pipelines.
Able to independently manage documentation such as runbooks and troubleshooting guides, and effectively collaborate across product, QA, and engineering teams for continuous improvement.