Sourav Kohli
PythonDjangoREST APIPostgreSQLAWSDockerAI Integration

Lead backend engineer keeping a live AI mental-health platform stable and growing.

Lead backend engineer for Meomind — an AI-powered mental health platform serving real users. Responsible for maintaining and extending the Python/Django backend of a live healthcare product.

View live product
Meomind mental health platform — the live product I maintain as lead backend engineer
The live Meomind platform — backend maintained and extended by me as lead backend engineer.

The Context

Mental health support is expensive and inaccessible for most people. Meomind’s approach: build a platform around a curated library of real therapy sessions, AI-driven assessments, and guided tools that users can engage with on their own terms and schedule, at a fraction of traditional therapy costs.

The platform is live, serving real users in a sensitive domain. “It’ll do for now” isn’t an acceptable standard when you’re handling data about people’s mental health.

System Architecture — Meomind

Content

Therapy Library

  • Real therapy sessions
  • Guided exercises
  • Mood assessments
  • Journaling tools

Meomind Backend

Python / Django · PostgreSQL · AWS

Content Delivery

session streaming & access

AI Assessments

personalised recommendations

Progress Tracking

user journey & insights

REST API Layer

mobile & web clients

Outcomes

User Wellbeing

  • Accessible therapy
  • Personalised support
  • Progress visibility
  • Continued reliability

Live healthcare product — reliability is non-negotiable

What I Do

As lead backend engineer, I carry the backend day-to-day. This is ongoing work — not a one-time build.

Feature development: I design and ship new features in the Python/Django codebase — new content delivery capabilities, assessment flows, personalisation hooks, and API endpoints consumed by the mobile and web clients.

Production reliability: A live healthcare product can’t have unexplained downtime or data issues. I maintain monitoring, debug production incidents, manage database performance, and keep the AWS infrastructure healthy.

API stewardship: The backend serves both mobile and web clients. I own the REST API contracts — versioning, consistency, and backward compatibility when the product evolves.

Codebase ownership: When you’re the lead engineer, there’s no one to hand off hard problems to. I’ve built a deep understanding of this codebase’s history and constraints, which means I can make good decisions quickly.

Why It Matters

In healthcare, reliability isn’t a nice-to-have — it’s the product. Being trusted to lead the backend of a live mental health platform is a specific kind of trust: the kind that comes after proving you understand the domain, take the responsibility seriously, and deliver without hand-holding.

This engagement is also evidence that I work well over time. Long-term clients who keep expanding my scope are more valuable signal than a one-time delivery.

Tech Stack

Python · Django · REST APIs · PostgreSQL · AWS · Docker · AI Integration · Git