PATH 3 | FOR TECHNICAL TEAMS

Senior engineering, without the enterprise wrapper.

Event-driven systems on AWS, Spark and Python data pipelines, RAG systems that get evaluated instead of demoed, and the full-stack platform on top. Architecture decisions explained in writing, code you can read after we're gone.

bring us the hard problem
~/engineering/aws/

AWS & Event-Driven Architecture

Lambda, SQS/SNS, EventBridge, Step Functions. Systems designed around events instead of cron jobs and polling: cheaper to run, easier to reason about, built to fail loudly and recover cleanly.

LambdaEventBridgeSQSStep FunctionsDynamoDB

~/engineering/data/

Data Engineering

Spark and Python pipelines that turn raw operational data into something analysts and models can actually use, with schema contracts, backfills, and observability, not just a DAG that ran once.

SparkPythonAirflowdbtParquet

~/engineering/rag/

RAG & LLM Systems

Retrieval-augmented systems over your own corpus: chunking and embedding strategy, evaluation harnesses, guardrails, and cost control. We measure answer quality; we don't demo-and-pray.

Claude APIpgvectorembeddingseval harnesses

~/engineering/platform/

Full-Stack Platform Work

The product surface on top: Next.js, React, Supabase/Postgres, auth, billing, CI/CD. One team from the event bus to the button, no handoff gap where bugs live.

Next.jsReactPostgresSupabaseVercel

CASE STUDY | GLOBE LIFE

glonboarding.com: an event-driven recruiting platform

Globe Life needed a system to run their independent-agent recruiting pipeline end to end: booking, reminders, approval, onboarding. We designed and shipped the whole platform.

n8n · reminder-pipeline

// webhook payload carries the meeting start time

start = payload.scheduled_event.start_time

wait_24h = start - now - 24h

wait_12h = start - now - 12h

wait_60m = start - now - 60m

wait_10m = start - now - 10m

// chain Wait nodes on the delta between each interval,

// so four reminders fire off one trigger, in sequence

→ SMS via Telnyx at 24h, 12h, 60m, 10m

Architecture

  • →React front end on AWS Amplify, with role-scoped dashboards for organizational leaders, sales leaders, and new hires, plus a guided onboarding checklist after signup
  • →Two n8n pipelines running behind AWS Elastic Beanstalk and EC2: one triggered by Calendly bookings, one by Jotform applications
  • →Supabase as the system of record: candidate profiles, new-hire records, and the lead-nurture log
  • →Telnyx API for transactional SMS, including an automatic welcome message to the whole team the moment a recruiter approves a candidate
  • →A scheduled job flags stalled leads and has AI draft the follow-up email

Result: recruiters got back roughly 10 hours a week previously spent on manual outreach and spreadsheet upkeep. That state now lives in Supabase and updates itself. Live at glonboarding.com.

Send the problem statement.

Stack, scale, and what's breaking. An engineer reads every message: you'll get a technical reply, not a sales sequence.