Arindam Paul

Engineering Stories

Blog

Twenty years of building systems across high-frequency trading, classical music technology, emergency healthcare, and industrial automation. These are the stories that don't fit on a resume.

This is a working engineer's blog — not a thought-leadership newsletter, not a hot-takes feed, and not a tutorial site. Every essay is built on something I shipped, broke, or rebuilt with my own hands. The stories are deliberately specific: the exact trading venue, the actual edge case, the line of code that broke at 03:14 in production.

If you're a senior engineer, an engineering leader, a hiring manager, or a recruiter who is trying to figure out what someone with a 20-year career across market making, music technology, and life-critical healthcare software actually knows how to do — this is the long-form version of the answer.

New essays every two weeks. Subscribe via RSS · follow on LinkedIn · or read what I'm working on right now.

Browse by topic

Trading & Markets
Low-latency systems, exchange connectivity, FIX, order books
Music Technology
Apple Music Classical, classical metadata, Primephonic
Healthcare
Emergency teleradiology, two US patents, life-critical software
Career
Twenty years, four continents, three industries, one engineer
Mentorship
Cambridge engineering interns — what they teach me

All essays

Apple Acquisition

How a Rare Book Became Apple's Most Beautiful App

The origin story of Apple Music Classical — and why the Primephonic metadata database we built was different enough from every other music catalog that Apple acquired the whole company to get it.

Classical Music Metadata

Parsing the Da Capo Catalog

How we turned 1,399 pages of printed classical music compositions into a searchable database — and why OCR, hand-tuned heuristics, and a lot of domain knowledge were the only way through.

High-Frequency Trading

What It's Like to Build Systems That Trade Billions

Goldman Sachs reconciliation systems, the ETF desk launch, and eight years of building infrastructure where a single bug costs more than most software engineers earn in a decade.

Career

Twenty Years, Three Industries, One Engineer

From industrial automation to trading floors to Apple Music. What crossing industry boundaries actually teaches you — and why the skills that transfer are never the ones you expect.

About this blog

How often do you publish?

Every two weeks, occasionally weekly when a story is fresh. The RSS feed always has the latest. Cross-posts hit dev.to, Medium, Hashnode, and LinkedIn within 48 hours of the canonical version going live here.

Why no comments section?

Conversation happens on LinkedIn, on the Hacker News submissions, and via direct email. That's where readers actually engage. A comments section on a personal site is mostly spam by week three.

Can I republish or quote your work?

Yes, with attribution — please link back to the canonical URL on arindampaul.com. For full reposts on a publication, ping me at arindam.paul@me.com first — happy to provide a clean copy with your house style.

Do you take guest posts?

No. This is a single-author site. If you want to write about something I've worked on, I'm happy to talk on background or be quoted — email me.

Are you available for hire?

Yes — from June 2026, for senior engineering leadership roles preferentially in APAC and the Gulf. Full details on the available and hire pages, or jump straight to engage.