Customer Engineer

What you own

• Onboarding, integration debugging and technical support for merchants.
• The installable store systems: tracking, AEO, CRO and vitals.
• Turning a broken pixel into a fix in the product, not a workaround in a ticket.

Your perimeter in the codebase

You own the commerce-systems pillar. In this repository that means, literally, these paths:

• src/features/tracking/**
• src/features/aeo/**
• src/app/(minimal)/scan/**

Stack

• TypeScript
• Prisma + Neon Postgres
• Zod

How we build

BoostEcom is split into 12 ownership pillars, and an AI agent fleet ships most of the volume: 6 product agents run the merchant side, coding agents open one pull request per backlog item per pillar. The platform runs 386+ API route handlers, 64+ scheduled jobs and 6 locales. Every push runs the full test suite before it leaves your machine.

What we look for

• You have supported technical users on a real product.
• You can read a network waterfall and a Liquid theme.
• You write the doc right after you answer the question.

How hiring works

You send one message saying what you have built. The founder answers personally. If it fits we talk for an hour, then we do a small paid piece of real work together and decide from it. No exercise before we have spoken, no interview panel, no six-week loop.