Technical Solutions Engineer

The brief

YinzCam builds the official digital products for professional sports teams and venues. I build internal automation and production web systems for them — Node.js integrations, event-driven workflows, data-feed routing, website delivery, and the production debugging that happens across eight live client environments.

The part I care most about is the tooling. A lot of delivery friction is really tooling friction — a hand-off living in someone's DMs, a status that exists only in one person's head. Where I could delete that with code, I did.

What I did

• Built a Node.js Slack-to-Jira service that turns structured Slack requests into tickets and subtasks, maps Slack users to Jira reporters, carries attachments across, syncs status back through webhooks, and recovers failed requests with retry and fail-safe logic.
• Engineered and launched the platforms for Burnley FC, Edgbaston, IMG Dubai and PJL — implementing the site experiences, configuring data-feed integrations, establishing frontend routing and content mappings, and taking each one through production readiness.
• Traced and resolved production failures across eight professional-sports websites, following each one through data feeds, routing rules, rendering behaviour and third-party integrations, and coordinating the release back out across engineering and client-facing teams.
• Built a Confluence/JQL delivery tracker and ran engineering status reviews on it with the VP and CTO, coordinating dependencies across product managers, developers, designers and account managers.

Measured

Architecture

In hindsight

Next step I'd take: route each request by its channel and message shape, so tickets land in the right project with the right owner automatically, instead of being sorted by hand after they arrive.

Stack