People · Business · Technology

Anuj Sadani

I build AI systems and the teams that build them. 16+ years across engineering leadership, microservice systems, and enterprise AI — currently Principal SDE at Infrrd. I'm known for mentoring engineers to their best, translating customer problems into honest technical bets, and steering AI adoption toward outcomes that actually hold up in production. People, business, and technology — in that order when it matters.

Anuj Sadani
Articles
Topic
Flavor
AI EngineeringThe Human Leverage Mapcraftresearch
"When intelligence becomes abundant, judgment becomes scarce."
When intelligence becomes abundant and cheap, judgment becomes the scarce thing. A two-axis map for finding the human value that survives AI: where your leverage goes once the machine can produce the answer, how that leverage quietly collapses, and how to keep the faculty it rests on. A field guide to staying the one who decides what is worth asking.
June 24, 2026
Read →
AI EngineeringThe Engineers Who Didn't Make It Through AIcraftmodels
"Every one of them was right. Every one of them still failed."
A companion to Three Leaders, One Market, turned on people instead of firms. Twelve brilliant principal engineers made rational decisions based on the world they knew, then the world changed faster than their optimization function. The Craftsman, the Skeptic, the Lone Expert, the Builder: twelve failure modes of senior technical leadership during a discontinuity, braided into one argument. No villains, only people who optimized for a reality that stopped existing.
June 23, 2026
Read →
AI EngineeringThe Monk Who Oversold the AImodelsresearch
"You can rent capability. You cannot rent a moat."
A product leader replaced the company's R&D with borrowed foundation-model capability, scaled brilliantly for two years, won the CEO's trust, and then dissolved the only moat the product had. Why borrowed intelligence is shared intelligence, why even strong ML teams give the moat away, and how to borrow without dissolving. Includes a downloadable designed PDF.
June 18, 2026
Read →
AI EngineeringThree Leaders, One Marketmodelscraft
"There are no villains. When the company fails, the leader is the one left on the stake."
A triptych. Three experienced leaders take three defensible AI strategies in the same market: one holds the proven playbook, one rides every wave, one builds the right system. All three fail, by different paths, because the market kept moving what it rewarded. A field report on good-faith failure, with no villains and the leader on the stake. Includes a downloadable designed PDF.
June 18, 2026
Read →
AI EngineeringVerification-maxxingagentscraft
"Generation is solved. Judgment is the moat."
The syntax tax collapsed; the verification tax replaced it. Why "vibe coding to agentic engineering" is a shift in where software's cost lives — Agent = Model + Scaffold, and most teams invest in the wrong half.
June 17, 2026
Read →
AI EngineeringThe Barbell and the Vanishing Middleagentsrag
"The middle didn't disappear. It became a load-bearing wall you can't see."
Where intelligent document processing is heading through 2028: value migrating to document infrastructure on one end and decision automation on the other, while the extraction layer becomes invisible, not simple. Includes a downloadable designed PDF.
June 9, 2026
Read →
AI EngineeringThe safety layer is youagentscraftsupply-chain
"The safety layer for the code your agents write is you. Right now you catch six percent."
A study put real developers in five-hour sessions with frontier coding agents that were quietly stealing user data. 94% shipped the sabotage after reviewing and approving it. Why human review is a 6% control, why the real attack surface is the agent's context and not the model, and why daily use erodes the one trait that actually catches it.
June 6, 2026
Read →
AI EngineeringFrom TODO to TOKNOWcraftagentic-coding
"The TODO was a promise to do the work. Make the TOKNOW a promise you refuse to write."
We used to defer work with a TODO. Now AI writes the code, the tests, and the docs in minutes, and what gets deferred is understanding the system. Why this debt compiles and passes its tests, the cognitive-equity cost of letting the agent hold the comprehension, and the one question I treat as the real launch gate.
May 31, 2026
Read →
AI EngineeringThe spec lies until something runs itpromptingevalscraft
"The spec you can finally trust is the one that has already eaten its examples."
I had a template and a skill to write these posts and still kept opening a real one. Why template plus skill wasn't enough, why adding a worked example cost more tokens and worked anyway, and how feeding its lessons back into the spec made the lean version the honest one.
May 31, 2026
Read →
AI EngineeringSynthID can't tell you who made it.provenance
"Machine-made is not the same as authentic."
Google wired SynthID into Gemini: drop an image in, ask if it's AI, read the answer in five seconds. The check is real and it's the best we have. It also tells you whether a model made something, not who did. Why screenshots beat it, why exiftool can't, and why video and audio are the real win.
May 29, 2026
Read →
AI EngineeringWhat is "agentic OCR," really?agents
"Traditional OCR is a camera. Agentic OCR is a cinematographer."
Vendors keep renaming document extraction agentic; skeptics call it LLM orchestration in a trench coat. The honest definition, three metaphors, and a decision table for when the word earns its keep.
May 29, 2026
Read →
AI EngineeringSelf-Improving AI, Honestlyagentsresearch
"The map is real. The 'step toward AGI' label is doing far more work than the results actually carry."
A landscape read across Reflexion, STaR, Voyager, AI Scientist, Darwin Gödel Machine, TTT/TTRL, and the 2026 SIA paper. Where self-improving AI actually works today, and the four pieces still missing for the AGI framing to hold.
May 28, 2026
Read →
AI EngineeringGoogle is quietly changing what "Flash" meansmodelscost-latency
"Flash is the new product floor, not the cheap tier."
Gemini 3.5 Flash beats 3.1 Pro on agentic benchmarks, ships GA across Google, and triples its own per-token cost. What the agent-first pivot means for builders.
May 22, 2026
Read →
AI EngineeringMoral Surrenderagentscraft
"Cognitive surrender costs you skill. Moral surrender costs you the architecture."
Two failure modes when working with AI agents — and why surrendering judgment is more dangerous than surrendering skill.
May 8, 2026
Read →
AI EngineeringContextual retrieval, honestlyrag
"Treat it as a strong default chunk-level upgrade, not a strategy."
Anthropic's contextual retrieval, read straight: real gains, real preprocessing costs, and the blind spots around long-horizon reasoning and governance.
May 7, 2026
Read →
AI EngineeringAutomated prompt optimization, in 2026promptingevals
"Prompts have stopped being something you write. They are something the system compiles."
A field guide to DSPy, TextGrad, ACE, GEPA, and the evaluation and Pareto trade-offs that decide what survives production.
May 4, 2026
Read →
AI EngineeringThe Complaints Are Valid. The Leap Is Real.models
"The leap is real. It's just not the leap people expected."
15 months after R1, DeepSeek V4 lands with valid criticism — but a genuine architectural win hiding behind the benchmark noise.
Apr 24, 2026
Read →
SecurityThe Mother of All AI Supply Chains: MCP's By-Design RCEsupply-chain
"The most dangerous vulnerabilities aren't bugs — they're features."
A configuration string is a shell command. Anthropic called it expected. OX Security called it an RCE.
Apr 21, 2026
Read →
DataThe Data Product Manifesto
"Data is the new oil. Valuable, messy, and everyone's hands are dirty."
Seven pillars for treating data as a first-class product, not a departmental afterthought.
Apr 2026
Read →
AI EngineeringThe Five Layers of the Modern AI Coding Agent Stackagentic-coding
"Any sufficiently advanced autocomplete is indistinguishable from AGI — until it rewrites your prod config."
Five architectural layers that separate a genuine productivity multiplier from expensive autocomplete.
Apr 2026
Read →
InteractiveAI Coding Agent Stack — Interactive Mind Mapagentic-coding
"A map is not the territory. But sometimes the territory is so confusing you really need the map."
37 tools, 6 clusters, one SVG — a pannable, filterable map of the 2026 AI coding ecosystem.
Apr 2026
Explore →
AI EngineeringAI Shrinkflation: The Silent Regression Your Team Won't See Comingmodelsevals
"Same logo. Same price. Different soul."
The model you shipped last quarter may not be the model running today — and your tests won't tell you.
Apr 2026
Read →
AI EngineeringFlex & Priority: One Line of Codecost-latency
"The best infrastructure decision is the one that costs 40% less and ships today."
One parameter — service_tier — trades latency for cost in Gemini production workloads.
Apr 2026
Read →
PolicyAI Writes the Code. You Own Everything.provenance
"The machine wrote the code. The human signed the DCO. The lawyers are still figuring out the rest."
The Linux kernel's first official AI policy redefines authorship — and puts the legal weight squarely on you.
Apr 2026
Read →
InfrastructureBreaking the Object-File Barrier
"For ten years, object storage and file systems refused to share a table. AWS finally sat them down."
Native NFS v4.1 on S3 buckets erases the decade-long object-vs-file divide — no rewrite needed.
Apr 7, 2026
Read →
SecurityThe LiteLLM PyPI Attack: A Supply Chain Postmortemsupply-chain
"In open source we trust — and sometimes that trust ships as a .pth file that phones home."
A hijacked PyPI account, 13 minutes, and 95M installs at risk — a blueprint for targeting AI developers.
Mar 24, 2026
Read →
Publications
Books
Amazon ↗
Amazon ↗
Papers
arXiv ↗
arXiv ↗
arXiv ↗
arXiv ↗
SSRN ↗
SSRN ↗
Digital
Ko-fi ↗
Ko-fi ↗
Ko-fi ↗
Ko-fi ↗
Ko-fi ↗
Ko-fi ↗
Ko-fi ↗
Ko-fi ↗
Ko-fi ↗
Ko-fi ↗
Journey
2009
NVIDIA
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
Delivery Hero
2021
Infrrd
2022
2023
2024
2025
2026
NVIDIA
Pune  ·  Full-time  ·  10 yrs 6 mos
Senior Tools Development Engineer
Oct 2014 – Jan 2020
By this point I'd outgrown .NET and made a deliberate pivot to Python — new territory, but I adapted fast and never looked back. The scope expanded: I led a small team of Python developers, built automation frameworks for the Tegra/Jetson embedded platform, and added data analytics and reporting tooling on top of the existing automation work. I went from writing tests to leading the engineers writing them — and owning the full SDLC end to end.
Tools Development Engineer
Aug 2010 – Sep 2014
Built NVQM — a full-stack .NET application that managed NVIDIA's internal software quality lifecycle: test case management, bug tracking, RCCA, reporting, and analytics. This is where I discovered I genuinely enjoyed building for engineers, making their daily work less painful. The system touched QA and dev teams across the org, which meant constant stakeholder conversations, requirement translation, and shipping features people actually used.
Software Quality Assurance Engineer
Aug 2009 – Jul 2010
An honest pit stop in the QA department before moving into tools development. I spent the year building dashboards and internal tracking tools to help the QA team work more effectively — and in doing so, realised my instinct was less to find bugs and more to build things that helped others find them.
Why I left Spending ten years at NVIDIA gave me an incredible technical foundation. Very early on, I was trusted with end-to-end ownership of the product cycle — handling both development and deployment. That level of accountability taught me a vital lesson: building mutual trust and letting your work speak for itself is the ultimate driver of your career. I'm incredibly proud of the engineering work I did there, but it was largely on an internal stage. Eventually, I outgrew that comfort zone. I wanted to build products that real customers touched and interacted with — shifting my audience from the internal to the broader market.
Delivery Hero
Berlin, Germany  ·  Full-time  ·  11 mos
Software Engineer II
Feb 2020 – Dec 2020
Joined a logistics tribe inside one of the world's largest food delivery networks — responsible for the infrastructure that moves orders from restaurants to riders to customers at scale. Hands-on with Python/Flask microservices, on-call rotations, Kubernetes, containerisation, CI/CD, and end-to-end release management. Worked closely with Data Science and BI teams to integrate analytical workflows that shaped real-time operational decisions. This was my first taste of genuine end-to-end ownership: you build it, you ship it, you support it — and it changed how I think about software.
Why I left Eleven months, six nationalities in one pod, and the most culturally rewarding experience of my career to that point. I hadn't planned to leave — the work was meaningful and the team exceptional. But COVID brought uncertainty, and family back in India brought clarity. I returned home.
Infrrd
Pune / Bangalore, India  ·  Full-time  ·  5 yrs 4 mos  ·  Current
Principal Software Development Engineer
May 2025 – Present
Moved from Applied ML practitioner to Principal Engineer — from building AI systems to leading the strategy behind them. I now own the Python stack across the organisation, lead and mentor a team of 8+ engineers, and run a focused LLM cost-optimisation pod alongside multi-feature delivery teams. The GenAI and hybrid ML+AI work I've architected contributed to Infrrd's recognition as a Leader in the Gartner Magic Quadrant and by Everest Group. Two patents are grant-pending. Two papers are on arXiv. The work continues.
ML Engineering Technical Architect
Nov 2021 – Apr 2025
Went deep on Applied ML and started owning the AI transition company-wide. I moved from practitioner to architect — designed the hybrid ML+AI cost architecture that cut operational costs 30–40% versus LLM-only approaches, led the GenAI platform work, built agentic workflows with CrewAI, and co-authored two technical patents. Owned the enterprise Python stack and evangelised MLOps best practices across engineering. The "Innovator of the Year" recognition from Deep Analysis meant more than any award — it came from people who watched the work firsthand.
Technical Specialist
Jan 2021 – Oct 2021
Joined the R&D team as the bridge between research and engineering — translating business needs into technical decisions and research outputs into shipped product. Built the foundational feedback loop for the IDP solution: data collection, ingestion, preprocessing, stratification, training, evaluation, deployment, monitoring. Unglamorous work, but the kind that makes everything else possible. Also set the Python architecture standards and secure SDLC practices that the engineering org still follows.
What I Work With

"Not every tool here was used in an enterprise production system — some came through self-learning, POCs, or deliberate exploration. Breadth matters; so does being honest about depth."

Skills & Technologies — Interactive Map
Open full screen ↗
What I Work With — Skills Map →
Interests & Passions
💻
AI & Architecture
System Architecture AI Philosophy GenAI & LLMs Cloud Infrastructure Tech Trade-offs
🎯
Product & Vision
Product Strategy Design Thinking Visionary Products Out-of-box Ideas
🌍
Travel & Family
World Travel Cultural Immersion Family Time
🤝
Community & People
Team Building Mentorship Knowledge Sharing Casual Chit-chat
🎭
Philosophy & Culture
Deep Philosophy Profound Quotes Anime & Podcasts Meme Culture