Systems design
Service boundaries, data models, integration contracts and failure modes — chosen so the second year of a product isn't spent undoing the first.
System designAPI designEvent-drivenMulti-tenant
Director of Technology
Technology leader with 10+ years across enterprise SaaS, industrial services and regulated healthcare platforms. I own architecture, engineering, cloud, security and IT operations end to end — and I still build alongside the team.
I trained as an electrical and electronics engineer and came into software the long way round — writing applications, then supporting enterprise SaaS at scale, then senior engineering, and now running technology as a whole: architecture, engineering, cloud, security and IT operations.
Along the way the research side of that early work produced a filed patent and a published paper, which is probably where the habit of measuring things before believing them came from.
Most of what I've built lives in environments with real consequences — systems an auditor, a regulator or an enterprise customer eventually reads the documentation for. That's made me comfortable holding an engineering mandate and a compliance one at the same time.
I lead small teams on short cycles and stay technical on purpose. I write code, review schemas, sit in the interviews and take the call when something breaks, which is the only way to keep an architecture opinion worth having.
Deep enough to build it myself, senior enough to own the consequences.
Service boundaries, data models, integration contracts and failure modes — chosen so the second year of a product isn't spent undoing the first.
Modern web applications end to end: typed front ends, service layers, relational data, background jobs and deployments that roll back cleanly.
Serverless and managed services where they earn their cost, low-code where it ships faster, with a clear rule for which one a problem belongs to.
Identity and access design, encryption posture, incident response, and a policy set written to be used rather than filed. Audit and due diligence handled first-hand.
Architecting LLM features that survive production — retrieval over private data, evaluation, guardrails, and automation with a human in the loop.
Hiring and growing engineers, roadmaps that survive contact with reality, vendor and cost management, and translating technology for non-technical leadership.
Five layers, one person accountable for all of them — with security running across every one.
Web and mobile interfaces, internal consoles, the surfaces the business is judged on.
Business logic, workflow, automation and reporting — built to be extended rather than rewritten.
APIs, events, webhooks, message contracts and third-party platforms that document themselves badly.
Schemas, migrations, pipelines, analytics and retention — designed before the first feature ships.
Cloud, networking, identity, endpoints, telephony, monitoring, backup and the bill at the end of the month.
A capability, not a religion. I architect it the way I architect anything else.
I design LLM features the way I'd design a payment flow: define the failure mode first, measure before believing the demo, and keep a person in the loop wherever being confidently wrong is expensive.
Most of the real value has come from unglamorous places — retrieval over data we already own, extraction from documents nobody wants to read, and quietly deleting work that used to be a person and a spreadsheet.
I also interview and hire for it, which has sharpened the distinction I care about most: something that impresses in a demo versus something that survives a month in production.
Roles have widened rather than changed direction — each one kept the last.
Healthcare technology · United States
Senior Software Engineer · Marine & industrial services
Enterprise SaaS
Engineer · Technology services
Software products & consulting
An engineering degree, and a return to formal study for analytics.
Indian Institute of Management, Kozhikodee-MDP, Advanced Analytics and Business Intelligence · 2023–2024 · Grade A
KCG College of TechnologyB.E. Electrical and Electronics Engineering · 2013–2017
EnglishProfessional
TamilNative
A filed patent, a published paper, and the recognition that came with them.
IN 3833/CHE/2015Filed July 2015 · EMERGEION
Voltage stability control using adaptive filter designSpringer · Anna University Annexure II
Best Researcher AwardApril 2017
Architecture, platform decisions, security, AI in production — or anything else on this page. Email reaches me fastest.
hello@nijandhan.com