Chennai, India

Builds systems companies run on

I take rough ideas, decide what they should actually be, and get them to production.

Lending, workforce, billing, ERPs. Multi-tenant SaaS across India and Saudi Arabia.

Rough ideas in.

Production systems out.

That is the whole job. The rest is discipline.

1.15M lines of code~1,600 API endpointstwo teams of six700+ students, every daysix products on one control planethree roles in eighteen monthsIndia and Saudi ArabiaChennai, IST1.15M lines of code~1,600 API endpointstwo teams of six700+ students, every daysix products on one control planethree roles in eighteen monthsIndia and Saudi ArabiaChennai, IST

The work.

Five systems. No live demos, they are proprietary. Instead: the architecture, the decisions, the numbers, all from the real repos. Click through for the full write-up.

By the numbers · all pulled from the repos

0.00M
lines of code I wrote or led, across five systems
~0
API endpoints in the repos
0
endpoints in GroundIT alone
0
database models in a school ERP built solo
0+
students whose school day runs on it
0
products on one control plane, built alone
0
roles in eighteen months
0
countries with statutory payroll packs
Preethan SK
Chennai · 13.08°N 80.27°E

About

Three roles in eighteen months. Same desk.

I joined Sysmedac in January 2025 as a backend developer. Eighteen months later I lead product and engineering across two teams of six. In between, I built the billing and tenant layer that every Sysmedac product sits on, by myself.

Alongside that I run Emplotec, my own company. Under it I built a school ERP that more than 700 students use every day, and a hostel ERP grown out of one real hostel's software.

What I am best at: taking a rough idea, deciding what it should actually be, and getting it to production. I am in Chennai, finishing a BCA at SRM University, and I work in English and Tamil.

  1. Jan 2025
    Sysmedac, backend developer
  2. 2025
    Founded Emplotec. Two ERPs, solo
  3. May 2025
    Full stack. Built Sysmedac One alone
  4. Jun 2026
    Product & engineering lead, two teams of six

How I work

01

Spec first, always.

Around 200k lines of specs and over a hundred architecture decision records sit next to the code in my repos. The document comes before the build, and it stays the source of truth after.

02

If it matters, it fails the build.

Per-route JavaScript budgets live in the test gate. A lint fails the lending platform if a market rule is hardcoded. Rules I have to remember are rules I will eventually break, so the machine remembers them.

03

Boring parts, interesting seams.

Modular monoliths, Postgres, queues, an outbox. The technology is deliberately unexciting. The effort goes into the seams: signed contracts between systems, entitlements, tenant isolation at the database, audit trails nobody can edit.

Node.jsTypeScriptNestJSPostgreSQLMySQLRedisPrismaDrizzleBullMQNext.jsReactTailwindFlutterDockerGCPKeycloakOpenTelemetryRazorpay

Contact

Building something that has to hold up?

Then I would like to hear about it. One email, no forms. I reply from Chennai, usually the same day.

preethan.sk@gmail.com