Experience
AudioEye
Internal marketing systems, headless CMS integrations, forms, quoting flows, accessibility work, and project ownership across product-adjacent web properties.
Overview
At AudioEye, I own much of the engineering surface area behind the company's marketing, lead generation, sales, and revenue operations. That work spans public web properties, CMS architecture, sales quoting software, CRM workflows, and internal tooling that helps non-engineering teams move faster.
My role sits at the intersection of engineering, demand generation, design, sales, and operations. The job is not just to ship interfaces, but to turn ambiguous business needs into durable systems that support accessibility, content velocity, and revenue workflows.
Role and scope
- Primary engineering owner for marketing and revenue-adjacent web systems.
- Public website, CMS, design system, forms, quoting software, CRM workflows, and related internal tools.
- Cross-functional partner to demand generation, design, sales, revenue operations, and content stakeholders.
- Effectively a one-person engineering team for this surface area, balancing speed, independence, maintainability, and stakeholder alignment.
My ownership
- Translated ambiguous business and operational needs into practical technical plans.
- Owned implementation across frontend, CMS modeling, platform architecture, deployment workflows, and internal integrations.
- Kept accessibility and editor experience central while modernizing the underlying platform.
- Protected confidential workflows by describing internal systems at a high level while still making the engineering scope clear.
Outcomes
- Modernized the public web platform and content operations stack.
- Improved editor quality of life and gave content teams more control without requiring engineering support for every change.
- Created reusable foundations for scanner experiences across public and partner-facing surfaces.
- Used AI-assisted internal tooling to speed up operational workflows in systems teams already use.
Constraints
- Maintained momentum across marketing, sales, CMS, CRM, and internal tooling needs with a very small engineering footprint.
- Balanced public-facing polish with internal workflow requirements and confidentiality boundaries.
- Built around third-party platform limitations when native CMS or integration behavior did not cover the team's real workflows.
Key projects
Systems I owned or helped shape
Platform modernization
CMS Migration and Web Platform Rebuild
Migrated the marketing site from a Gatsby and Prismic stack to a Next.js, Storyblok, Turborepo, and Vercel platform. The migration also created room to refresh the brand and design system, improve deployment workflows, and give editors a more flexible CMS model.
Ownership
Owned the engineering path across the application architecture, CMS modeling, shared UI package extraction, Vercel deployment model, and stakeholder coordination with demand generation and design.
Impact
The new foundation improved maintainability, gave editors better day-to-day quality of life, and helped content operations move faster without sacrificing engineering control.
AI-assisted operations
Custom MCP Servers
Built custom MCP servers for internal HubSpot and Storyblok workflows before first-party options were available. Even after first-party servers emerged, the custom HubSpot work remained useful because the team's account manager and contract workflows needed deeper functionality.
Ownership
Designed and implemented the bridge between AI-assisted workflows and the real systems used by marketing, sales, and operations teams.
Impact
Helped internal teams use AI against practical business workflows while keeping system-specific behavior accurate and controlled.
Specific account, contract, and CRM workflows are intentionally described at a high level.
Reusable product surface
Partner Scanner
Helped create a white-label partner scanner by extracting scanner functionality into a shared package that powers both AudioEye's public website scanner and a separate partner-facing scanner application.
Ownership
Separated scanner logic from a single branded implementation and shaped it into a reusable package that could support multiple scanner experiences.
Impact
Reduced duplication and created a more durable scanner foundation for public marketing and partner-facing use cases.
Localized content operations
AI Translation Layer
Built a custom AI-powered translation layer inside Storyblok so the team could publish localized pages in minutes without adding translation headcount. The system handles complex CMS structures rather than only translating simple text fields.
Ownership
Designed the translation workflow around the actual Storyblok page model, including localized page text, global component swaps, and preservation of editor-friendly CMS patterns.
Impact
Made localization faster and more practical for content teams while working around Storyblok's native translation limitations.
Screenshots and visuals
Public Case Study
The CMS migration has a public AudioEye case study that is safe to link and gives outside context for the platform work.
Open case study(opens in a new tab)Internal Systems
Screenshots of sales, CRM, quoting, MCP, and contract-related systems are omitted or described at a high level to avoid exposing confidential workflows.