Skip to main content
This portfolio is structured as API documentation — because if I’m going to say I think in systems, I should probably show it.

GET /taylor-mcneil/readme

75,000+ developers across 6 continents have used something I wrote to get unstuck. I’ve mass-configured 150 flash drives overnight for a robotics workshop. Explained HMAC authentication to a room that thought I said “hammock.” Built documentation systems that outlived two reorgs. Judged many a zany hackathon project. I’m a Developer Experience Engineer with 5+ years in DevRel — at NCR, Dropbox, Stellar Development Foundation, and Mastercard. Currently freelancing, consulting on AI evaluation rubrics, and building tools that help people see complexity.
Response 200
{
  "status": 200,
  "data": {
    "roles": [
      "Developer Experience Engineer",
      "Technical Writer",
      "Developer Advocate"
    ],
    "location": "Atlanta, GA (Remote)",
    "email": "mcneiltaylor@live.com",
    "github": "https://github.com/taylor-mcneil",
    "linkedin": "https://linkedin.com/in/taylormcneil",
    "availability": "Open for opportunities"
  }
}

Where to go from here

Quickstart

The TL;DR. Configure a DevEx Engineer for your team in under 2 minutes.

Changelog

Career history as versioning — from v1.0.0 (Origins) to v4.0.0 (Current).

Case Studies

How I approach documentation architecture — OpenAPI specs, tutorial design, and more.

Guides

Full technical guides I’ve written. Real code, real explanations.

Tutorials

How I approach teaching — step-by-step walkthroughs with working code.

Active Builds

What I’m building right now: &mpersand, the DevRel Playground, and this site.

Why a docs site?

I wanted a portfolio that works the way I work: structured, searchable, and slightly overengineered for the joy of it. Also, I thought it would be funny. It was. For about 40 hours of Next.js debugging.
Start with /quickstart for the fast path, or browse the Changelog to see the full version history.

Build docs developers (and LLMs) love