How we’re organized
Poly Syncer is a small, distributed company — fourteen people across six time zones — and the leadership team is three people. Each of us owns a vertical end to end. Eli runs editorial, partnerships, and the public face of the company. Maria runs quantitative research: the wallet-scoring composite, the Sharpe adaptation, every model we ship. Jamal runs engineering: the listener, the execution path, the RPC fleet, and the on-call rotation. We hold a sixty-minute leadership review every Monday and otherwise stay out of each other’s way.
We publish bios because trust in a non-custodial trading system is a function of who built it. If you are going to delegate sub-second execution decisions to our infrastructure, you should know our backgrounds, our priors, and what we’ve shipped before. Each profile below links to a longer page with credentials, prior roles, and recent writing.
Founder & Editor-in-Chief
Eli Marsh
Eli is the founder and editor-in-chief of Poly Syncer. He spent six years as a quantitative trader at a Chicago proprietary trading firm before transitioning to research, where he covered prediction markets full time and has been writing about Polymarket since early 2023.
Read Eli’s bio →Head of Quant Research
Maria Ostrowski
Maria leads quantitative research. She holds a PhD in Statistics from the London School of Economics and spent seven years between an HFT firm and a London betting-exchange research team. She owns the wallet-scoring composite and the Sharpe adaptation we ship in production.
Read Maria’s bio →Head of Engineering
Jamal Okafor
Jamal leads engineering. He was a staff engineer at a top-five crypto exchange where he led on-chain settlement, and previously shipped low-latency systems in fintech payments. He owns the execution engine: the co-located node, the MEV-protected order path, and the RPC fleet.
Read Jamal’s bio →How we hire
We hire slowly and almost exclusively through referrals or open-source contributions. Every engineer on the team has shipped production trading or settlement code somewhere with real money on the line. Every researcher has a publication record or a track record at a quant fund. We do not have product managers, growth marketers, or a sales team. We do have an in-house counsel on retainer and a fractional CFO.
If you’re curious about open positions, the careers page lists what is currently open. We post roles only when we genuinely have one to fill, which means the page is empty more often than not.
How we work
The company runs on three documents: the whitepaper, the methodology page, and an internal engineering handbook. The whitepaper is the public spec for the system — how trades are mirrored, how risk is bounded, what the user contract looks like. The methodology page is the public spec for the research — how wallets are scored, how Sharpe is adapted, how outliers are shrunk. The engineering handbook is internal and covers everything from on-call expectations to deployment cadence.
We ship continuously. The changelog documents every meaningful release, and the status page publishes p99 latency and uptime in near real time. When something breaks, the post-mortem appears on the changelog within two business days.
Editorial standards
Eli is the byline on most posts on the blog. Maria is the byline on research-heavy posts — anything involving statistical methodology, the wallet-scoring composite, or position-sizing math. Jamal occasionally writes on the engineering side: MEV protection, RPC infrastructure, anything where the implementation detail matters more than the conceptual framing. Every post is reviewed by at least one other team member before publication, and material updates are dated on the post itself.
We do not accept paid placements, sponsored posts, or affiliate links anywhere on the site. Subscription revenue from Pro and Elite is the only way the company makes money.
Contact
The fastest way to reach the team is the contact page. Press inquiries can use the same form — flag the message as press and Eli will respond directly. For security disclosures, the security page lists a dedicated PGP-encrypted address.