Engine engineer
Python engineers who like data that fights back.
What you would work on
Reading Elysium block by block, grouping lookalike tokens, the rules that decide labels, and keeping every label’s evidence checkable.
Careers
Help decide what’s real.
SEAL has no open listings right now. We would still like to hear from people who want to build the verification layer for project launches.
Roles that fit.
Where we expect to need people first.
Integrations engineer
Engineers who like making someone else’s product better.
What you would work on
The API, examples and client libraries, and working with launchpads, wallets and terminals until the label sits where traders decide.
Onchain researcher
People who enjoy finding the trick.
What you would work on
New copy-farm patterns, hard cases checked by hand, and the research reports and case studies that show what SEAL finds.
Developer relations
People who explain clearly and like helping builders get unstuck.
What you would work on
The docs and quickstarts, conversations with builders on X, and bringing what they ask for back into the API.
What the work is like.
The same principles the product runs on.
Evidence first
Every label has to point to something anyone can check. Most of the work is making that true for one more case.
Silence over guessing
When the evidence isn’t there, SEAL says nothing. Building that restraint into software is harder than it sounds.
Show the work
Rules are versioned, changes are dated, and mistakes are written up in the open.
How to get in touch.
No forms with twenty fields.
- Write a short noteWhich role fits you, and what you would want to build first.
- Share your workA link to code, research or writing you have shipped.
- We read itThe team reads every note. If there is a fit, we write back.
- A conversationAn informal call about SEAL, the work and what you are looking for.
Write to us
or message @sealmarkets on X