CV

Seven years of client-side delivery, end to end. I scope with the customer's engineers, architect it, build it, deploy into their environment, and own it after go-live.

Download the PDF Two pages. Same facts, laid out for print.

Selected delivery

Most of this is client work under NDA, so each entry describes architecture and outcomes rather than showing source. Where there is a full write-up, it starts with what went wrong.

  1. Tool-using agent operating on live client systems

    2025

    Croncore internal, daily production use

    One tool surface, two runtimes: the same tools run against the Anthropic Messages API directly or through the Claude Agent SDK. It triages pull requests, tracks developer tasks and drafts client mail. Every side effect waits in a pending_actions row for a human, and each run is scoped to one project_id so context cannot leak between clients.

    Read the case study
  2. Bilingual education platform, live with Québec school boards

    2024 to present

    Co-led delivery, architecture owner for the next stage

    EN/FR role-based platform in use with school boards. An EN/FR-parity Playwright suite means a regression in one language cannot ship because the other passed. Rewriting the generation prompts and the text handling cut text-render errors by roughly 80% with no model change, no added cost and no added latency. I now own the architecture for an orchestration layer where content, assessment and analytics agents read and write one shared learner record.

  3. Multi-provider LLM platform under load

    2023 to 2025

    Shurq, UK adtech startup

    Tiered pricing with automatic provider fallback, self-hosted Ollama through to OpenAI, so a provider outage degraded cost and latency instead of taking the feature down. Stress-tested to 200+ concurrent users before release, with drift and latency dashboards handed to the team so degradation shows on a graph before a customer reports it.

  4. CRM-integrated agent under US and Canadian compliance rules

    2025

    US payment services, Canadian SEO SaaS

    Full Pipedrive integration as agent-invoked actions, with the compliance layers built in-house: timezone-aware dialling windows, DNC scrubbing, mid-call opt-out detection, verbal-consent logging and CASL unsubscribe handling. The failure that took longest to find was two layers below where everyone was looking.

    Read the case study
  5. Retrieval agent that quotes prices from the client's own data

    2025

    Automotive, EU

    A Django prototype taken to a production retrieval pipeline over pgvector with a query rewriter, and pricing synced live from the client's own sheets. A price change on their side lands without a redeploy, and no quoted figure comes from model memory.

  6. Speech service into a legacy PBX

    2024

    Language with no commercial vendor

    Built and operated the serving stack: a self-hosted FastAPI service running two off-the-shelf engines behind one interface with fallback between them, producing audio that matched the client's existing Asterisk/FreePBX contract so nothing on the telephony side had to change.

Experience

Integrated with

Each one wired up and debugged in production, not read about.

Twilio · Asterisk/FreePBX · Deepgram · ElevenLabs · Pipedrive · ClickUp · GitHub · Gmail · Google Sheets · Google Places · Stripe

Skills

Languages
Python · TypeScript/JavaScript · Node.js · SQL
Agentic & LLM
tool-using agents · MCP tool servers · Anthropic tool use · OpenAI function calling · schema-validated structured outputs · RAG · provider fallback · human-in-the-loop approval gates · prompt-injection containment · eval design and calibration
Backend
FastAPI · Django/DRF · Next.js · PostgreSQL · pgvector · Redis · BigQuery · Docker · async pipelines · rate limiting and backoff
Cloud & ops
AWS · GCP · Azure · Vercel · Render · Cloudflare · GitHub Actions CI/CD · Prometheus/Grafana

Education and availability

BSc Software Engineering, Pak-Austria Fachhochschule, Institute of Applied Sciences and Technology, Pakistan.

Remote, with working hours overlapping the EU in full and the US East coast by four hours. Set up to work remotely long term, and equally open to relocation to the US, EU or UK where a role calls for it. Available for customer travel and on-site work. Open as an employee, or on contract through my consultancy.

Hiring for a forward-deployed or solutions role? Send me a real integration problem you are dealing with and I will tell you how I would approach it. That is faster than a screening call for both of us.

sparli@croncore.com