Professional archive · 2022—now

Systems work, with the decisions left in.

Case studies covering the context, constraints, implementation, and outcomes—not just the final technology list.

Snorkel AI — Frontier Model Evals

Software Engineer, AI Evaluation (Contract) — building and reviewing SWE evals with deterministic grading and anti-cheat validation

50+ evaluations built200+ evaluations reviewedAnti-cheat validated
  • 50+ evals built
  • 200+ evals reviewed
  • Reward-hacking resistant
Read the case study

Impact

  • Designed and delivered 50+ software-engineering evaluations for frontier AI coding models, each with a deterministic reference solution and automated grading.
  • Reviewed 200+ evaluations for correctness, test coverage, reproducibility, and resistance to reward hacking.
  • Strengthened model-assessment signal by applying AI-assisted code review and systematic failure analysis.

Problem

Evaluating whether a frontier model can actually ship working code requires tasks that are unambiguous, reproducible, and impossible to game. Weak specs, flaky tests, or exploitable graders produce misleading scores that overstate model capability.

Approach

  1. Authored deterministic reference solutions and pytest grading harnesses for each task.
  2. Packaged every evaluation in a reproducible container so results are environment-independent.
  3. Designed anti-cheat validation to catch reward hacking and shortcut solutions.
  4. Reviewed peers' evaluations for verifier strength, instruction/test alignment, and reproducibility.
  5. Used AI-assisted code review and failure analysis to raise task quality and code quality.
PythonpytestDockerReproducible containersDeterministic oraclesCI/CD

Results

  • 50+ evaluations delivered with deterministic grading and anti-cheat validation.
  • 200+ evaluations reviewed, improving correctness, coverage, and reproducibility across the set.
  • Clearer, harder-to-game tasks that produce more trustworthy model-capability signal.

LAUSD Snowflake Identity Migration (Ping AIC)

Software Engineer, Trivir — Client: LAUSD — IC owner of connector patch + bi-directional live-sync rollout

250K+ identitiesBi-directional live sync (Snowflake ↔ Ping AIC)Write-backs to Snowflake
  • Migration unblocked
  • Near-zero sync failures
  • Manual reconciliation eliminated
Read the case study

Impact

  • Enabled bi-directional live sync between Snowflake and Ping Advanced Identity Cloud for 250,000+ student and staff identities.
  • Replaced legacy IAM, unlocking LAUSD’s migration to modern cloud identity at district scale.
  • Improved reliability and reduced operational overhead from nightly manual reconciliations.

Problem

Snowflake write operations were failing during identity syncs because the ForgeRock Database Table Connector incorrectly attempted `RETURN_GENERATED_KEYS` on non-INSERT operations. Since Snowflake views are immutable, deletes/updates failed, blocking the migration and stalling LAUSD’s IAM modernization.

Approach

  1. Diagnosed connector’s JDBC misuse (`RETURN_GENERATED_KEYS` on DELETE/PATCH).
  2. Patched ForgeRock Database Table Connector to skip unsupported calls.
  3. Designed and deployed live sync so that identity changes in Snowflake automatically propagated to Ping AIC—and vice versa.
  4. Validated integration with test cohorts; rolled out incrementally to 250K users.
  5. Implemented monitoring and alerting for sync reliability.
Ping AIC (RCS)SnowflakeJava/KotlinJDBCDockerOAuth2/OIDC

Results

  • Migration unblocked; Snowflake ↔ Ping AIC synchronization stable in production.
  • LAUSD successfully cut over from legacy IAM, covering quarter-million identities.
  • Reduced sync failures to near-zero; eliminated manual reconciliation overhead.

Georgia Courts — Docket Notices

Software Engineer, Trivir — Client: Georgia Court of Appeals & Supreme Court — led Java→Kotlin rewrite and deterministic PDF pipeline

Java → Kotlin rewriteDeterministic PDFsVersioned REST APIs
  • Template errors eliminated
  • Predictable rendering
Read the case study

Impact

  • Modernized docket notice pipeline to Kotlin with stricter contracts and versioned REST.
  • Produced deterministic PDF notices via Freemarker + FlyingSaucer replacement, improving reliability and debuggability.

Problem

Legacy Java utilities and Velocity templates caused brittle formatting and null-handling issues in docket data.

Approach

  1. Ported Java to Kotlin with data classes; enforced enums and date formatting in DocketNoticeData.
  2. Replaced Velocity with Freemarker; added safe URL escaping via String?.escapeUrlString().
  3. Fixed ResultSet mapping, null safety, and associated-case queries.
  4. Added tests around getAssociateCaseView; stabilized template rendering.
KotlinFreemarkerFlyingSaucerJDBCPDFsREST

Results

  • Eliminated classes of null and formatting errors; predictable PDFs and simpler diffs.
  • Clearer API boundaries and easier future changes.

eDirectory CI Rig for IdMUnit

Software Engineer, Trivir — Internal CI/IdMUnit — built containerized eDirectory test rig + Jenkins pipeline

Containerized eDirectory 9.2.7TLS-ready startupAutomated IdMUnit testsAD↔eDir network checks
  • Fewer flaky builds
  • Predictable readiness gates
Read the case study

Impact

  • Created a Docker Compose test rig for eDirectory with init imports and cert generation, enabling consistent IdMUnit runs in CI.
  • Reduced flaky start and wait issues with a dynamic readiness gate instead of hardcoded sleeps.

Problem

Manual setup of directory state and TLS blocked reliable automated tests and slowed builds.

Approach

  1. Four-service Compose: cert-generator, eDir, eDir-init, test-runner.
  2. Dynamic wait for TLS port and health checks before tests.
  3. Jenkins pipeline with stages for container startup, AD↔eDir network verification, and Ant build.
  4. Host-network config for Maven stages; artifact gating for snapshot and release.
Docker and ComposeJenkinsAnt and Java 1.8IdMUnitTLSBash

Results

  • Reproducible local and CI environment; fewer flakes and faster feedback loops.
  • Clear runbook and predictable test outcomes.

Golden 1 — Verafin Log ETL

Software Engineer, Trivir — Client: Golden 1 Credit Union — built, tested, and deployed the Ping AIC → Verafin pipeline in Ruby + Fluentd

High-volume event streamFraud/AML-ready recordsResilient in production
  • Auditable transforms
  • Single normalized record shape
Read the case study

Impact

  • Built, tested, and deployed a production Ruby/Fluentd pipeline that transformed a high volume of Ping Advanced Identity Cloud login and logout events into structured Verafin fraud-monitoring records.
  • Delivered a single, normalized record shape that fraud and AML workflows could consume reliably.
  • Hardened the pipeline against real production failure modes so ingestion stayed dependable.

Problem

Raw Ping authentication logs did not match Verafin's required schema, and a naive transform broke on malformed fields, missing values, and delimiter collisions—stalling fraud and AML monitoring for a credit union's login activity.

Approach

  1. Implemented event mapping and field normalization in Fluentd using Ruby filters.
  2. Added resilient field fallbacks, status normalization, and delimiter-safe serialization to survive malformed input.
  3. Diagnosed and fixed control-flow, nil-response, and runtime failures surfaced in production.
  4. Added local diagnostic logging and validated output against the Verafin specification.
RubyFluentdPing AIC logsJSONCI/CDLinux

Results

  • Auditable, compliant ingestion with a single normalized record shape.
  • Eliminated manual reconciliation by enforcing consistent, well-formed records.
  • Improved production reliability by removing the control-flow and nil-response failure modes.

Microsoft — Azure HPC Telemetry and Access-Review Automation

Software Engineer Intern — data pipelines and compliance automation.

Microsoft
Azure HPC pipelinesNVIDIA H100 telemetryAccess-review automation50K+ records processed
  • Telemetry centralized
  • Faster tuning feedback
Read the case study

Impact

  • Built Python pipelines on Azure HPC clusters to analyze GPU thermal and telemetry data used for model training and tuning cycles.
  • Automated access-review compliance workflows, processing 50K+ records and surfacing insights via dashboards.

Problem

Telemetry was scattered and manual compliance processing slowed operations.

Approach

  1. Orchestrated Python jobs on Azure and stored and queried data in Azure Data Explorer.
  2. Automated access-review workflows with Logic Apps and standardized the data shape.
  3. Published interactive dashboards for stakeholders.
PythonAzure HPCAzure Data ExplorerLogic AppsPower BI

Results

  • Faster tuning feedback for HPC users and reduced manual compliance effort.
  • Centralized data with repeatable workflows.

Independent work

Products built from personal stakes and curiosity.

Smaller systems where I own the problem definition, product choices, implementation, and feedback loop.

Personal product

USCIS Civics Exam Study App

2025

Bilingual exam‑prep platform with adaptive testing, streaks, role‑based media access, and Arabic audio.

Built for one real learner; helped my mom prepare for and pass her U.S. citizenship exam.

ReactTailwindFastAPISQLAlchemySupabase

Private market intelligence build

Court Terminal

2026

A production market-intelligence platform for the NBA 2K MyTEAM auction house. Pipelines collected 1.54M listing observations across 29,600 runs, covering 869K unique listings and 709K inferred sales.

Turned an opaque auction market into a queryable system, deployed as a five-container Docker/Caddy environment with GitHub Actions, GHCR images, and restricted-SSH releases.

PythonFastAPIPostgreSQLDockerCI/CD

Independent build

WNBA Prediction Platform

2026

A FastAPI/Go backend and model pipeline for game prediction, with Optuna hyperparameter tuning, 10,000-run Monte Carlo simulations, and PostgreSQL storage.

Turned raw game data into calibrated predictions, backed by ~55 automated tests for reliability.

PythonFastAPIGoPostgreSQLLightGBM

Next system

Need this kind of engineering judgment on your team?

Start a conversation