The team
The research and infrastructure engineers behind SquadProxy
A small team with ML training, RAG infrastructure, proxy network operations, and corpus engineering backgrounds. The blog is written by the people doing the work; this page describes who they are.
Research engineer — Common Crawl + open data
Elena Novak
Research engineer at SquadProxy focused on Common Crawl sampling, open-web corpus construction, and the provenance chains that make research-grade training data defensible.
Focus
- Common Crawl sampling and bias
- Open-web dataset construction
- Provenance documentation for training data
Research engineer — evaluation
Hamza Rahim
Research engineer at SquadProxy focused on LLM evaluation, regional bias measurement, and specifically the comparative benchmarks that test whether model APIs behave consistently across origin regions.
Focus
- Multi-origin LLM evaluation
- Regional bias measurement
- Safety and red-team methodology
Research engineer — corpus engineering
Imogen Reyes
Research engineer at SquadProxy focused on training-corpus engineering — deduplication, tokenisation-aware sampling, corpus-level bias measurement.
Focus
- SquadProxy deduplication and quality filtering
- Tokenization-aware sampling
- Common Crawl post-processing
Infrastructure engineer — gateway + pool
Nathan Brecher
Infrastructure engineer at SquadProxy focused on the gateway architecture, per-class routing, exit identity capture, and the specific plumbing behind the header-based proxy pattern.
Focus
- Gateway architecture and class routing
- HuggingFace / Common Crawl / arXiv specific tooling
- AI agent infrastructure
Research engineer — methodology
Reeya Patel
Research engineer at SquadProxy focused on LLM evaluation methodology, RAG pipeline infrastructure, and the statistical validity of multi-origin evaluation studies.
Focus
- RAG ingestion and retrieval consistency
- LLM evaluation reproducibility
- Multilingual benchmark methodology
Ship on a proxy network you can actually call your ops team about
Real ASNs, real edge capacity, and an engineer who answers your Slack the first time.