Naya Labs
ShippedForward-deployed engineering on 3–6-month client engagements across the US, UK, Canada, Kenya, Ghana, Nigeria and Pakistan, including OmniArsenal: a US defence contractor's Go CI/CD platform of around eight services with a React front end.
- Go
- React
- Docker
- Kubernetes
Built OmniArsenal's ingestion pipeline and monitoring infrastructure, and traced a month-old production defect breaking real-time rendering to an incorrect browser-storage reference.
What was broken.
Forward-deployed engineering means joining a client's codebase for three to six months and being useful inside the first week, which over this period meant teams in the US, UK, Canada, Kenya, Ghana, Nigeria and Pakistan. On OmniArsenal — a US defence contractor's CI/CD platform of around eight Go services behind a React front end — the work was the parts nobody owned: getting data in reliably, and being able to see what the platform was doing.
How it is wired.
Around eight Go services with a React front end. I built the ingestion pipeline feeding them and the monitoring infrastructure around them, so the platform's behaviour could be read directly rather than inferred from its output.
What I shipped.
- OmniArsenal's ingestion pipeline
- Monitoring infrastructure across its services
- Traced a month-old production defect breaking real-time rendering to an incorrect browser-storage reference
- Embedded with client teams on 3–6-month engagements across seven countries
Why these choices.
That rendering defect had been looked at as a rendering problem for a month. It was a storage-key problem. Symptom and cause sat in different layers, which is the whole argument for monitoring you can read: without it, the search space is the entire stack.