Work

What I built and owned, and where an attacker would push on it. The engineering is the proof. The attack surface is where I’m heading.

Rad Labs Working

Sep 2026 – Present

Full Stack Engineer / Project Lead

Problem

A healthcare product needed a mobile app built from the ground up, on top of a backend that web dashboards and production workflows already depend on.

What I build and own

  • Lead development of the healthcare mobile application.
  • Build and integrate production features across React Native / Expo, APIs, authentication, data flows, and backend services.
  • Extend the existing backend while keeping it compatible with its current consumers.

Attack surface

Patient data on a mobile device, authentication between the app and the API, and a shared backend where one change can affect every client.

Consultifi Data

Feb 2026 – Jun 2026

Full Stack Engineer

Problem

Manufacturing operations needed software that matched real floor and office workflows: inventory, production, dispatch, and devices that keep working when the network drops.

What I built and owned

  • Production ERP workflows across frontend, backend services, databases, and device integrations.
  • React / Electron apps, SQLite / PostgreSQL, REST APIs, QR-based workflows, and real-time updates.
  • Connected stations: USB scales, thermal printers, QR identities, and Raspberry Pi services, with offline-first sync, retries, and idempotent writes.

Attack surface

Physical devices on a factory floor, the tokens they carry, the sync queue that replays events, and the boundary between plants.

Controls

  • A token per station instead of one shared key, mapped server-side to a single plant.
  • 401 for unknown callers and 403 for the wrong plant.
  • An event id in the data model, so a replayed event can’t double-count stock.

Result

Operations keep moving when the network drops, and one compromised box doesn’t speak for the whole factory. Client identities stay confidential.

SIA Health

May 2025 – Oct 2025

Full Stack Developer

Problem

A healthcare product needed new features built and maintained across the whole stack, inside an existing codebase.

What I built

  • Full-stack features across frontend interfaces, backend APIs, database workflows, and third-party integrations.
  • Turned requirements into working features and investigated production issues.

Attack surface

User-supplied input in health-related forms, third-party integrations, and how data is validated before it’s stored.

Autonomous Work

Jan 2025 – Mar 2025

Full Stack Developer

What I built

  • Web application features across frontend and backend layers, integrating APIs and database-driven workflows.

Personal projects

Ongoing

Products I owned end to end

What I built

  • Simple Form: a form builder with public submissions, analytics, exports, and embeds, plus rate limiting and a honeypot on the public path.
  • Custom OIDC provider: an experimental OpenID Connect provider built with Bun.
  • Recipe Reveal: a full-stack Next.js app using SSR and SSG, deployed to production.

Attack surface

A public database port, and the redirect and token handling in an identity flow.

Open-source work is listed under Achievements on Home.

Result

A ransomware bot got into Simple Form’s Postgres through default credentials. I moved the database to loopback-only with real secrets. That incident is a big part of why I’m moving into offensive security.