Hire a PostgreSQL Expert
Hire a PostgreSQL expert for query optimization, indexing, row-level security, concurrency, and pgvector. EXPLAIN-driven performance work — remote, senior, ex-CTO.
If you need to hire a PostgreSQL expert because a query is slow, a table is locking up, or a database is buckling under growth, that’s my favourite kind of problem. I’m Kuldeep Pisda — a senior backend engineer and former startup CTO in Bengaluru who treats Postgres as a first-class part of the system, not a black box the ORM talks to. I work from query plans and measurements, never guesswork.
What I help with
- Query optimization — I read
EXPLAIN (ANALYZE, BUFFERS)and fix the real cause: sequential scans, N+1 storms from the ORM, bad join order, or a sort that should have been an index. - Indexing strategy — composite indexes in the right column order (equality before range), partial and covering indexes, and index-only scans that never touch the heap.
- Row-level security & multi-tenancy — enforcing tenant isolation in the
database. I wrote django-rls, a Postgres RLS library, so
a forgotten
WHEREclause can’t leak one tenant’s data to another. - Concurrency correctness —
SELECT ... FOR UPDATE, exclusion constraints, and the right isolation level so two users can’t grab the same seat or double-book a room under load. Correctness lives in the schema, not hopeful application code. - pgvector & semantic search — vector columns, HNSW/IVFFlat indexes, and tuning recall vs. latency for embedding-based search.
- Scaling & migrations — safe schema changes on large tables (no
ACCESS EXCLUSIVEsurprises),CREATE INDEX CONCURRENTLY, and moving data without downtime.
Proof you’re hiring
I’ve taken a hot endpoint from ~30 seconds to roughly 200ms — the before-plan showed a sequential scan throwing away tens of thousands of rows; the after-plan was an index scan reading eight cached pages. I’ve enforced no-double-booking with a GiST exclusion constraint (which, as a bonus, made availability lookups ~4000× faster), and scaled a Postgres-backed platform past 30,000 users. The case studies walk through the plans and the numbers.
How engagements work
Usually a focused audit: send me the slow query, its EXPLAIN output, and the
relevant schema, and I’ll come back with the specific fix and the reasoning. From
there it can be a one-off, a short optimization sprint, or an ongoing retainer as
your database-of-record grows. Remote, IST, comfortable with US/EU hours.
FAQ
Can you actually make our slow queries fast?
Almost always — most “slow database” problems are missing indexes, N+1 query
patterns, or plans gone wrong, and they’re fixable once we look at the real
EXPLAIN output rather than guessing.
What do you need from us to start?
The problem query, its EXPLAIN (ANALYZE, BUFFERS) plan, table sizes, and the
relevant schema. That’s usually enough to pinpoint the issue.
Do you handle multi-tenant isolation and RLS? Yes — it’s what django-rls exists for. I can design tenant isolation that’s enforced by Postgres itself, not by discipline.
Can you help with pgvector / vector search?
Yes — from choosing dimensions and index type to tuning ef_search/probes for the
recall and latency you need.
Do you work remotely with international teams? Yes. I’m in India (IST) and regularly overlap with US and EU schedules.
Let’s talk
Send me the query that’s keeping you up at night — get in touch, or grab a time below:
Related: Hire a Django Developer in India · Hire a Django Consultant · Hire a Backend Engineer in India · Hire a Python Developer in India · PostgreSQL Performance Consultant