Under constructionThis site is actively being worked on, so expect rough edges and placeholder content.

Tony Prokop
Résumé
Live2022 - nowFull-stack engineer, Sr. StaffWP Engine

WP Engine

Core architecture for the next generation of WP Engine's customer-facing API, and the frontend platform on top of it.

customer portal · sign-in requiredRead the write-up ↓
wpengine.com
WP Engine homepage with the managed hosting pitch, dashboard previews and the Walter AI agent chat
Fig 01 - The WP Engine homepage1 of 4
100%page load performance improvement
45%drop in support chat volume
12engineering teams on one app

01 / overview

The problem

The customer-facing application was split across 12 engineering teams, and page loads showed it. [Describe what was slow or painful about it.]

The next generation of the API also had to hold up under agentic workloads, which arrived with the WP Engine MCP. [Describe the scale requirement.]

02 / my contribution

What I did

  1. 01Built core API infrastructure to scale and meet the demand of agentic workloads upon release of the WP Engine MCP.
  2. 02Led a refactor of the core application to a single page app across 12 engineering teams.
  3. 03Shipped an AI chatbot that cut overall support chat volume by 45%.
  4. 04Maintain the component library used daily by 50+ engineers, and lead the frontend guild.

03 / decisions

Key decisions

Decision 01

[Decision one]

[What you chose, what you passed on, and what it cost.]

Decision 02

[Decision two]

[What you chose, what you passed on, and what it cost.]

Decision 03

[Decision three]

[What you chose, what you passed on, and what it cost.]

01 / 06 projects

all projects →