Engineer · Storefront automation

A cross-border seller repeats the same set of actions every day across several platforms: listing, repricing, restocking, replying to messages, running ads. None of it is hard on its own. What is hard is that it is spread across platforms with different APIs, different rate limits and different failure modes — and it has to be reliable, because getting it wrong once costs real money.

This role makes those actions into automation that holds. The toolchain on this line already runs on real merchants' storefronts; what you change is in someone's hands the same day.

What you will do

• Fix what real use exposes — not a hypothetical on an issue list, but the thing a merchant is stuck on today
• Add capability against real demand: a merchant says "I still have to click this step myself", and you take that step away
• Finish the publishing path: merging products inside the system, pushing to each platform, through to production
• Work against the platforms' official APIs — rate limits, idempotency, rollback on failure. These are the parts you do not get to skip

What we look for

• Solid engineering fundamentals; code that stays maintainable, not just code that runs
• Fluency with tools like Claude Code. A requirement, not a bonus point — our engineering team works at this size because every person's output is amplified
• You learn fast. The business keeps moving; a year from now this job is probably not the same job. That is what we screen for, not what you already know
• Willingness to face the user directly. You will know who uses what you write, and hear where they get stuck
• An obsession with reliability. This system moves other people's money, and one silent failure is worse than ten small bugs