Team Lead - Software Engineering
Zelis (company site, opens in a new tab)HyderabadOn-siteDirect career pageEst. 18–30 LPA
Posted 3d ago
Reach people at Zelis
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 Zelis 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
- Own the architecture and end-to-end delivery of .NET payment services and APIs, with accountability for availability, fault tolerance, performance, and transaction consistency.
- Design payment workflows including processing, settlements, reconciliation, exception handling, and high-volume transaction handling.
- Lead and mentor engineers; set code quality practices and coordinate delivery with Product, QA, SRE, Architecture, and Compliance.
Minimum Requirements
- Work Experience Required: Not explicitly mentioned in the JD.
- Strong expertise in C#, .NET Core/.NET 6+, ASP.NET Core Web APIs, REST services, and microservices; experience with event-driven architectures.
- Strong SQL Server skills, including complex queries and performance tuning, plus experience with financial transactions and data consistency.
- Experience with Azure services, CI/CD pipelines, Docker, DDD, messaging/eventing, and caching; payment-system security and compliance requirements include PCI-DSS, HIPAA, OAuth2/JWT, and role-based access.
Ideal Candidate Profile
- A hands-on technical lead who can own payment architecture while remaining involved in implementation and engineering standards.
- Candidates with practical payment-domain exposure—especially transaction processing, settlements, reconciliation, and exception handling—are closely aligned.
- Likely to fit environments requiring reliable, secure, high-volume services and cross-functional delivery with product, compliance, QA, and operations teams.