Lead Ruby on Rails & Python Developer – AI & Agentic AI
ChiStats (company site, opens in a new tab)4–6 yrsPuneOn-siteDirect career pageEst. 12–22 LPA
Posted 2d ago
Reach people at ChiStats
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 ChiStats 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 a small Rails/Python engineering team while owning technical design, coding standards, reviews and delivery.
- Plan and execute migration of Rails applications to Python, including APIs, business logic, jobs and data; maintain functional parity with testing and minimize business disruption.
- Build production web applications and REST APIs, and lead implementation of LLM integrations, RAG pipelines and agentic workflows.
Minimum Requirements
- Work Experience Required: 4–6 years in software development; at least 1–2 years leading or mentoring developers.
- Strong Ruby on Rails proficiency and Python web development experience; hands-on Python REST API, ORM and database migration experience are required.
- Hands-on experience with LLM integrations, RAG, embeddings, vector databases, and building AI agents or agentic workflows.
- Work hours: 2:30 PM–11:30 PM IST.
Ideal Candidate Profile
- A hands-on technical lead who can guide a small team while remaining directly involved in architecture, implementation and delivery.
- Strong fit for Rails-to-Python modernization, particularly candidates able to map Rails components and workflows to Python equivalents; prior migration leadership is a plus.
- Insurance or InsurTech experience is preferred, especially exposure to policy administration, claims or underwriting workflows.