Matt P. S.

From ambiguity
to production.

The last year of building in public. 1,360 contributions.

The last 3 months of building in public. 647 contributions.

Bringing product thinking
into engineering execution.

See workGet in touch
01The range

Problems cut across layers. So do I.

01

Shaping the product

  • Ambiguous problems
  • Stakeholder alignment
  • Product scoping
  • MVP definition
  • Prototyping
  • UX thinking
02

Designing the architecture

  • System design
  • Data modeling
  • APIs & SDKs
  • Event-driven systems
  • Multi-tenant scale
  • Technical trade-offs
03

Building & shipping

  • Full-stack delivery
  • Cloud
  • Data workflows
  • RAG & agent workflows
  • Model selection
  • Production ownership
04

Building the tools that build

  • Internal platforms
  • Workflow automation
  • SDKs & templates
  • Agent infrastructure
  • Validation systems
  • Developer experience
05

Running lean at scale

  • Cloud cost
  • SQL optimization
  • Latency
  • Performance
  • Observability
  • Reliability
06

Securing the system

  • Threat modeling
  • Pentest
  • Hardening
  • Audits & compliance
  • Access & secrets
  • Secure defaults
Stack
  • TypeScript
  • Node.js
  • React
  • Next.js
  • Python
  • FastAPI
  • Go
  • PHP
  • PostgreSQL
  • MySQL
  • Prisma
  • Redis
  • Kafka
  • Polars
  • Data pipelines
  • Query optimization
  • Microservices
  • Event-driven
  • Distributed systems
  • Background workers
  • SDKs
  • pytest
  • Jest
  • go test
  • Playwright
  • Selenium
  • Linux
  • Bash
  • AWS
  • Docker
  • Kubernetes
  • Terraform
  • Cloudflare
  • CI/CD
  • Prometheus
  • Grafana
  • CloudWatch
  • Observability
  • LLM APIs
  • RAG
  • LangGraph
  • LangSmith
  • Prompt engineering
  • Tool calling
  • Structured outputs
  • Embeddings
  • Code agents
  • MCP
02Projects

What I’m building right now.

Open source · ThesisEngineering platformLast commit Sep 2

Workflow Execution Engine

Engineering knowledge lives in docs and people’s heads. WEE turns well-defined workflows into versioned, replayable, budgeted pipelines, and the engine owns the loops, not the model. It has already reviewed a real PR and opened a real pull request on a public repo, end to end.

Key callcore/tool/git deliberately has no push op. Landing a fix on GitHub goes through the generic http tool speaking GitHub’s own Git Data API directly, instead of a one-off integration bolted onto git.

GoTypeScriptJSON SchemaLLM APIs
Workflow Execution Engine project preview
GitHubCase studyArchitectureADRsVision
03Process

Not just the code, the whole system.

Five layers between a rough idea and a working system. I own all of them, so nothing gets lost in a hand-off.

04Working with leverage

Generating options is easy now. Choosing is the job.

AI creates countless possibilities. My job is to bring judgment, context, and responsibility to choose the path that creates real impact.

POSSIBILITIESAI expandsthe frontierJUDGMENTI bring focus,context, and tasteDIRECTIONOne pathchosenIMPACTOutcomes thatmove the business
05Writing

I write to work things out.

On engineering, product, and the parts of the job I’m still figuring out.

06Work with me

Have a solution worth building?
Let's turn it into a product.

From discovery and architecture to implementation and production. One engineer. End-to-end ownership.

Schedule a 30-minute intro call
GitHubLinkedInEmailResume
Best fit
Early-stage companiesProduct-focused engineeringAI-enabled productsComplex business workflows0 → 1 and scaling products
Open to
Product Engineer rolesSoftware Engineer rolesFounding Engineer roles
Languages
English · Spanish · Portuguese
Résumé
Download PDF