Wallboards Leaderboard v2
Rebuilt the real-time Leaderboard slide for a contact-center Wallboards display system in six weeks with one teammate — new UI, better slide management — as part of a 12-engineer platform-wide replacement effort.
Daniel Boyd — Software Engineer
Two-plus years shipping and maintaining features in a large enterprise platform (.NET, Angular) — plus a growing habit of building directly with LLMs, most recently a retrieval-augmented assistant for tabletop game masters.

Rebuilt the real-time Leaderboard slide for a contact-center Wallboards display system in six weeks with one teammate — new UI, better slide management — as part of a 12-engineer platform-wide replacement effort.
An LLM-powered assistant for tabletop game masters covering spell and monster lookup, encounter building, and full worldbuilding support, backed by a retrieval-augmented generation pipeline over game rules and lore.
Extended a large enterprise product to Simplified Chinese, Traditional Chinese, and Korean, with groundwork laid for Hebrew ahead of a pending regional deal, plus contributions to a shared internal localization tool.
Designing and shipping a retrieval-augmented generation assistant for tabletop game masters, using OpenAI models over a custom knowledge base of rules and lore.
Use Claude and GitHub Copilot daily in production work to accelerate scaffolding, refactoring, and repetitive implementation tasks while preserving code quality.
Treat AI output as a draft: verify behavior, align with architecture, and ship only after measurable confidence through testing and review.
I’m strongest when translating broad goals into working software with clear tradeoffs. I care about dependable execution: diagnosing issues quickly, reducing complexity, and keeping delivery predictable.
Outside work, I run tabletop campaigns as a dungeon master. That’s part of why I started building an AI assistant to help other DMs run their own tables — combining a hobby I love with hands-on LLM engineering.
I keep this section because passion projects still show engineering habits: integrating third-party APIs, handling auth securely, and presenting noisy data clearly.
Data comes from a server-side Next.js API route using FFLogs OAuth credentials from environment variables. No API secrets are exposed to the browser.
This panel demonstrates secure OAuth integration, server-side API routing, and live data rendering.
I’m open to software engineering opportunities where I can contribute to product quality, velocity, and long-term maintainability.