Pieter VenterPrincipal engineer / architect

Principal Software Engineer & Software Architect

Architecture.Code. Delivery.

I’m a hands-on engineer and technical leader with 15+ years of experience. My focus is architecture, TypeScript and AI systems, with hands-on delivery across Node.js, React and Python.

An idea, taking shape
Portrait of Pieter Venter
15+ years
building software and teams
Early team member at Invisible
led core engineering and the Process Engine
Hands-on technical leadership
AI products, durable workflows and integrations

Selected work / 01

What I’ve built and led.

From leading Process Central at Invisible to building AI sales features at Acquisity, I combine hands-on engineering with architecture and team leadership.

More projects and case studies

Brief for Web2026Side project

Turn public tenders into a practical shortlist

A tender discovery workspace for web agencies, with source-linked opportunities, eligibility details and submission deadlines. Compare notices, keep private notes and decisions in the browser, and export a shortlist or calendar reminders.

Open Brief for Web
Catalog Check2026Side project

Find price mismatches before they become feed problems

A browser-based diagnostic that compares a product feed row with structured offers from saved product-page HTML. Check variant identity, sale prices and currencies, then export an evidence report. Product inputs stay in the tab.

Open Catalog Check
FulfilCheck2026Side project

Trace warehouse charges back to agreed rates

A browser-based tool for comparing 3PL invoice exports with flat per-unit rate cards. Exact decimal calculations flag rate differences and repeated line IDs, while reviewer decisions, notes and provider questions stay with the review. Files stay in the browser.

Open FulfilCheck
Personal Worklog2026Side project

Resuming coding-agent work across sessions

Personal tooling that records active tasks, decisions and pending reviews so a new coding-agent session can pick up where the last one stopped.

Read the system study
BabyTracker2026Side project

A small app for busy days

A personal project: a native iPhone app for logging feeds, sleep and care, built with SwiftUI, SwiftData, widgets and App Intents.

SynclyFounder2025-PresentSide project

Durable data integrations

An independent data integration platform designed around long-running syncs, retries, rate limits, progress reporting and external-system failure boundaries.

Read the architecture study

Interactive prototypes / 02

Show the working idea.

Exploratory demos of sales follow-up, workflow design and order review. These are prototypes, not production customer deployments.

Interactive prototype / 01

A useful next message starts with context.

Review a sales conversation, edit the suggested follow-up and decide whether it should proceed. Replies and opt-outs stop the sequence.

  • Conversation context
  • Editable drafts
  • Explicit approval
Signal DeskSample workspaceOpen full screen
Signal Desk prototype with a conversation queue, relationship context and an editable follow-up draft.

Browser prototype with sample conversations. Sending is simulated; no email service is connected.

Read the design decisions
View all prototypes

Public record / 03

The work leaves a trail.

A small selection of source material for people who prefer to inspect the details.

tRPC / 2021

Early contributor and maintainer.

Collaborated with Alex Johansson on early API design and reviewed middleware, server-side calling APIs and the v9 changes.

Prisma / 2021

Scaling a system without stopping it.

Prisma’s case study documents a gradual Sequelize-to-Prisma migration at Invisible, with no customer downtime reported during the transition.

Open source / ongoing

Small changes, real failure modes.

Documentation credit in ts-rest and a Factory transition-handling fix with regression coverage in Mastra.

Working style / 04

Close to the code. Clear on the outcome.

01

Start with something useful.

Find the smallest version that a real person can use, learn from it and let that shape the architecture.

02

Make decisions clear.

Explain the tradeoffs, agree on the next step and give the team enough context to move forward.

03

Design for recovery.

External systems fail. People change their minds. Good software makes the next safe action obvious.

I’m at my best in small teams with hard problems and short paths from idea to reality. I’ve led engineers and engineering managers, but I’ve never wanted to get too far from the work itself.

TypeScript, React, Node.js, Python and Postgres are familiar ground. Durable workflows, integrations and infrastructure for AI agents are the problems I keep coming back to.

Start a conversation / 05

A worthwhile problem is a good place to begin.

I’m looking for a full-time Principal Software Engineer or Software Architect role where I can lead and stay hands-on. I’m also open to focused contracts and fractional CTO work.

Remote · B2B contractor via own company · No sponsorship needed · open to periodic travel© 2026 Pieter Venter