BrytecoreBrytecore

The platform problem

One platform, many brokerages: every tenant gets its own Next.js site powered by its own Strapi headless CMS, and all of them consume a shared package I build and maintain — design-system components, listing search and mapping, and edge middleware for bot detection, geo-aware consent, and visitor identity. A GraphQL layer feeds structured CMS content into each app, so the content model and the component architecture have to evolve together.

The role runs well past UI

Three fronts get most of my attention. Technical SEO at fleet scale: schema.org structured data, sitemap and canonical correctness, ISR caching strategy, and SSR crawlability guards that catch regressions at build time rather than in search consoles. Privacy and analytics integrity: consent management across opt-in and opt-out markets, consent-gated network blocking, and first-party analytics you can trust — bot filtering, event dedupe, attribution. And test infrastructure: colocated Vitest suites plus a shared Playwright E2E registrar that gives every tenant a fleet-wide spec suite from a single source.

AI-augmented, evidence-disciplined

The biggest shift in how I work happened here: I run AI-augmented engineering daily, orchestrating parallel Claude agent lanes through MCP integrations — project tracking, browser automation, CMS, observability — under a written evidence discipline that separates measured fact from inference. Audit-to-remediation programs that would take a team weeks now land in days, with tighter review than before, not looser.

How I got here

I joined in September 2024 as a Frontend Developer, building tenant sites and the CMS-driven page composition behind them — content types, component blocks, and the GraphQL queries wiring them into each app, alongside listing surfaces backed by live MLS feeds. In May 2025 I stepped up to lead the frontend.