An application made for this job — a tailored resume and cover letter that speak straight to the posting.
SELLIT9 is seeking an engineering leader to design schemas, build APIs, ship UI, and operate production systems on GCP. You will own the product questions behind your work, turning them into specs and end-to-end solutions that move metrics.
You will sit between product, design, and engineering, owning tickets and shaping the design system in code while delivering for both people and AI agents. You will extend agent surfaces and automateoperations with agents.
This is an engineering role first. You'll design schemas, build APIs, ship UI, and operate production systems on GCP, and you'll be judged on the quality of what you ship. On top of that foundation you'll own the product side of your work too: you'll take a product question ("why did this model stop converting?"), turn it into a spec, build it end to end, and watch the metric move. A recent example: our market-prices system, where one engineer owns everything from the scraper data contract to the calibration report that tells us when a rival outbids us.
The role sits deliberately between product, design, and engineering. There's no separate PM writing your tickets. Our design system lives in code, so you'll make the design calls and ship polished UI without waiting for a handoff. And you'll build for two kinds of users: people and AI agents. Our trade-in flow already runs inside Claude through our MCP connector, and a growing share of our operations run as agent workflows the team writes as skills.
A note on AI-native: AI multiplies engineering skill, it doesn't replace it. You need the depth to review, correct, and own everything an agent writes, because you could have written it yourself. Vibe coding doesn't survive contact with a production pricing system.