the work

// about

No degree.
Ten years of shipping anyway.

I'm DJ Vos, a self-taught developer in Omaha. I learned to build the slow way — by needing something that didn't exist, building it badly, and then rebuilding it until it held up in daily use. Most of the projects on the front page started as a problem I had that week.

The one I'd point a hiring manager at first is the agentic work harness: a multi-agent system that automates the bulk of a client-facing operations role, built over about two months and now in daily use. It isn't a weekend demo and it isn't a toy — it's a system quietly doing a real job, which is a very different engineering problem from making an agent look impressive once. It runs against a real company's systems, so the details are for a call rather than a public page.

The other half of my background is the part that usually doesn't come with a developer: ten years in client-facing, quota-carrying roles. I can sit in front of a customer, work out what they actually need as opposed to what they asked for, and then go build it — which is most of the job description for a forward-deployed or solutions engineer.

I'm looking for a full-time developer role, remote or in Omaha. I'd rather be judged on the work on the front page than on a credential I don't have. Five of them are open source; the demos are recordings of real software, not mockups.

DJ Vos
DJ Vos · Omaha, NE

// how i build

Four habits the work has in common.

01

Agents that ship, not agent demos

The hard part of an agent is not the prompt, it's the boundary: what it may do unattended and what has to come back to a human. Every one of mine draws that line explicitly — the front desk drafts texts for approval, the Minecraft agent's survival rules are enforced in the mod rather than requested in a prompt, the consolidation engine proposes and never writes.

02

Local-first by default

Jarvis, the Work Brain and vault-pm all run with the network unplugged. Partly cost, mostly consequence: a tool with no API bill and no vendor cannot be priced out of existence or shut off, and a password vault or someone's private notes should never have been another company's problem to leak.

03

Measured, not assumed

Jarvis runs hourly against an eval suite. Rug Radar writes every scan's real outcome back and grades itself against it. The trading bot has a published gate — +5% per trade across 150+ paper trades — that it has not met, so it has never touched real money. Field HQ has a test that fails the build if the server collapses back into one god file.

04

End to end, including the boring half

Schema, backend, frontend, deploy, and then the installer, the cache headers, the compressed video encodes and the write-up. Several of these exist because the version a friend had to npm install was the version a friend never opened.

// stack

What I reach for.

Languages

  • Python
  • TypeScript
  • JavaScript
  • Swift
  • Node
  • Solidity
  • Lean 4
  • SQL
  • PowerShell

AI & agents

  • MCP servers
  • multi-agent harnesses
  • tool use
  • local RAG
  • Ollama / MLX
  • Claude API
  • eval loops
  • XTTS voice

Data & infra

  • SQLite
  • Postgres
  • Supabase
  • Drizzle
  • FastAPI
  • Express
  • Cloudflare Pages
  • Workers
  • Railway
  • Tailscale

Frontend & shipping

  • Next.js
  • React
  • vanilla JS
  • Canvas / WebGL
  • SwiftUI
  • SpriteKit
  • Electron
  • Playwright
  • GitHub Actions

// contact

Let's talk about a role.

Fastest way to reach me is email. If you want to see something that isn't recorded yet, I'll walk you through it live on a call.