2023
Full-Stack Developer · Legabyte
Started part-time — full-stack legal-tech for the 'Mamla Karo' team in JavaScript and Python. Owned the backend architecture and shipped it to production.
THE BYLINE · THE LONG VERSION
Behind the Byline
The developer behind this broadsheet — Anirban Das, full-stack, currently building ops-automation systems at Rentor after Bau.ai, Medecro.ai, and a run of part-time starts before that.
► FROM PAGE 1 · THE LEAD STORY, CONTINUED
The front page says I ship the boring, load‑bearing parts on purpose. Here is the long version: I build the systems people only notice when they fail — auth, data, real-time, the AI feature that has to be right — and I stay close to them long after they ship. The interesting part of engineering, to me, starts where the demo ends.
I started part-time at Legabyte and ProjectX while learning the craft, went full-time at Medecro.ai in late 2024, spent early 2026 shipping document intelligence at Bau.ai in Berlin, and now build ops-automation systems at Rentor. Across all of them the work has been the same shape: own the data model, the API, and the frontend — and stay through the on-call.
Live and in production: an RBAC/PBAC system across 80+ microservice APIs, AI-powered X-ray analysis, real-time medical dashboards, tender-document intelligence, and an automation engine with exactly-once delivery. The side of the work I most enjoy is the part nobody notices until it breaks.
“I like the unglamorous problems — auth, data integrity, the AI feature that has to be right. If it ships and still holds up on Monday morning, that's the work.”
The method
A feature is a system — inputs, constraints, and failure modes — not a happy path with good lighting. I'd rather ship the correct, slightly less flashy version than the one that demos well and flakes in CI: types end-to-end, tests that mean it, and a sane fallback for when the model is confidently wrong.
The next assignment
A team that ships often, reviews PRs the same day, and treats users as more than tickets. Remote or on-site, India or international — the masthead matters less than this: engineering owns outcomes, and the product is big enough that the work counts.
On the desk
By day: exactly-once delivery and a no-code pipeline builder at Rentor. After deadline: sharpening terminal tooling and maintaining Bluekeys, a typing-trainer CLI that got pleasantly out of hand.
TIMELINETHE WORK HISTORY, IN COMMIT ORDER
Career timeline
2024
Frontend Architecture · ProjectX
Led the frontend for Infinity-OS — a full operating system running in the browser with minimal latency — while joining Medecro.ai full-time that September.
2025
Full-Stack Developer · Medecro.ai
RBAC & PBAC across 80+ microservice APIs, AI X-ray analysis, real-time medical dashboards, and a digital prescription system — at 100% TypeScript coverage with Playwright E2E.
2026
Bau.ai → Rentor
Document-intelligence features at Bau.ai in Berlin, then an ops-automation engine at Rentor — a no-code pipeline designer backed by an exactly-once server-side executor.
THE STYLE GUIDEHOUSE RULES FOR SHIPPING SOFTWARE
The style guide — house rules
§1A test that fails only in CI isn't flaky — it's the honest one.
The 'flaky' label usually hides a real cause: a race, a shared fixture, a timezone. The test found it. The fix is to listen, not to hit retry.
§2Types are documentation that can't go stale.
I write TypeScript end-to-end less for the compiler than for the next person — usually me, six months later — who reads the signature instead of the source.
§3The boring parts are the product.
Auth, migrations, error states, retries. Nobody demos them; everybody depends on them at 2 a.m. That's where the effort earns the most.
§4'It works on my machine' opens the bug report, it doesn't close it.
The real question is always what's different — the env var, the data, the clock, the network. Closing that gap is most of the job.
LETTERS TO THE EDITORREADER QUESTIONS, ANSWERED FROM THE DESK
Letters to the editor
Q. Frontend or backend?
A.Both, genuinely. I've architected an in-browser OS frontend and RBAC across 80+ backend APIs in the same year. I go where the hard part is.— ED.
Q. Are you actually available?
A.Yes — open to full-stack, frontend, or product-engineer roles, remote or on-site, and I'll relocate for the right team and a fast CI pipeline.— ED.
Q. What's the AI experience, really?
A.Shipped X-ray analysis, transcription, RAG, and document auto-fill in production — with evals, guardrails, and fallbacks, not a one-off demo.— ED.
Q. TypeScript zealot?
A.Reformed pragmatist. 100% coverage where it earns its keep; a well-placed escape hatch when the deadline is real and the risk is low.— ED.