This is a foundational role — the first engineer of its kind here, on a product early in its life. There is a large amount of ground to clear and no established playbook. You'll define the discipline as you build it. The people implementing on our new platform — developers at agency partners in most cases, in-house teams at direct customers in others — are building design systems and websites and connecting those sites to third-party services: commerce platforms, identity providers, analytics, search, consent management, industry-specific backends. Your job is to make that work easier. Not by doing it for them — we provide the materials so clients can do it themselves. "Materials" is deliberately broad: documentation and guides, scripts, AI skills, connectors, reference implementations, and example widgets with integrations already built in (which are really just reference implementations in another form). How the work arrives: our sales engineer learns that a client is about to implement against a particular system — say, BigCommerce. You, the SE, and the client then work out the list of materials that would make that implementation easier, and you build them. The one-off then becomes reusable: what you built for one client's BigCommerce integration is the starting kit for the next one. The mix of writing versus coding will shift over time. Early on, it's probably more writing — guides and documentation — with the coding share growing as patterns repeat and reference implementations accumulate. We honestly don't know the long-run split, which is why we need someone genuinely strong at both.
Stand Out From the Crowd
Upload your resume and get instant feedback on how well it matches this job.
Job Type
Full-time
Career Level
Entry Level
Education Level
No Education Listed