Shren Patel

AI agent orchestration engineer · Canada, remote (EST/PST)

I build multi-agent systems that do real work — and stop for a human before anything irreversible.

Open to Staff AI, AI Platform, AI Architect and Forward-Deployed roles · patel.shrenil@gmail.com

Proof

3

What I’ve shipped

CentrOS

In productionsince Feb 2026

An orchestration platform that turns messy business workflows into agent systems — agents draft guest replies, process refunds and vendor invoices, and an owner approves anything irreversible.

router → executor → adversary → verifier → owner inbox

23-unit hospitality operation · 3,980+ tests on main · 4 vendor primitives → 1 governed layer

In progressA 60–90s walkthrough video: a ticket arrives, risk is classified, the owner reviews, and the tool fires with an audit trail. Until then, try the live demo.

Read the case study

AXED

IP deal2018 – 2020

A WEBTOON Original I created solo and shipped twice weekly, then closed an IP rights deal with Wattpad WEBTOON Studios for a book and a 2-season animated television adaptation.

40M+ reads · 492K+ subscribers · 2M+ monthly views at peak

Read the case study

Also

4

Experience

Ten-plus years — Coursera, Faire, D2L, WEBTOON, now CentrOS. Each row opens.

Education

  • University of WaterlooBachelor of Software Engineering (BSE), Computer Software EngineeringWaterloo, ON · 2012 – 2018

Skills

Agent systems
  • Multi-agent workflow design & task decomposition
  • Tool/function calling, structured outputs, schema-validated arguments
  • Stateful workflow orchestration, checkpointing, crash recovery, replay
  • Human-in-the-loop approvals, escalation paths, audit trails, governance
  • RAG, retrieval pipelines, embeddings, context windows, prompt management
  • Agent evaluation, tracing, observability, latency & token-cost monitoring
  • MCP servers, webhooks, OAuth-scoped tool access, third-party API integrations
  • Router · executor · adversary · verifier patterns; confidence-gated handoff
  • POCs, demos, eval-gated rollout & production hardening for business workflows
LLM practice
LLMs since Nov 2022 · tool-calling since Jun 2023 · multi-agent, RAG and evals since 2024 · MCP since late 2024
Languages
Python 3 · JavaScript · TypeScript · C / C++ · HTML5 · CSS
Data & cloud
PostgreSQL · pgvector · OpenSearch · GCP (BigQuery, Cloud Run, Vertex AI) · AWS (Lambda, Step Functions, DynamoDB, SQS, EventBridge) · Kubernetes · Docker
Full toolboxlanguages, frameworks, databases, cloud, dev tools, integrations
Languages, familiar
Objective-C · C# · VB / VB.Net · Arduino · Processing · MIPS / ARM assembly · uC++ · GML
Frameworks
React + React Native · MobX + Redux · Jest + Storybook · Node.js + Express · FastAPI + Django + SQLAlchemy · TensorFlow + OpenCV · Hugging Face · Socket.IO + WebGL · Bootstrap + SASS / LESS · Selenium + Cocos2d-x · jQuery + Angular · Android SDK · iOS SDK · Windows SDK · Mac OSX SDK · Cocoa Frameworks
Databases
PostgreSQL · MySQL · MongoDB · SQLite · Vector DBs: pgvector · OpenSearch · FAISS
Cloud
  • GCP: BigQuery · Cloud Functions · Cloud Run · Vertex AI
  • AWS: Lambda · Step Functions · DynamoDB · S3 · SQS · EventBridge · API Gateway
  • Kubernetes · Docker · infrastructure-as-code
  • Serverless architectures · event-driven pipelines
  • Heroku · CI/CD deployment
Dev tools
Git + Git-SVN · GitHub + Bitbucket · JIRA + Trello · Unix Terminal · Apache Server · MKS Integrity · RegEx · VSCode · PyCharm · XCode · Eclipse · Netbeans · Sublime Text
Integrations & ops
REST APIs · webhooks · OAuth · Slack · email · calendar · CRM-style workflows · Booking & hospitality / accommodations systems · PDF / document parsing pipelines · Git · CI · Unix · AWS · Heroku
Working style
Forward-deployed mindset: gather requirements, ship POCs, iterate with stakeholders · Strong written communication for runbooks, eval reports & customer-facing demos · Background in high-scale web, mobile, and workflow automation since 2013

Roles I fit

8 roles

Staff AI Engineer · Agent Runtime · AI Platform · AI Architect · Workflow and GTM automation · Agent integrations · Forward-Deployed · Serverless production AI. What I bring to all of them:

  1. Durable runtimesCrash-resumable execution on PostgreSQL: checkpoints, retries, rollback and stop-ship, with an explicit failure taxonomy per stage.Seen in CentrOS: the pipeline
  2. Human approval by designRisk tiers and policy lanes as access boundaries, approval before any side effect, and audit trails kept as state.Seen in CentrOS: the owner inbox
  3. Evals and observabilityRegression-gated eval harnesses and traces over cost, latency and failure modes, tested in CI on every merge.Seen in CentrOS: the adversary
  4. Grounded retrievalRAG with ranking, freshness and source attribution, plus token-cost discipline: model routing, prompt design, caching.
  5. Tool and integration contractsTyped, scoped, idempotent tool calls with audit logs; router → executor patterns; the same primitives across LangGraph, Temporal and MCP.Seen in CentrOS: versus the parts
  6. Forward-deployed deliveryCustomer workflow → production agent: process mapping, gated POC → production, and domain experts at the approval step.Seen in CentrOS: the 23-unit deployment

What I bring, role by role

8 roles

  • Staff AI EngineerOrchestration-layer thinking for the team: durable multi-step execution, runtime state, traceability and retrieval quality.
    • Stateful multi-agent workflows with typed state contracts
    • Non-deterministic eval harnesses with regression gates
    • RAG pipelines with retrieval ranking and freshness controls
    • HITL approval surfaces with audit trails
    • LangFuse-style observability over trace + cost + failure modes
  • Agent RuntimeThe layer beneath agent behaviour most teams underinvest in — state, execution, recovery and production ownership.
    • Crash-resumable execution with durable state on PostgreSQL
    • Gate runners: retries, checkpoints, rollback, stop-ship
    • Scoped tool-execution sandboxing with versioned deploys
    • Explicit failure taxonomy per stage — no silent corruption
    • Streaming LLM responses with cancellation and timeout policies
  • AI PlatformThe capability layer that lets multiple teams deploy AI safely without bespoke setup: connectors, execution patterns, governance, tooling.
    • Tool registries with typed schemas and scoped permissions
    • Policy lanes (auto / confirm / careful) as an access-boundary model
    • Audit trails as first-class state, not afterthought logging
    • Self-service workflow templates with opinionated guardrails
    • CI-backed gate tests validating platform changes per merge
  • AI ArchitectAmbiguous business processes translated into cloud-native AI systems with tool calling, retrieval, state management and approval flows.
    • Reference architectures for agent workflows — blueprints, not one-offs
    • Framework-parity thinking: same primitives across LangGraph / Temporal / MCP
    • Risk-tiered governance language that stakeholders can use
    • Multi-vertical domain experience (hospitality, accommodations, ops)
    • Production engineering standards: CI / logging / monitoring / rollback
  • Workflow / GTM automationAgent systems as operational infrastructure, moving work across Slack, CRMs, email, calendars and internal APIs.
    • Router → executor patterns with specialized agents and fallbacks
    • MCP / tool-registry contracts with scoped permissions
    • RAG pipelines tuned for freshness and source attribution
    • Self-service workflow templates with guardrailed config
    • Narrow action scopes; approvals before any side effect
  • Agent integrationsThe boundary where agent systems become real products: integrations, context continuity and reliable handoff between automation and humans.
    • Evidence timelines preserved across AI → human handoff
    • Context-rich session transfer with no lost history
    • Audit-logged tool calls: idempotency, retries, rollback per integration
    • Explicit session lifecycle phases with state ownership transitions
    • Observability over handoff statistics and API failure patterns
  • Forward-DeployedCustomer workflow → production agent: POCs, integrations and live deployments, paired with domain experts and built under compliance constraints.
    • Active production deployment: 23-unit hospitality vertical under direct management
    • POC → prod path through gated expansion, not big-bang launches
    • HITL demo surfaces tailored for stakeholder reviews
    • Domain-expert pairing (legal / accounting / ops) at confirmation gates
    • Domain-specific controls layered onto a shared workflow shell
  • Serverless production AIPython/Node function calling, multi-agent orchestration and vector RAG on serverless AWS (Lambda · Step Functions · DynamoDB · SQS · EventBridge), with LangFuse traces and synthetic testing.
    • Contract / gate state machines (Step Functions–style)
    • Tool registries with typed schemas and idempotent activities
    • Vector retrieval and streaming-response patterns
    • CI-backed contract/gate test suites running on main
    • Token-cost discipline: model routing, prompt design, caching

Contact

Canada remote · NA-friendly · EST/PST. Happy to walk through CentrOS architecture, framework parity, or a tailored eval and observability slice for your domain.

Contact

Shren PatelAI agent orchestration engineer

Canada, remote · EST/PST.

Solid draws a plain colour instead of the sky, so your device does less. Both choices are saved in this browser only.

No cookies, no tracking.