Embeddings: Representation Layer of AI
Embeddings are the layer under search, ads ranking, recommendation and RAG. How they are built, how you compare them, and how you search a billion of them fast.
Sr. ML Engineer at Atlassian | Ex-Meta | PhD
RL & multi-Agentic AI for Confluence/Jira Search. On the Central AI team, I’m building and improving SMART Answer generation using RL-based fine-tuned LLMs and multi-Agent AI architecture. Previously at Meta on Ads Ranking, fine-tuning LLaMA 3 for large-scale suggestive ad generation.
I write about RecSys, agentic AI, RL fine-tuning, and what actually ships at scale.
Embeddings are the layer under search, ads ranking, recommendation and RAG. How they are built, how you compare them, and how you search a billion of them fast.
Each generation of NLP tech solved the previous one’s problem and created a new one. This is that chain, from counting words to modern transformer variants, with what each choice costs you.
Which model for which problem, what each one is really doing under the hood, and where each breaks. Written for engineers shipping models and sitting interviews, not for a syllabus.
A practical map of ML metrics across four layers (offline, online, infra, business) and every model type from logistic regression to LLM agents, with the failure modes that make a good-looking number meaningless.
How models actually get trained: the optimizer family tree, why Adam won and where it loses, the schedule and warmup decisions that matter more than the optimizer choice, and the practical machinery (clipping, accumulation, checkpointing, sharded states) that shows up in real training runs.
Which activation to use where, why ReLU replaced sigmoid, why transformers moved to GELU and SwiGLU, and the failure modes (dead units, saturation, non-zero-centered outputs) interviewers ask you to diagnose.
A scannable reference for ML interviews: which loss to use for which task, why it works, when it breaks, the PyTorch gotchas that cause real bugs, and how to answer the question every interviewer asks.
Python syntax and DSA patterns for coding interviews, condensed into a single reference: core syntax on page 1, the coding patterns worth memorizing on page 2.
The missing layer between observability and benchmarks. Over the last year, Agentic AI has exploded. OpenAI has agents. Anthropic has agents. Google DeepMind has agents. Every startup suddenly has a multi-agent architecture diagram. And if you look closely, something interesting has happened. The industry solved observability. The industry largely solved benchmarks. Yet somehow, we still cannot answer a deceptively simple question: Was this agent actually good? Not “did it finish.” ...
Executive Summary Agentic AI is entering enterprise deployment faster than its evaluation infrastructure is maturing. Most teams can now observe traces and benchmark outcomes, but they still cannot reliably grade how agents behave in production across coordination quality, trajectory correctness, and safety compliance. That missing layer is becoming a strategic bottleneck for executive teams deciding where to place platform bets, set governance controls, and scale high-autonomy workflows with confidence. As of June 2026, the market has largely solved two layers: observability (OpenTelemetry GenAI conventions, AgentOps, OWASP AOS) and benchmark comparison (HAL, GAIA, SWE-bench). The unresolved layer sits between them: an open, framework-agnostic evaluation protocol that takes any OTel-compatible trace and scores agent behavior end-to-end. Without this layer, enterprises can measure activity and final outcomes, but still miss the process-level failures that drive hidden risk, cost overruns, and policy violations in real deployments. That gap is not only a research problem; it is now a platform opportunity with direct implications for deployment risk, governance, and competitive advantage. ...