Principal Software Engineer
Keka (company site, opens in a new tab)10–18 yrsBengaluruOn-siteDirect career pageEst. 40–65 LPA
Posted 16h ago
Reach people at Keka
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 Keka 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 and architecture of scalable, maintainable software solutions end-to-end from design to production reliability.
- Set technical standards and architectural decisions, collaborating with Product, architects, and cross-functional teams to align development with product goals.
- Improve engineering quality through mentoring, code reviews, troubleshooting complex production issues, and introducing new technologies.
Minimum Requirements
- 10 to 18 years of software engineering experience with leadership in architectural decisions and mentoring.
- Proficiency in Web API development, OOPS, SOLID principles, SQL databases; modern language skills with .NET, C#, EF Core as advantages.
- Solid understanding of architectural patterns such as MVC, MVVM, microservices, and experience with distributed systems, data structures, and algorithms.
- Working knowledge of CI/CD pipelines, AWS or Azure cloud services, and Git branching strategies.
Ideal Candidate Profile
- Experienced software engineer with proven leadership in architecture and team mentorship within complex, scalable product environments.
- Comfortable working in multi-language, cloud-based, high-ownership engineering teams with an emphasis on maintainability and production reliability.
- Able to bridge technical and non-technical stakeholders by effectively communicating architectural decisions and troubleshooting outcomes.