Software engineer · Product designer

Building high-trust systems under uncertainty.

I work across backend infrastructure, behavioral intelligence, financial systems, and product UX, turning noisy data, constraints, and failure modes into decisions people can act on.

Available for select remote engineering and product systems roles

32K+Forensic scans
15KCurrent deployer cohort records
GO + TSWorker to product interface
API · MCP · BOTSHuman and agent surfaces

Selected systems / 03

Proof through systems.

Three projects. Three forms of uncertainty: financial behavior, route judgment, and human attention.

Behavioral / forensic intelligenceLive product

Rugburn

Token structure changes quickly, while the operator relationships behind risky activity are harder to erase.

Behavioral risk infrastructure that turns attribution, funding topology, market evidence, and uncertainty into an inspectable decision surface.

Ownership

Solo product, architecture, Go worker, frontend, data, API/MCP, bots, and operations.

  • 32K+ scan corpus; 15K current deployer cohort records
  • Attribution, funding topology, Atlas, and public Augury records
  • Dashboard, API, MCP, Telegram, and Discord surfaces
GoNext.jsPostgreSQLSolanaMCP
Financial decision infrastructureActive build

VŒID

The cheapest route across fragmented money rails can still be slow, unreliable, illiquid, or operationally wrong.

A risk-aware route intelligence layer that ranks paths under explicit cost, timing, posture, and policy context.

Ownership

Product model, route-engine prototype, operational UX, workspace architecture, and system direction.

  • Deterministic Go ranking prototype
  • Live-reference and mock-state separation
GoNext.jsSupabaseTypeScriptData systems
Social product systems / product designProduct system

Nakupenda

Social products must support expression and discovery without treating attention, access, and relationships as consequence-free.

An interest-graph social system where feeds, messaging, moderation, long-form work, and live voice each carry explicit human boundaries.

Ownership

Product design, interaction systems, state models, responsive UI, and implementation direction.

  • Role-aware live audio states
  • Boundary-aware messaging and governance
Next.jsReactTypeScriptRealtimeProduct design

How I think

Operating principles.

The repeated decisions behind the work, from data collection to interface hierarchy.

01

Evidence before confidence

A system should expose what it knows, what it inferred, and what remains unknown.

02

Failure modes are requirements

I design degraded and partial states before pretending the happy path is complete.

03

Semantics scale

Color, depth, motion, and hierarchy should represent roles, not one-off component styling.

04

Performance is UX

Every persistent animation, dependency, and render boundary has to justify its cost.

05

Automation needs boundaries

Probabilistic systems can explain and recommend. Irreversible actions need explicit policy and control.

06

Interfaces reduce uncertainty

A useful dashboard changes the quality of the next decision, not merely the amount of data on screen.

Range / archive

Different systems. Same care.

Commerce operations, music infrastructure, education products, writing, and visual work live here without competing with the flagship story.

Open channel

Building something where trust matters?

I’m available for select remote engineering, product systems, and founding-team roles.

Start a conversation