About Poly Syncer
Poly Syncer delivers prediction market copy trading by mirroring the trades of profitable Polymarket wallets for our subscribers, in seconds, without holding their funds. The heart of the product is not the listener and not the executor — it is the policy layer that sits between them. The policy layer is where we encode what we will and will not copy, what we will and will not size up, and what we will warn subscribers about before letting their capital touch a market. The manifesto covers our posture. The whitepaper covers the architecture.
The role
You will own the policy layer. That means: defining the framework for what we mirror — by market type, by leader behavior, by liquidity profile, by venue; defining the limits that protect subscribers from leader misbehavior, including the kill-switches that stop a wallet from being copied within seconds of a signal trip; defining the disclosure language that makes those decisions legible to subscribers in product; and, when we get a decision wrong, defining how we explain the change in the changelog.
This is not a paper-policy role. We expect policy as code, not policy as PDF. The decisions that govern the executor are versioned, code-reviewed, and tested the same way the executor is. You will work hand in hand with the engineering and quant teams. You will write specifications that engineers can implement directly, you will read the diffs that implement them, and you will have explicit veto power over any product decision that trades subscriber safety for growth metrics. You will report directly to the CEO.
Year-one priorities: ship a written risk framework that we can publish externally; tighten the leader de-listing pipeline (current latency from signal to de-list is two hours; target is fifteen minutes); design the cross-venue limit framework for the Q3 routing layer; and hire the second risk seat in late year-one.
You'll be a fit if
- You have senior experience in trading risk, exchange risk, or quantitative compliance — at a real venue or a serious trading firm. We will check references hard on this one.
- You think in policy-as-code terms, not memo-as-policy terms. You can write a spec that an engineer implements without ambiguity.
- You have a documented track record of saying no to product features that traded user safety for growth, and the receipts to prove it.
- You can write clearly for a general audience. Subscribers need to understand the policies that govern their capital, in plain English, on the public site.
- You read code. Solidity and Python at minimum; ideally enough Go or Rust to read the executor.
- You are comfortable being the senior voice in the room when senior is not the loudest. The CEO will back your veto; you should be willing to use it.
- You have shipped at least one limit framework that survived a real adverse event. Your story about that event will tell us most of what we need to know.
Bonus points
- You have led risk at a crypto exchange, derivatives venue, or a market-making firm during a crisis.
- You have written a public risk framework that has been picked up by other firms.
- You have a working relationship with regulators in at least one of the EU or US.
Process
- Intro call (60 min). A direct conversation with the CEO covering the role, your background, and your views on risk in our setting.
- Reference check. Three references at firms where you have led risk. We do this before the take-home, not after.
- Paid take-home (10–14 hours, $2,000). A written framework for a real open question on our backlog. You keep the work and the IP regardless of outcome.
- Final round (half-day). Conversations with the CEO, the head of engineering, the head of research. Offer within five business days.
Compensation
$200k–$260k base + meaningful equity. Equity vests over four years with a one-year cliff. The seat is senior; the compensation reflects it. We pay top-tier health coverage in your home country, fund a co-working stipend, and cover a quarterly off-site. The role carries an annual performance component tied to risk-event outcomes — not to revenue.
Location
Remote-first, HQ Stockholm. The role requires at least four hours of overlap with European working hours and quarterly travel to Stockholm for senior-team off-sites.
How to apply
Email [email protected] with a short note covering one risk decision you led where the right answer cost the company growth. We want to know how you reasoned about it and how it played out.
For posture, the manifesto is the canonical document. For technical context, the whitepaper and the methodology page. For team background, the about page.