01 · A shipped demo, not another résumé

PREHOG

Context before credentials.

I built this presentation for the Context Engineer role on PostHog's Wizard & Docs team. It is also my first production implementation of PostHog.

02 · Why PostHog

Why PostHog

I value teams that write decisions down, ship useful work, and learn from real usage. That is the engineering culture I see in PostHog.

  • Autonomy, not process theater
  • Context that's written down, not tribal
  • Small teams where writing and code are the same job
  • Shipped and observed, not polished in private

03 · Why Context Engineering

The throughline in my work

Software engineering, reliability, interaction design, technical communication, and AI workflow engineering all depend on clear context. It is the thread that connects my work across those disciplines.

Make the next step clear for the person or system doing the work.

See the evidence on /about

04 · How I work

How I work

I start by understanding the problem, then structure the work, build it, test it, observe the result, and document what changed. This presentation followed that same process.

05 · Evidence

Relevant work

Three projects that show how I approach context, systems, and documentation.

localcrew

Local inference orchestration

A local-first harness that connects Ollama and OpenAI endpoints across a LAN into one usable inference network.

View source

stay-ahead

Agent-assisted development notes

A working notebook on writing documentation that an agent can use while a team builds and maintains software.

View source

prehog

Instrumented application project

A small PostHog implementation with Playwright coverage, a reviewer-facing README, and structured context for coding agents.

View source

06 · Learning PostHog through implementation

What I am measuring

This is my first production PostHog install. I started with a short list of questions, then added only the events needed to answer them.

Question Signal
Do people meaningfully progress through the deck?prehog_slide_viewed
Where do sessions stop?prehog_slide_viewed vs. prehog_completed
Is the navigation discoverable on mobile?prehog_navigation_used + masked replay
Do reviewers inspect the repository?prehog_outbound_clicked
Does anyone let it auto-play, or take control?prehog_autoplay_toggled

07 · Context for humans and agents

Documentation for people and agents

The project keeps its architecture notes, decisions, and analytics rules in the repository. The README.md gives a reviewer the story; AGENTS.md gives a coding agent the working context.

Read AGENTS.md

08 · Why me, why now

Why this role

I have spent more than ten years building full-stack products, QA automation, documentation systems, and AI-assisted workflows. This role brings those strengths together. My resume has the details.

09 · Inspect the work

Take a look

GitHub github.com/benmcnulty/prehog Resume benlive.tv/about Portfolio benlive.tv/portfolio Home benlive.tv

A short feedback survey may appear here after you finish the presentation.