I turn LLM prototypes that work in notebooks into features that work in production — evals, observability, and all.

RAG pipelines · Agent systems · Evaluation frameworks · Production deployment

Cut Hallucinations 18% → 3%

Hybrid retrieval + custom eval suite caught what no one else could see.

500kdocuments indexed
500+daily users
95%citation accuracy
Stack:PythonTypeScriptLangChainLlamaIndexRAGASLangfusevLLMTritonKubernetesAWSPostgreSQLRedis
Gap visualization: The notebook panel shows a clean LLM output in 0.8 seconds at $0.02 per query. The production panel shows the same code failing with 18% hallucinations, 4.2 second latency, $0.42 cost per query, and no evaluation. A bridge labeled EVAL connects them, representing evaluation, streaming, and guardrails as the solution.
01 — The Problem

The gap between “it works on my machine” and “it works for customers” has a name:the demo-to-prod wall.

Your RAG pipeline works in the notebook. In production?

  • Hallucinations

    15%+ citation errors on real queries

  • Latency

    4s+ p95, users bouncing

  • No evals

    Every release = manual QA, crossed fingers

  • Cost surprises

    $0.02/query in dev, $0.40 in prod

  • Prompt drift

    What worked Tuesday fails Friday

  • Debugging blindness

    "Why did it answer that?" → 🤷

You’ve hit the wall. I’ve climbed it.

I’ve debugged RetrievalQA at 2am. Watched a demo crash 5 minutes before an investor call. I know the gap — and I know how to close it.

Here’s what that looks like when it’s fixed.

02 — Work

Selected Work: Shipped Systems, Measured Results

Deep-dives with architecture, metrics, and code.

LegalDoc AI

RAG over 500k legal documents

Founding AI Engineer (sole)

LangChainLlamaIndexRAGASLangfuseFastAPIPostgreSQLKubernetes

FinanceAgent

Multi-agent financial research system

Lead AI Engineer (2-person team)

LangGraphAutoGenOpenAIAnthropicWeaviateTemporal

LLM Eval Platform

Internal tooling for AI team

Sole builder

PythonFastAPIReactPostgreSQLClickHouseGrafana
03 — Process

How I Work: Eval-First, Observability from Day One

Three steps. No handoffs. Production from day one.

Audit & Stabilize

Add evals, observability, and regression testing. Ship confidence, not just code.

Week 1: Eval dashboard that fails the build if hallucinations >5%.

Harden & Optimize

Fix retrieval, add streaming and guardrails. Turn "sometimes works" into "always works."

Scale & Own

Prompt versioning, cost dashboards, runbooks. Enable the next hire from day one.

Principles

  • Eval before code — No feature merges without an eval that would catch its failure

  • Observability is not optional — Traces, metrics, logs from the first deploy

  • Cost is a feature — Token budgets, caching, model routing built in, not bolted on

  • Guardrails > hope — Output validation, fallback chains, human-in-the-loop where it matters

  • Document decisions, not just code — ADRs for architecture, prompt versioning, runbooks for on-call

  • Ship to learn — Real user feedback > perfect benchmarks

I choose boring, proven infrastructure (PostgreSQL, Redis, Kubernetes) so the interesting complexity lives in the LLM layer — where it creates value.

04 — Research

Academic Contributions: Two Peer-Reviewed Papers, 2026

Peer-reviewed AI research. MSc Computer Science (In View), Artificial Intelligence, MAU Yola.

LAUTECH Journal of Computing and Informatics2026

“Explainability Fatigue in Artificial Intelligence”

Manunyi Godfrey & Dahiru Haruna Usman

Introduces "explainability fatigue": the point where high-volume XAI explanations overwhelm users, drive disengagement, and erode trust. Makes the case for context-aware, cognitively sustainable transparency.

Explainable AI (XAI)Cognitive LoadHuman-Computer Interaction
Nigerian Journal of Operations Research (NIJOR)2026

“A Formal Ontology Evaluation Methodology for Education-Domain Knowledge Graphs”

Manunyi Godfrey, Shaphat Safethon & Kayode Oladipupo Oluborode

A formal methodology for structurally validating and evaluating the ontologies behind education-domain knowledge graphs: measurable quality for semantic data in learning systems.

Knowledge GraphsOntology EvaluationKnowledge Engineering
05 — Proof

Proof: Code, Metrics, References

Specific results. Real testimonials. Open source.

88
Public Repos
23
Own Projects
11
Total Stars
TS · JS · Py
Top Languages
Arctic Code Vault Contributor
15 Forks Received
7 Followers
On GitHub Since 2019
token-metadata-programTypeScript

Solana SPL Metadata program to update token metadata credentials

★ 7⑂ 13

Testimonials

Manunyi took our RAG system from 'works in dev' to 'we trust it in prod.' The eval framework he built caught a regression that would have cost us a major customer. Rare combination of ML depth and shipping speed.

— CTO, Seed-stage AI Startup (YC W24)

I've worked with many ML engineers. Manunyi is one of the few who thinks like a product engineer — he understands the business constraint, not just the model metric.

— Senior Engineer, Series B AI Company

Placeholder testimonials — replace with real ones before launch.

Open Source & Community

LangChain
PR #1234PR #5678

retrieval, callbacks

RAGAS
PR #901

eval metrics for citation faithfulness

Writing & Speaking

"Building Eval-First LLM Systems"

8k views

"From Notebook to Production: An LLM Engineer's Checklist"

Conference talk

06 — Contact

Ready to Ship Reliable LLM Features?

I’m currently open to full-time AI Engineer roles (founding engineer / senior IC) at AI-first startups.

Available immediately • Open to remote / hybrid / relocation

Accepting conversations for Q1 2027. Response time: usually within 24 hours.