Customer Engineer in AI ecommerce startup (Magento/Adobe stack)

⚡ About Tellis Tellis is an AI-native product data enrichment platform for ecommerce brands. Large product catalogues leak revenue. Turning a spec into a live product page takes weeks. Most teams only have bandwidth to polish their top 20% of SKUs, and thin or messy data across the rest costs brands millions a year in lost sales, returns, and compliance issues. With the rise of agentic commerce, this problem is now urgent: if merchants' product data isn't AI-ready, they become invisible to shopping agents like ChatGPT Shopping and Google AI Mode. Tellis is a team of AI agents that sits on top of a merchant's stack, turning siloed shopper signals into enriched, validated product data at scale, pushed straight into the client's CMS or PIM. We're building the AI shopping context layer that makes every product discoverable and conversion-ready for the AI shopping era. We're a VC-backed, pre-seed startup with paying customers in the UK, founded by ex-Google and second-time founders. 🧑‍💻 The role You’ll be our first Customer Engineer, working directly with clients to deploy Tellis on their catalogueues. Each client brings different data sources, tools, and use cases — your job is to make Tellis work for them, fast. You'll own a small set of merchants end to end: their catalogue, their configuration, their results, and the Magento integration underneath. This is not support and it is not consulting. You connect the store, decide how Tellis should reason about that catalogue, run the generation cycles, and judge the output. When something doesn't fit, you change it yourself: configuration when that's enough, a pull request against the product code when it isn't. Because you sit closest to the customer, what you learn materially shapes what gets built next. We're not looking for a solutions consultant who can't debug, or an engineer who won't take the call. Concretely, you will: - **Onboard new clients**: ingest, clean, and map their catalogue data, and own the process from connection through to published content - **Configure how Tellis handles each catalogue**: quality policies, generation prompts, category and attribute mapping, publishing rules - **Build on the Magento integration itself** — the connector, field mappings, catalogue sync and write-back path — shared with the platform side and increasingly yours - Run generation cycles, review drafts across categories, and tune until the output is genuinely on-brand - **Add integrations for sources specific to your accounts** — a bespoke PIM, an ERP, a scheduled feed - Sit in client calls, understand what they actually need, and translate it into working configurations - **Feed what you learn back into the product**: spot the patterns across deployments and work with our CTO to turn repeated custom work into platform features That last point is half the job. We're not hiring someone to absorb custom work forever — we're hiring someone to help make each deployment cheaper and better than the last. This is the way into owning the Customer Solutions function at Tellis. As our book of business grows, the first customer engineer on it becomes a leader who can translate technical asks from the clients into a scalable and repeatable product engine. ✅ Must have - 2+ years Magento/Adobe Commerce integration engineering. Attribute sets, configurable vs simple, category trees, url_key and suffix conventions, custom attributes, idempotent write-back — and what the APIs won't let you do. - Strong data skills — SQL, Python, wrangling messy real-world catalogue data. - Built with LLMs in production — prompt design, agent workflows, evaluation. - You ship with coding agents (Claude Code, Codex or equivalent). You know what to hand over, how to review what comes back, and when it's faster to write it yourself. - Can sit in front of a client without a founder in the room. - Comfortable with ambiguity — priorities shift weekly at our stage, and you find that energising. ❇️ Nice to have - Ecommerce or digital marketing background — you know your way around GA4, GSC, GMC, product feeds - Merchandising instinct — you can look at a PDP and say why it converts, and judge whether generated copy is right for a given retailer - Shopify or BigCommerce API experience - Startup experience, or evidence you've shipped things without being told how 🎁 What you get - Ground-floor role at a funded startup with early revenue and a clear thesis - Direct work with founders and clients — no layers - Competitive compensation (depends on experience) - Clear ownership and opportunity to expand responsibilities - Remote work arrangements How to apply Please tell us about the biggest catalogue-related challenge you faced and how you eventually solved it.