UX Engineer, Traackr
An influencer marketing platform built as a cluster of microservices and applications, serving brands and content creators. Four team rotations over four years: feature delivery, design system, platform modernization and developer experience.
- TypeScript
- JavaScript
- Vue 2.7
- Composition API
- Vuex
- Vue Router
- Node.js
- Go
- GraphQL
- Apollo Server
- PHP
- CakePHP
- Sails.js
- Express
- SQL
- PostgreSQL
- Sequelize
- TypeORM
- Redis
- REST
- OpenAPI
- Swagger
- Anthropic API
- Claude Haiku
- Claude Code
- CLAUDE.md
- OpenID Connect
- OAuth 2.0
- Keycloak
- JWT
- Kubernetes
- Helm
- Terraform
- Docker
- AWS
- JFrog Artifactory
- Jenkins
- GitHub Actions
- Datadog
- Grafana
- New Relic
- Storybook
- WAI-ARIA
- WCAG
- axe
- SCSS
- Tailwind CSS
- HTML
- CSS
- Vite
- pnpm
- release-please
- Jest
- Vitest
- Jasmine
- Vue Testing Library
- Bubble Tea
- Shopify
- SendGrid
- Slack API
- Axios
- Git
- GitHub
- Bitbucket
- Jira
- Confluence
- Slack
- Zoom
- Figma
- Scrum
- design tokens
- microservices
- monorepos
- feature flags
-
Built a production LLM analysis pipeline on the Anthropic API, and made all of its architectural and technical decisions. Claude Code session hooks captured development transcripts, a worker scrubbed secrets and personal data, Claude Haiku returned typed findings with confidence scores naming missing tooling and repeated failure patterns, and findings above a threshold were posted to Slack as pre-filled Jira tickets for a human to accept or reject. I also authored the
CLAUDE.mdfiles and skill definitions for three platform monorepos. -
Principal contributor to an accessibility-first design system, published as an npm library and adopted as mandatory across the engineering organization. I built a large share of its 30-plus components, from atoms up to the UI Shell every page renders inside, all to the WAI-ARIA guidelines — full keyboard navigation on every interactive component, and a breadcrumb that measures its available space and collapses or expands its trail to fit. I wrote Storybook stories for each of them, backed by full unit-test coverage and automated Storybook tests with visual-diff checks against regressions, and published releases through release-please. I also contributed to the Styles Library, the design-token layer governing typography, color and theming across the system.
-
Acted as the UX team’s engineering ambassador. I helped engineers on other teams translate Figma designs into components, filled the gaps in the library when they found them, and resolved undocumented usage. I hosted internal talks on building accessible components, on CSS layout, and on how DOM events actually work.
-
Built bulk-selection components and the GraphQL batch mutations behind them, so customers could select thousands of records the browser had never loaded and act on all of them at once. In the design system: the checkbox, with its indeterminate state and the select-all logic behind it, and the floating toolbar that carries the actions. In the GraphQL aggregation layer: batch mutations that report which records failed and why, and cursor pagination written by hand in both directions. The work crossed service boundaries, so I traced it through the cluster to every service and code path it touched, and released each service only after the ones it depended on.
-
Contributed to a strangler-fig migration that replaced legacy monolith endpoints with a GraphQL aggregation layer, helping move multi-source data assembly out of a PHP application into Apollo Server: resolvers, schema contracts, pagination and batch operations.
-
Diagnosed and rebuilt the query semantics of a distributed search pipeline, so that negated filters, and records held at both tenant and global scope, returned exactly the right results for every customer. I used Boolean algebra to handle absence-of-record and multi-scope quantifier logic over a legacy schema, drove the specification with Product, de-risked the cross-service blast radius with the staff engineers, and wrote the corner-case verification plan.
-
Added Slack and Jenkins automation to my team’s Go release assistant, which every engineer on the platform monorepo used. The assistant, a Bubble Tea terminal application, walked an engineer through a release, every step of which meant leaving the terminal to write documentation, notify release approvers, track release tickets or execute build pipelines. I wrote the Slack integration, which showed the exact message and asked before notifying the approvers, and the Jenkins client, which executed the build pipelines, so those steps no longer took anyone out of the terminal.
-
Primary frontend engineer on the brand–creator collaboration feature, spanning three services, and wrote all of the frontend’s integration with brands’ Shopify stores: product selection and grid rendering, CDN media upload with preview and replay verification, and a constraint-filtering algorithm computing which product variants remained selectable as a user narrowed their choices.
-
Proposed and delivered a full rewrite of the creator application’s layout, which made it genuinely usable on a phone — including the difficult iOS Safari cases across layout, video playback and native control substitution. Nobody asked for it; the product needed it.
-
Triaged reported security vulnerabilities, establishing which were genuine and which were false positives, and documenting the findings with proposed fixes for the ones that were real.
-
Modernized the legacy application incrementally — navigation, wizards, menus, snackbars and forms — including replacing a modal orchestration system that couldn’t reliably keep to one modal at a time, and introducing blur-validated forms with real loading, error and confirmation states.
-
Worked on the developer-experience team that consolidated the company’s repositories into three domain monorepos, one each for the application services, infrastructure as code and data pipelines.
-
Deployed services to Kubernetes through Terraform and Helm, writing the deployment definitions for new and existing microservices and shipping my own changes to production.
-
Wrote the frontend test suites across all three codebases in Jest, Vitest, Jasmine and Vue Testing Library, and enabled the QA team’s Cypress end-to-end suite with dedicated test attributes. Released behind feature flags with progressive rollout, and organized cross-team bug bashes before major releases.
