Skip to content

I build the systems software ships on — and a few systems nobody asked for, but real people use.

Senior platform engineer with 10+ years shipping production systems — the Pipeline-as-a-Service platform that carried every application to production at Penbrothers, student-information features at Oracle, and NOC dashboards for Google as a vendor. I work across Go, TypeScript, and Python with a bias for boring, well-tested infrastructure. After hours I keep building for real users: an agent-authored operating system I run my own workday on, a live-translation stack for my church, and small tools finished properly. This site is the evidence.

Open to senior platform engineering roles and consulting engagements.


baked Oct 14, 2026

Last deploy
today
github actions
CI status
passing
github actions
Commits
48
git
Writing published
10 posts
content/
Case studies
6
content/
Last essay
531d ago
content/
Data layer
1070 lines
data/
Site age
3d ago
github

Static site — no servers. These values bake into the HTML at build time; every push to main rebuilds and redeploys them.

The 2021 how-to

687 contributions in the last year, peaking at 70 on Oct 11, 2026 — the day this site was rebuilt. Baked from the GitHub calendar at build time; the skyline is the same idea I wrote about in 2021, now running on my own site.

realtime in-memory layout
Fluid Layout Engine· realtime obstacle routing

Good platform engineering turns chaotic, distributed pipelines into quiet, deterministic systems. At its best, infrastructure is an invisible craft: reproducible build environments, immutable artifacts, resilient service orchestrations, and boring, well-tested primitives that let teams ship fearlessly. We design architectures to absorb failure, eliminate synchronous bottlenecks, and treat runtime latency as a primary constraint. When every system is measured with mathematical precision, the tools disappear, leaving real engineers free to create with clarity and confidence.

NODE-01260, 150
engine: @chenglou/pretext·layout: <0.2ms·
Try dragging the node or switching to Follow

Production platform work

The pipelines, dashboards, and internal tooling other engineers shipped on — at Penbrothers, Google (as a vendor), and Oracle.

Self-directed systems

Systems I found a reason to build: agent infrastructure I run my own day on, and a complete live-translation stack for my church.

Craft and open source

Small tools finished properly — tested, documented, and shipped — plus civic-tech work in the open.

All projects
  • helper

    2026

    An agent-authored operating system for my own executive function: 17 skills, confirm-first write gates, and an append-only audit trail, grounded in real Jira, git, and calendar data.

    Markdown vault / Agent skills / Jira / Confluence / Git

  • Captions intercepted from spf.io, LLM-translated into conversational Taglish with context buffering, persisted for review, and served to a live Material 3 caption viewer — deployed on Deno Deploy.

    Deno / TypeScript / Qwen2.5-72B / Supabase / Deno Deploy

  • A REST API serving Philippine Congress data from a Neo4j graph — legislators, bills, committees — with schema validation and automatic OpenAPI documentation. Built for the BetterGov.ph civic-tech initiative.

    Deno / Hono / Neo4j / Zod / OpenAPI

All posts

Hiring for a platform team, or need one built? hello@napjose.ph

I answer every serious email — role conversations and consulting engagements alike. PGP available via Keybase.