Open to full-time engineering and select consulting opportunities

Christian
Bobo.

01 / Systems

Full-stack applications, data pipelines, integrations, and operational tools.

02 / Translation

Complicated domains become models, workflows, and explanations that hold up against real constraints, edge cases, and incomplete information.

03 / Judgment

Six years in capital markets shaped an approach grounded in evidence, failure modes, and knowing when the correct answer is still unknown.

Before the code

The work began with financial systems that were difficult to explain and expensive to misunderstand.

At BMO Capital Markets, I worked on the credit side of Global Markets, translating businesses, transactions, and changing exposures into decisions senior stakeholders could act on.

Bloomberg, Intex, SQL, VBA, Excel, and internal systems became tools for improving reporting and reducing repetitive work. Development continued the same method: understand the system, connect the evidence, expose exceptions, and make the result usable.

Explore the work

Selected work

Working systems, explained from the inside out.

Educational Research Tool01

InsulinGuide

Making fragmented insurance evidence understandable without pretending it is more certain than it is.

InsulinGuide asks what evidence exists that a health plan may cover a specific insulin pump, and how confident someone should be in that evidence.

The system reconciles inconsistent plan identities, separates authoritative documents from fallback sources, preserves explicit unknowns, and shows why a result was reached.

Entity resolution across carriers, issuers, plans, states, and marketsEvidence maturity without flattening uncertaintyPatient guidance and a deeper clinician research workspaceApplied AI constrained by sources, review state, and exceptions

Evidence flow

Sources
Extraction
Normalization
Evidence classification
Audit state
Research experience

Next.js · TypeScript · Supabase · Vercel

Hover to load preview
Live preview
Private Working Pilot02

Hummingbird PMP

Designing operational software for work that does not fit neatly into CRUD.

Hummingbird is a private working pilot for role-based property operations, accounting integrity, and workflow automation.

Its strongest slice follows rent through onboarding, payment state, reconciliation, and the records visible to property managers and owners. Payment workflows remained in sandbox and staging.

Multi-tenant organization and property boundariesRole-specific portals and permission scopesStripe Connect, ACH state, and idempotent webhook finalizationPlaid and Stripe bank-line reconciliation with visible match status

Cash-collection workflow

Organization setup
Role and property scope
Stripe Connect
ACH payment state
Webhook finalization
Ledger consistency
Bank-line explanation

React · TypeScript · PostgreSQL · Stripe

Hover to load preview
Live preview

Selected experiments

Ideas explored far enough to understand what they could become.

Slang Sleuths

Functional Prototypes · Archived

A game-based Spanish-learning prototype using short exercises for vocabulary, listening, grammar, and country-specific slang.

Architecture
A regional phrase library supplied mini-games, daily training, skill visualization, progress summaries, and adaptive game selection.
Intended end state
A playful learning product for recognizing how everyday Spanish changes across countries and contexts.

World Events

Research & IA Prototype

An Obsidian research system connecting people, institutions, events, time periods, sources, and recurring themes.

Architecture
Structured notes and source records linked entities, timelines, themes, and competing interpretations.
Intended end state
A searchable visual knowledge graph: a modern Wikipedia organized around relationships, provenance, and visible uncertainty.

Bushido

Early Unity Concept

A virtual-reality concept for learning swordsmanship through tracked physical movement instead of button combinations.

Architecture
A Unity 6 foundation combined input, physics, and VR/XR support around tracked controller movement.
Intended end state
A training game that maps physical technique to recognition, feedback, progression, and eventually sparring.

Capabilities

Tools selected for the problem.

A working toolkit across product development, data systems, deployment, observability, payments, and AI integrations. Familiarity is grouped by how consistently each tool appears in the work.

Core

GitHub
Vercel
Railway
Supabase
Stripe
Plaid
PostHog
Grafana
Cursor
Codex
Ollama
Docker

Regularly Used

Google AI StudioChatGPTClaudeGeminiClerkTwilioContext7LinearDocuSign DeveloperFigmaHermes · Discord botNotebookLMRedisOpenRouterNVIDIA NIMMCPs

Explored / Comfortable

Perplexity Deep ResearchHugging FaceSentryImprovMXConvexReplitNotionCanvaMercury

Engineering Principles.

How difficult systems become workable

01 /

Pass the Taxi-Driver Test

If a system cannot be explained clearly to an intelligent person outside the field, it probably is not understood well enough yet. Clear language is part of the engineering work.

02 /

Model the Problem Before the Interface

Start with actors, states, decisions, and failure modes. A polished interface cannot rescue a model that does not match the work.

03 /

Treat AI as an Accelerant, Not an Authority

Models can accelerate discovery, extraction, comparison, and drafting. Correctness still requires constraints, source evidence, evaluation, and a human in the loop for consequential decisions.

04 /

Preserve the Unknown

In finance, healthcare, and production systems, an unsupported answer can be worse than an explicit gap. Uncertainty should be exposed rather than converted into manufactured confidence.

05 /

Debug the System, Not Just the Symptom

Important failures often begin upstream: an unclear contract, weak data model, missing state transition, or process nobody fully documented.