About Slake Design | SaaS Systems Engineer

TL;DR

I design and ship internal systems for B2B and operations‑heavy teams—pipelines, retrieval layers, and automation loops wired directly into the way your business actually runs.
The output is a Capital System: a piece of infrastructure that reliably answers “what’s going on?” and “what should happen next?” without another Slack ping or spreadsheet.
The target is always the same: less manual search and context switching, more execution per headcount.

Technical Capabilities

Systems Architecture

I design the backend for Capital Systems: ingestion and retrieval pipelines, data integrity layers, and automation loops that are meant to survive 10 years of tech churn. Schemas, API contracts, and failure modes get worked out before anyone touches the editor.

Next.js, NestJS, Node.js, PostgreSQL, REST/GraphQL

Cloud & DevOps

Capital Systems only matter if they stay up. I handle the deployment lifecycle—containerized, observable, and auto‑scaling—so the system is boringly reliable under real load.

Docker, Azure, CI/CD pipelines, Linux/Bash, security‑conscious ops

AI & Automation

I integrate LLMs (Vertex AI, OpenAI, Anthropic) as retrieval and signal engines over your private data—not chatbots bolted on top. That means Vertex AI Search/RAG grounded in your docs and logs, automated briefings, and decision‑support agents tied to live operational data.

Recent work includes deploying Vertex AI Search over internal SOPs and tickets for ops teams, and wiring RAG responses into existing ticket workflows.

Vertex AI (Search/RAG), OpenAI API, vector databases, Make/n8n, agentic workflows

Why Work With a Principal Architect Directly?

You’re not hiring an agency layer; you’re working with the person designing and shipping the system. My background in risk and controls shows up as boring, predictable behavior in production: clear ownership, guardrails, and audit trails instead of “magic.”

Operational Discipline & Controls:

Failure Mode Analysis: Failure modes are mapped before build, with recovery paths designed for business continuity.
Auditability & Provenance: Data is treated like a ledger: logged, traceable, and hard to corrupt by accident.
Long-Term Viability: Systems are written so another senior engineer can take them over without a two‑week oral history.

Based in Austin, TX. Available for on‑site work for local engagements.

Ready to Kill Your Information Tax?

Start with a free Systems Snapshot. We’ll surface the worst search and glue‑work leaks in your operations and show you what a Capital System would replace.

Get a Systems Snapshot (Free) See Systems Work