GrantSpider
Founding Engineer, multi agent RAG platform
production
A grant intelligence platform: it catalogues funding opportunities, matches them to the right researchers,
and drafts citation backed proposals. I owned technical direction for the agent and retrieval layer, and
stayed hands on through production code, infrastructure, and the operator facing UI.
LangGraphRAGPythonFastAPI
Postgres + pgvectorReactTypeScriptAWSTerraformDocker
▶Technical detail
- Designed the multi agent architecture: a coordinating layer that delegates to specialised sub agents for discovery, matching, evidence gathering, and drafting, with a scheduler for long running and proactive tasks.
- Built the matching engine that scores researchers against upcoming calls using open bibliographic data, topic overlap, and recent publication history, running as asynchronous jobs rather than blocking the request path.
- Added an LLM as a judge relevance and evidence check inside the retrieval loop, so low quality matches are caught before they reach a user rather than after.
- Implemented guardrails against hallucination and prompt injection, plus a structured evaluation harness that turned "the output feels worse" into a number the team could act on.
- Built operator facing React dashboards for review, correction, and human in the loop intervention on anything the agents were not confident about.
- Owned the ingestion and promotion pipeline that moves catalogued opportunities through development, staging, and production on scheduled workers, including the root cause work when a promotion silently exported the wrong database.
Why it was hard: retrieval quality and agent autonomy pull against each other. More autonomy means more surface area for a confident wrong answer, so most of the engineering went into evaluation and the human in the loop path, not the prompts.
NASA Ames Research Center
AI Engineer (Research), via San Jose State University
2024
Transformer based decision support for airspace operations, running as production services under
strict latency and reliability SLOs. I led the agent architecture and technical direction while staying
hands on across design, code, and deployment.
PyTorchTransformersPythonKubernetesREST APIsCI/CDobservability
▶Technical detail
- Shipped Python microservices exposing REST APIs consumed by operator applications and downstream systems, orchestrating multi step reasoning agents over heterogeneous aerospace datasets.
- Deployed on Kubernetes with blue/green rollouts and automated rollback, because a bad model version reaching operators is not an acceptable failure mode.
- Instrumented end to end observability with structured logs, metrics, and tracing, then used it to cut mean time to detection and recovery on real incidents.
- Debugged production failures spanning API integrations, data ingestion, inference, agent orchestration, and downstream consumers, which in practice meant owning the whole path rather than one layer of it.
BagsID
Machine Learning Engineer (freelance)
2023 to 2024
Distributed Vision Transformer inference serving live customer traffic. I owned capacity planning,
latency, and cost, and got 40% more throughput out of less infrastructure.
Vision TransformersPyTorchDockerKubernetesCI/CD
▶Technical detail
- Designed batching, caching, and resource aware deployment patterns that raised throughput by 40% while cutting the infrastructure bill.
- Built CI/CD covering training, evaluation, and deployment so model changes shipped on the same rails as code changes.
- Resolved production incidents across the data, model, and infrastructure layers, including the ones that only appear under real traffic shapes.
Atradius
Senior Quantitative Analyst
2022 to 2023
High throughput ML pipelines inside a regulated credit insurance environment, processing
billions of records on Linux based distributed systems where a silent data error is a compliance problem.
distributed pipelinesPythonSQLLinuxdrift detection
▶Technical detail
- Redesigned the data architecture for scalability, fault tolerance, and recoverability under partial system failure, so a single bad node stopped meaning a full rerun.
- Implemented automated monitoring, validation, and drift detection, catching model and data degradation before it reached a decision.
- Investigated production failures through structured root cause analysis, in an environment where "we restarted it" is not an acceptable postmortem.
Text4Quote
Co-founder and CTO
venture
An end to end LangGraph agent handling multi turn conversation, tool calling, persistent memory,
and structured outputs. I owned architecture, production code, and every integration.
LangGraphFastAPIPythonstructured outputspersistent state
▶Technical detail
- Modelled the conversation as an explicit graph rather than a prompt chain, which made the failure modes inspectable and the flow testable.
- Backed the agent with FastAPI and persistent state so a dropped session resumes instead of restarting.
- Founder side ownership too: scoping, technical direction, and the calls about what not to build.
GrantForge
Personal build, synthetic SaaS twin and DR rehearsal harness
2026
A runnable, fully synthetic reference implementation of an entire SaaS company stack, built so that
clean room rebuilds and restore drills can be rehearsed without ever touching a production system.
disaster recoveryNode.jsPostgresRedisDocker ComposeRBAC
▶Technical detail
- Multi tenant core API with role based access control and an audit log, backed by Postgres with migrations and a zero dependency JSON fallback so the twin runs with nothing but Node installed.
- Synthetic data platform generating tenants, users, opportunities, applications, CRM records, and campaigns from a seed, with a verifier that fails the build on any real PII signal.
- Snapshot and restore tooling plus a written DR runbook, so a recovery drill is a command rather than a fire drill.
- A white label configuration engine that rebuilds the same codebase under a different brand, used to test how much of a stack is genuinely portable.
- Binds to localhost only and reaches no external system by design. Every person, org, and dollar in it is fictional.
Why build it: most teams have a disaster recovery plan and no evidence it works. This is the evidence, produced without risking anything real.
Sphinx
LLM compliance extraction
project
A hybrid extraction pipeline that pairs deterministic rules with an LLM, so the parts that must be exact
stay exact and the language model handles only what rules cannot.
hybrid rules + LLMPythonCI/CD validationstructured eval
▶Technical detail
- Rules first, model second: anything expressible deterministically stays deterministic, which keeps the compliance surface auditable.
- Automated CI/CD validation and structured evaluation with end to end test coverage, so a prompt change cannot quietly regress extraction quality.
ESA, OHB, ATG Europe
AI Consultant
2020 to 2021
Telemetry pipelines and anomaly detection for mission critical satellite operations, on Linux
infrastructure under strict reliability SLAs and formal change control.
anomaly detectiontelemetryPythonLinuxSLA driven ops
▶Technical detail
- Built detection over live spacecraft telemetry, where a false negative is a missed anomaly on an asset nobody can go and fix.
- Worked inside structured engineering process: change management, validation, and continuous testing as a requirement rather than a preference.
Supplai
ML Infrastructure Engineer
2022
Kubernetes based ML deployment stacks with Terraform and GitHub Actions, exposing real time
prediction APIs over multimodal inputs.
KubernetesTerraformGitHub Actionscontract testing
▶Technical detail
- Containerised microservices with clear service boundaries, contract testing, and explicit performance budgets.
- Automated retraining and evaluation loops wired into upstream data sources and downstream serving, so the system improved without a human in the loop for every cycle.
SITAEL
AIT Engineer, assembly, integration and test
2018 to 2020
Linux based automation and orchestration tooling for distributed hardware integration, plus
system level validation and structured failure analysis across satellite programs.
test automationLinuxPythonfailure analysis
▶Technical detail
- Where the engineering discipline came from: hardware in the loop, no undo button, and every anomaly written up properly.