📍 Bangalore, India | 🤖 Agentic builder | 🚀 Napplied Founder
Quick Profile Contents ...
┌──────────────┬────────────────┬───────────────────────────────────┐
│ Startup... │ Open Source... │ Multi Agent Orchestrations │
│ Napplied AI │ Coming soon │ Build with me │
└──────────────┴────────────────┴───────────────────────────────────┘
|
Napplied is an Agentic AI platform reimagining how talent meets opportunity — powered by relevance, ontology, and deep contextual intelligence. Not your average HR Tech AI. Not even close. |
Right Brain — For Recruiters
Left Brain — For Candidates
The Engine
|
"Candidate search agents go deep — contextually evaluating the right candidates for the right job"
┌──────────────────────────────────────────────────────────────────────────────┐
│ AI-Powered Candidate Search [ Parameter Settings ] [ Relevancy Agents ] │
│ Searching best candidates for: AI Engineer │
├──────────────┬────────────────┬────────────────────┬─────────────────────────┤
│ EVALUATED │ ANALYZED │ WITH SCORES │ RETURNED │
│ 75 │ 25 │ 25 │ 25 │
├──────────────┴────────────────┴────────────────────┴─────────────────────────┤
│ Top 25 AI-Ranked Candidates │
│ │
│ #1 ██ 75 AI Engineer @ Middleware · Agentic AI, Apache Airflow · Ahm... │
│ #2 ██ 71 AI Consultant · Data Science, LLMs, Python · Bangalore... │
│ #3 ██ 71 ML Engineer · Conversational AI · Bangalore Urban... │
│ #4 ██ 68 Architect of Autonomous AI · Multi-Agent Systems · Jaipur... │
│ #5 ██ 66 Senior AI Engineer · Bangalore... │
└──────────────────────────────────────────────────────────────────────────────┘
What makes it different:
- 🧬 Relevancy + Context-driven — ranked by semantic understanding, not keyword count
- 🤖 Deep Multi-Agent orchestration — specialized agents evaluate each candidate in concert
- 🕸️ Skill ontology analysis — understands relationships between skills, not just matches
- 📊 Context-aware scoring — role context, domain depth, team fit all factored in
🤝 Work With Me Linkedin — AI Engineers & Agentic Builders
╔═══════════════════════════════════════════════════════════════════════╗
║ ║
║ I'm looking for engineers who feel personally offended by: ║
║ ║
║ 😤 RAG pipelines that retrieve the wrong context ║
║ 😤 Agents that hallucinate instead of reason ║
║ 😤 "AI-powered" features that are just regex + LLM wrappers ║
║ 😤 Ontologies maintained in Excel by someone named Dave ║
║ ║
║ If you nodded at any of the above — let's build together. ║
║ ║
╚═══════════════════════════════════════════════════════════════════════╝
|
🔬 You build in...
|
⚡ You believe...
|
🎯 You want to...
|
💡 When you reach out — tell me one thing you've built with agents that surprised even you.
░▒▓████████▓▒░▒▓█████████▓▒░░▒▓██████▓▒░░▒▓████████▓▒░▒▓███████▓▒░
░▒▓█▓▒░▒▓█▓▒░ ░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░ ░▒▓█▓▒░░▒▓█▓▒░
░▒▓██▓▒░░▒▓█▓▒░ ░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░ ░▒▓█▓▒░░▒▓█▓▒░
░▒▓██▓▒░ ░▒▓██████▓▒░ ░▒▓████████▓▒░▒▓██████▓▒░ ░▒▓███████▓▒░
░▒▓██▓▒░ ░▒▓█▓▒░ ░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░ ░▒▓█▓▒░░▒▓█▓▒░
░▒▓█▓▒░ ░▒▓█▓▒░ ░▒▓█▓▒░░▒▓█▓▒░▒▓█▓▒░ ░▒▓█▓▒░░▒▓█▓▒░
░▒▓████████▓▒░▒▓████████▓▒░▒▓█▓▒░░▒▓█▓▒░▒▓████████▓▒░▒▓█▓▒░░▒▓█▓▒░
Two projects so cursed they need a disclaimer before launch.
┌─────────────────────────────────────────────────────────────────────┐
│ │
│ THREE FRAMEWORKS. ONE COHERENT INTELLIGENCE STACK. │
│ │
│ [Multi-Agent] ──► [Relevancy+ Ont] ──► [Context] ──► Right Talent │
│ │
└─────────────────────────────────────────────────────────────────────┘
The insight from building Napplied: When you run a candidate search, you don't need one smart agent — you need a team of specialized agents that reason about delegation, context, and handoffs. We built that. Now we're open-sourcing the framework.
┌──────────────────────────────────────────────────────────────┐
│ ORCHESTRATION LAYER │
│ │
│ ┌──────────┐ ┌───────────┐ ┌────────────────────────┐ │
│ │ Routing │──▶│ Specialist│──▶│ Episodic Memory Store │ │
│ │ Agent │ │ Agents │ │ (per-agent + shared) │ │
│ └──────────┘ └───────────┘ └────────────────────────┘ │
│ │ │ │ │
│ └───────────────┴────────────────────┘ │
│ │ │
│ ┌──────────▼──────────┐ │
│ │ Relevance Evaluator │ ◀── Ontology Graph │
│ └─────────────────────┘ │
└──────────────────────────────────────────────────────────────┘
Design bets:
- 🎯 Relevance-first routing — agents reason about whether to act, not just how
- 🔗 Composable primitives — not a framework you fight, one you extend
- 🧠 Shared + episodic memory — agents remember what matters, forget what doesn't
- ⚡ Async-native — synchronous agent orchestration is a distributed systems crime
| Principle | What It Means in Practice |
|---|---|
| 🧬 Relevance over volume | Don't retrieve everything. Retrieve the right thing, ranked by domain relevancy + ontology |
| 🕸️ Ontology is infrastructure | Skill graphs, concept maps, and domain taxonomies are first-class citizens |
| 🤖 Agents that reason about delegation | Not just "which agent does this task" — but "should any agent do this at all" |
| 🎯 Context is a product | The context window is engineered, not stuffed |
| ⚡ Ship, then refine | A v0.1 that runs beats a v1.0 in Notion |
╔══════════════════════════════════════════════════════╗
║ ║
║ ᶻ𝗓 Napplied — Talent Search & Job Search Agents ║
║ ║
║ Building where agents meet relevancy meets ║
║ context meets the real world. ║
║ ║
║ If that sounds like your kind of problem — ║
║ come find me. ║
║ ║
╚══════════════════════════════════════════════════════╝
| 🌐 | napplied.com | Main Platform |
|---|---|---|
| 💼 | Md Mahabub Alam | |
| 📧 | [email protected] | Direct Email |

