Software Engineering Lead (GO & Python, AWS)
Optum (company site, opens in a new tab)5+ yrsBengaluruOn-siteDirect career pageEst. 28–42 LPA
Posted on 24 Sept
Reach people at Optum
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at Optum you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Lead design, development, and operation of a high-throughput AWS Lambda-based log processing pipeline handling ~500 TB/day from AWS, GCP, Azure into Splunk Cloud.
- Develop event parsing, transformation, and tiered data routing logic for multiple cloud log formats to optimize licensing costs and support 59,000+ unique log types.
- Build observability tooling, collaborate on architecture decisions, maintain infrastructure as code, and contribute to data standards and new log source onboarding.
Minimum Requirements
- 5+ years of professional software engineering experience.
- Strong hands-on experience with AWS services including Lambda, Kinesis Data Streams, S3, IAM, CloudWatch, DynamoDB.
- Proficiency in Go (primary) for production Lambda functions, plus Python (secondary) for automation and tooling.
- Experience with multi-cloud platforms (AWS primary, working knowledge of GCP and Azure log services) and building high-throughput streaming data pipelines.
Ideal Candidate Profile
- Experienced in designing and operating large-scale serverless event-driven data pipelines in multi-cloud environments.
- Proficient in building production-grade, scalable software with strong operational monitoring, alerting, and error handling expertise.
- Familiar with CI/CD pipelines, infrastructure as code (Terraform preferred), and collaborative code review and trunk-based development workflows.