Backend engineer who ships systems people rely on.
2.5+ years in Node.js/TypeScript and Python on PostgreSQL: APIs for a healthcare platform used by 2,300+ clinics, a modernised 20-tenant ERP, and a CCTV dashboard a guard team uses every night. Every claim below links to proof.
The summary is ready to paste into your ATS or a hiring-manager message.
PyDB's test suite SIGKILLs a writer mid-workload and checks that no committed row is lost. CI runs it on every push.
AI-CCTV alerts for Max Estates, Dehradun: 8 cameras on one screen, patrol compliance, installed on site by me and live since Sep 2026.
A disability-support provider in Victoria built around accessibility, and a bilingual lead-generation site for a Bangkok agency.
A B+Tree with a pager and write-ahead log, a consistent-hash ring, and a rate limiter on a live edge route that returns real 429s.
A decade-old Java monolith to Spring Boot + React, 0 → 1,435 automated tests, worst pages from 15.6 s to 2.4 s. Client code is private; happy to walk through it on a call.
What broke, why, and what fixed it, from a database that lost every committed write to row-level security that quietly switches itself off.
An AI camera box across eight cameras was detecting intrusions, falls, animals and unattended posts, but nothing turned those detections into something a guard could act on at 3 am, or told management whether the patrol route was being walked.
Classifies a shipment's paperwork, checks the documents against each other with rules the customer edits, and routes only the doubtful cases to a person, with an audit trail on every decision.
A decade-old Java monolith with no tests and a database in Singapore read from India, where the number of queries, not their complexity, decided whether a page loaded at all.
Parents emailed to ask for visits, staff approved by email, and security checked IDs by hand at a gate whose QR readers and boom barrier had never been connected to any of it.
A transactional storage engine in pure Python: an 8 KB pager, clustered and secondary B-Tree indexes, and a write-ahead log with redo recovery and atomic checkpoints.
A real-time chat backend where the socket layer never waits on the database: a queue decouples ingestion from persistence and read receipts batch through Redis.
Contract work for businesses in India and abroad: a document-workflow platform for a shipping-software company, a live AI-CCTV dashboard for a gated community, and client websites.
Backend for an EHR platform used by 2,300+ clinics, as one of four engineers.
Joined as an intern and was promoted to software engineer, working on serverless data pipelines for tax computation software.
Internal tools, ERPs and document workflows shaped around how your team actually works.
Camera boxes, gate readers and QR passes brought onto one screen your staff can use.
Audit first, then fix in order of payoff: N+1 queries, slow pages, tenant isolation, deploys.
Documents into data, answers from your own records. The AI reads, code checks, a person confirms.
What are you actually trying to fix? No charge.
Scope, stages, timeline and risks in writing before work starts.
Working software every week, not a reveal at the end.
On your premises or your cloud; training in Hindi or English.
Remote support after go-live, and a retainer if you want one.
Disability support, so accessibility was the design: low-stim mode, persistent text sizing, text-to-speech, an eligibility quiz.
A lead machine: visitors run a free live audit of their own site, configure a quote, and get invited back if they leave. English and Thai.
Paid workshop bookings where two people can't buy the same seat: instant locks, abandoned checkouts released, payment confirmed server-side.
Full D2C commerce with subscriptions and referrals, plus batch provenance: scan the jar, see the hive and harvest.
A real astronomy engine underneath, not lookup tables, driving seven calculation services with booking on top.
A golden-hour calculator for a couple's date and venue, a colour-grade slider, link previews tuned for WhatsApp.
Static-first for mobile data, with a cost estimator that qualifies leads before they reach the phone.
The practitioner publishes articles herself through a proper editing dashboard; handed over with a plain-English guide.
Reads like an architectural drawing set; 348 KB, no dependencies, and a pricer that pre-fills the enquiry.
Free tools that answer a client's first question before the call, written inside the Bar Council's no-advertising rule.
It depends on scope, so I don't publish a rate card. After a free call you get a fixed quote in writing, split into stages, and you pay stage by stage, so you never pay for work you haven't seen working.
The written plan gives a date for every stage. As an example, a visitor-pass app with a multi-level approval chain was planned at 10–15 working days. If your deadline isn't realistic I'll say so on the first call, not in week three.
You own the code, the data and the accounts from day one, in your name. Every stage ships with tests and plain-language notes, so any competent developer could pick it up.
I do, remotely, or on a monthly retainer if you want changes and monitoring. Or a clean handover to your own team, with documentation and tests that fail when the important logic breaks.
Yes. I visit sites across Uttarakhand and Delhi NCR and work remotely everywhere else. Training is in Hindi or English, and I built a dashboard so a guard could use it at 3 am without help.
Yes. I sign an NDA if you want one, and I describe client work by sector, not name, unless you agree to be named.
Tell me what's slow, manual or breaking. I reply within 24 hours and say honestly whether software fixes it. Not ready to talk? 12 questions to ask before you hire any developer, including me →
I don't just describe systems, I build them. These run for real in your browser.
Write-ups of real problems: what broke, why, and what fixed it.
Hiring, a project, or a question about something I wrote — type it below, or email anichandan124@gmail.com.
Prefer email?