About Poly Syncer
Poly Syncer is a non-custodial Polymarket bot for copy trading. The product surface is dense — leaderboards, strategy composers, real-time fills, allocation editors — and the users are sophisticated. They do not need hand-holding. They do need a product that respects their attention. The manifesto covers our posture; the about page covers the team.
The role
You will be the second designer at Poly Syncer, working alongside the founding designer with broad ownership over the visual system, the interaction patterns, and the dense data displays that make this product readable. The first major project is a redesign of the strategy composer — the surface where a subscriber decides which leader wallets to follow, at what allocation, with what risk caps. The current version works. The next version needs to make the system legible to a trader who has never used Poly Syncer before, while not getting in the way of the trader who has used it for two years.
Beyond the composer, you will own iterations on the leaderboard (currently the most-trafficked surface on the site), the trade-history dashboard, and the new mobile companion. You will work directly with engineering — there is no PM intermediation layer — and your designs will ship. We expect roughly one substantial release a quarter, and you will be the design lead on at least two of them.
This is a role for a designer who reads code. Not because we expect you to write production code, but because the design decisions on a trading product are inseparable from the system that delivers the data. If you do not understand why an order-book update arrives in batches, you will design a UI that pretends it does not. We have one designer today who happily does this; you would be the second.
You'll be a fit if
- You have a portfolio of shipped product work in fintech, trading, data-heavy SaaS, or a comparable surface where information density matters.
- You are fluent with Figma component systems — building them, maintaining them, and pruning them when they grow stale.
- You have a sensible eye for typography. Our type ramp does real work; please do not break it.
- You are willing to read order-book code and ask questions until the answers make sense, so your designs reflect what actually happens.
- You can prototype interactions in code or in Figma. We do not care which, but we expect ideas to be shown, not described.
- You write design rationale in plain prose. Why a decision was made matters as much as what was decided.
- You have shipped at least one mobile-first or mobile-companion experience.
Bonus points
- You have used Poly Syncer yourself, or you have used a competitor and have an opinion about it.
- You have experience with motion design for data-heavy UIs.
- You have shipped a design system that survived a team scaling from 5 to 25 engineers.
Process
- Intro call (45 min). A conversation with the head of product and the founding designer.
- Portfolio review (60 min). You walk us through three projects in depth — what shipped, what did not, what you would do differently.
- Paid design exercise (8–12 hours, $1,200). A scoped redesign of one screen from our current product. You keep the work and the IP regardless of outcome.
- Founder call + offer (60 min). Compensation, equity, and the values. Offer within five business days.
Compensation
$140k–$190k base + meaningful equity. Equity vests over four years with a one-year cliff. We pay top-tier health coverage in your home country, fund a co-working stipend, and cover a quarterly off-site.
Location
Remote-first. HQ is in Stockholm with desks for anyone who wants one. We hire across EU and US time zones with at least four hours of overlap with European working hours, so design and engineering can do live reviews together.
How to apply
Email [email protected] with a link to your portfolio and a short note on which surface in the current Poly Syncer product you would attack first. We respond to every application.
For company background, see the about page and the team page. For posture, the manifesto is the canonical document. For a sense of how the engineering team thinks about the surfaces you would be designing, the methodology page covers the data flow that ends up in front of subscribers.
One last note: the existing design system is documented internally in Figma but it is not precious. If your first month surfaces three things you would change, we want to hear them. The second designer sees what the first designer is too close to see. That is the point.