CHARLES JONES
Live portfolio: junelifeinsurance.com · callcharlie.co · callcharlie.io
AI Platform Engineer — AI-Directed Development
Solo builder-operator engineering agentic AI systems on Google Cloud Platform (GCP): multi-agent orchestration, Model Context Protocol (MCP) infrastructure, and two production web platforms totaling 1.35M pages — owned end to end across architecture, build, deploy, CDN/cache behavior, SEO, analytics, security, and uptime. AI agents write most of my code; my job is context, architecture, review, and holding the bar on what ships. Every deploy is manifest-hashed and gate-verified before it goes live — no merge on vibes.
What I Own in Production Today
junelifeinsurance.com — 388,000-page statically generated insurance platform
Astro SSG + Firebase Hosting on Google Cloud. Core Web Vitals 100/100/100/100 across page families — verifiable in PageSpeed Insights right now. 7–18 structured-data nodes per page, sitemap partitioning at scale, honest lastmods, canonical discipline. Built in the licensed-insurance vertical: producer/agency directory architecture, state licensing data, compliance-gated public surfaces.
callcharlie.co — ~958,000-page licensed-contractor directory platform
Same discipline at 2.5× the scale. Public-records transparency model (Know Your Contractor) that the insurance property was patterned on.
Selected Engineering Work
- Custom MCP server, designed and shipped. 26-tool (measured 2026-08-08) Model Context Protocol (MCP) server on Cloud Run, Google Cloud Platform (GCP), serving session state, ledger queries, BigQuery-backed search analytics, and task management to every agent seat — the tooling layer that lets one engineer run a 1.3M-page surface.
- AI-first development at production stakes. Run multiple Claude agents in parallel across dedicated build, deploy, and tooling seats — one implementing, one auditing, one on infrastructure — with myself as the single review gate. Built the governance to make that safe: append-only decision registers, gate verdicts bound to artifact manifest hashes, SHA-verified deploy read-backs, honest-failure reporting (a failed read never renders as a clean line).
- Document/data ingestion at scale. Parsed Florida's public licensing corpus — 688,000+ producer records, 28,000+ agencies — from messy government exports into a deduplicated, structured directory with per-record pages, facets, and schema.
- Licensing-data corpus at national scale. Maintain the full active Florida DBPR contractor-license corpus powering callcharlie.co; currently sourcing nationwide active NIPR insurance licenses and every state's active insurance-license records for national expansion of the directory platforms.
- Funnel and demand instrumentation. Google Search Console BigQuery export analysis (SQL over impression/click/query tables), Google Ads API Basic Access with Keyword Planner via API for first-party demand data, indexation forensics, attribution-safe lead-capture design.
- Production incident ownership. Diagnosed and remediated a compromised service-account credential incident end to end — forensics, key rotation to keyless service-account architecture, IAM lockdown, provider escalation through to a written determination and full credit. Case covered by The Register (July 2026). Closed a Firestore security-rules vulnerability with claim-checked rules and live production verification.
Experience
Call Charlie Holdings LLC — Founder / Principal Engineer · January 2026–present
Everything above. Sole operator: product, engineering, infrastructure, growth, and the AI toolchain that multiplies one seat into a team. 1.35M production pages shipped across two properties in the company's first seven months.
Chief Engineer — Private Yachts to 180 ft · 20 years
Sole engineer responsible for every system aboard at sea: power generation, propulsion, HVAC, water, and the alarm/monitoring systems I built and maintained on the job. The final 7 of those years were spent concurrently building software and dev infrastructure aboard — the monitoring systems, the automation, the tooling — learned in production because at sea there is no other environment. The original on-call: failures offshore have no escalation path; you diagnose and repair under way. Source of the habits I still run: read the gauges, never trust an unverified claim, keep an audit trail.
Technical
- TypeScript
- Node
- Astro / SSG
- GCP
- BigQuery
- Cloud Run
- Firestore
- IAM
- MCP
- Claude Code
- Technical SEO
- Schema
- Python
- SQL
Fluent / daily: TypeScript & JavaScript (Node), Astro/SSG architecture, GCP (Firebase Hosting, Firestore, Cloud Run, IAM, BigQuery, Cloud Scheduler), Claude Code and agentic development toolchains, MCP server development, enterprise technical SEO, structured data/schema, HTML/CSS
Working proficiency, AI-directed daily: Python, SQL (BigQuery analytics in production; relational/OLTP growing)
Practices: manifest-verified deploys, gated release pipelines, observability and honest-failure instrumentation, security-first IAM (keyless service accounts, least privilege)