Data model first
Most backend problems are data problems. I start with the schema, the constraints and the access patterns — the APIs follow naturally.
Senior Python developer and Tech Lead from Kochi, Kerala — happiest deep in the code, solving the hard engineering problems behind reliable products.
“Most backend problems are data problems. Get the model right and the API, the security and the scale follow.”
I'm a Python backend engineer with more than eight years of experience building scalable, secure systems. I completed my B.Tech in Computer Science and Engineering in 2018 and began my career the same year as a Junior Software Developer at SparkSupport Infotech in Infopark, Kochi.
Over five and a half years at Vofox Solutions I grew from Software Developer to Senior Software Developer, owning backend delivery for clients in Australia, the USA and the Philippines — including the admin platform for a major Australian e-commerce business used by 1,000+ staff — and leading a team of four developers.
At TerrificMinds I built the backend of a multi-tenant dental practice integration platform serving around 1 lakh tenants and thousands of third-party integrators through nearly 100 API endpoints, and led backend development of a learning platform used by 100+ organisations with real-time AI roleplay over WebSockets. Today, as Tech Lead, I lead backend engineering while staying hands-on in design, development and code review, and I'm helping shape the company's ISO 27001 engineering practices.
I'm known for clean, maintainable code, rigorous code reviews and fast, reliable delivery — and I'm always open to conversations about challenging backend engineering work.
Most backend problems are data problems. I start with the schema, the constraints and the access patterns — the APIs follow naturally.
Authentication, authorisation, rate limits and audit trails are designed in from day one, not bolted on before launch.
Thin views, explicit service layers, consistent formatting and tests enforced in CI. Code is read far more than it is written.
AI-assisted development (Cursor, Claude) where it helps, CI/CD and observability everywhere — speed without surprises in production.
Select a category to explore. Levels reflect production experience, not tutorials.
The core of my day-to-day work.
How I structure systems that many teams and partners depend on.
Modelling, migrating and tuning relational and in-memory stores.
Background work, queues and real-time delivery.
From a Dockerfile to production on AWS and GCP.
Guard rails for code, data and teams.
Analytics and third-party platforms I have shipped against.
I'm open to conversations about senior and lead backend engineering roles, and about hard problems in Python, APIs and multi-tenant SaaS.