00/Open roles
Build real estate, art and games on Tezos — with us.
We are hiring across full-stack, frontend, backend, blockchain, mobile, AI, design, DevOps and QA — and if you can move the company forward in a way no listing describes, apply as Other. Every role is remote and open worldwide, compensation is set with you rather than for you, and every process ends in a paid evaluation.
01/Platform & Application
Full-stack engineer
The Platform squad ships the surfaces people actually touch: onboarding, the portfolio, quarterly statements, the mint. You would take a feature from a one-paragraph brief to production, including the indexer query and the wallet interaction in the middle.
At a glance
- Squad
- Platform & Application
- Shape
- Full-time, or long-term contract
- Location
- Remote — global, 4h overlap with US Central
- Compensation
- TBD
- Reports to
- CTO
Tech stack
- TypeScript
- React
- Next.js
- Node.js
- PostgreSQL
- Prisma
- Taquito
- Docker
What we genuinely need
- Production TypeScript on both sides of the wire — React on the client, Node on the server — and the judgement to know which side a piece of logic belongs on.
- Relational data modelling in PostgreSQL, including migrations you have run against a live table without taking it down.
- Comfort reading a smart contract's entrypoints and building a product against them, even if you have never written one yourself.
- A habit of shipping small and often, with tests that describe behaviour rather than implementation.
- Clear written communication. Most of our technical decisions are made in documents, not meetings.
What would help, but is not a filter
- Next.js App Router and React Server Components in production.
- Taquito, Beacon, ethers or any other wallet-connection library.
- Regulated-product experience — statements, KYC flows, audit trails.
- Open-source work you can point us at.
Apply
Keep the cover letter short and let the work do the talking — a repository, a portfolio, a system you designed, a bug you are proud of finding. Anything that shows how you think.
02/Platform & Application
Frontend engineer
A wallet signature is irreversible, so the interface in front of it has to be unambiguous. You would own the component system and the pages built on it, working day to day with the designer who sets the visual language.
At a glance
- Squad
- Platform & Application
- Shape
- Full-time, or long-term contract
- Location
- Remote — global, 4h overlap with US Central
- Compensation
- TBD
- Reports to
- CTO
Tech stack
- TypeScript
- React
- Next.js
- Tailwind CSS
- Storybook
- Playwright
- Beacon / Taquito
What we genuinely need
- Deep React and TypeScript, and the CSS to match — layout, motion and responsive behaviour without reaching for a library every time.
- Accessibility as a default: semantic markup, keyboard paths and screen-reader testing, not an audit at the end.
- Performance literacy. You can read a Core Web Vitals report and tell us what to fix first.
- Experience building or maintaining a shared component library used by more than one team.
- A good eye, and the willingness to argue with a designer about an interaction — then build their version well if you lose.
What would help, but is not a filter
- Transaction UX on any chain — pending states, confirmations, failure recovery.
- Data visualisation for financial reporting.
- WebGL or canvas work, for the generative collections.
- Tailwind CSS and the Next.js App Router.
Apply
Keep the cover letter short and let the work do the talking — a repository, a portfolio, a system you designed, a bug you are proud of finding. Anything that shows how you think.
03/Platform & Application
Backend engineer
Chain state is the source of truth, but investors read statements and accountants read reconciliations. You would own the services that turn one into the other — and make sure they agree to the cent.
At a glance
- Squad
- Platform & Application
- Shape
- Full-time, or long-term contract
- Location
- Remote — global, 4h overlap with US Central
- Compensation
- TBD
- Reports to
- CTO
Tech stack
- Go or TypeScript (Node.js)
- PostgreSQL
- Kafka
- Redis
- REST & gRPC
- Docker
- OpenTelemetry
What we genuinely need
- Strong production experience in TypeScript, Go or Rust, building services other teams depend on.
- Data-pipeline discipline: idempotency, replay, back-fills, and knowing what happens when an upstream source reorganises.
- PostgreSQL at depth — query plans, locking, and schema design for append-only financial records.
- APIs designed to stay stable enough for outside integrators to build on.
- Operational ownership of what you ship: the metrics, the alerts and the on-call rotation that comes with them.
What would help, but is not a filter
- Blockchain indexing on any chain — Tezos, EVM or otherwise.
- Fund administration, payments or ledger-system experience.
- Event sourcing in production.
- Smart-contract work in LIGO, SmartPy, Solidity or Rust.
Apply
Keep the cover letter short and let the work do the talking — a repository, a portfolio, a system you designed, a bug you are proud of finding. Anything that shows how you think.
04/Protocol & Contracts
Blockchain engineer
Everything we tokenize lives in a contract, and a bug in one of ours costs an asset rather than an image. You would join the squad that owns every contract we deploy: the FA2 issuance behind property and Editions, the escrow and royalty logic of the NFT marketplace, and the move of our games' settlement onto Tezos.
At a glance
- Squad
- Protocol & Contracts
- Shape
- Full-time, or long-term contract
- Location
- Remote — global, 4h overlap with US Central
- Compensation
- TBD
- Reports to
- CTO
Tech stack
- Michelson
- LIGO (JsLIGO)
- SmartPy
- Taquito
- Octez
- TzKT
- Solidity & Hardhat
What we genuinely need
- Smart contracts shipped to a mainnet — on Tezos, or on an EVM chain with the discipline to learn Michelson's stack model quickly.
- Security-first habits: threat models written before code, property-based tests, and an audit you have been through without surprises.
- A working understanding of token standards — FA2 / TZIP-12 on Tezos, or ERC-721 / ERC-1155 on EVM — and why transfer hooks matter.
- TypeScript fluent enough to build the off-chain half: deployment scripts, indexer queries and the client calls against your entrypoints.
- Clear written specifications. Our contracts are designed in documents and reviewed before a line is written.
What would help, but is not a filter
- Formal verification — Coq, Mi-Cho-Coq, K or similar.
- Marketplace mechanics: listings, offers, auctions and on-chain royalty enforcement.
- Commit–reveal, VRF or mental-poker protocols for provably fair games.
- Contributions to the Tezos ecosystem — tooling, TZIPs or open-source contracts.
Apply
Keep the cover letter short and let the work do the talking — a repository, a portfolio, a system you designed, a bug you are proud of finding. Anything that shows how you think.
05/Mobile — new squad
Mobile engineer
Most of our collectors and players arrive on a phone, and today they meet a responsive website. You would be the first mobile hire: one cross-platform app for holders, collectors and players, built on the same APIs and design system as the web, with native modules where a wallet or a game loop needs them.
At a glance
- Squad
- Mobile — new squad
- Shape
- Full-time, or long-term contract
- Location
- Remote — global, 4h overlap with US Central
- Compensation
- TBD
- Reports to
- CTO
Tech stack
- React Native
- Expo
- TypeScript
- Swift
- Kotlin
- Beacon / WalletConnect
- Fastlane
What we genuinely need
- Apps shipped to both the App Store and Google Play, including the review process and the release after the first one.
- React Native in production, with enough Swift or Kotlin to write a native module when the bridge is not enough.
- Secure storage, biometrics and deep links handled properly — the building blocks of a wallet connection people can trust.
- Offline-aware state management and performance profiling on real mid-range devices, not just the simulator.
- The judgement to keep one design system across web and mobile rather than building a second product.
What would help, but is not a filter
- Wallet integrations — Beacon, WalletConnect or an embedded wallet SDK.
- Mobile game or real-time experience — WebSockets, animation, canvas.
- App-store policy knowledge for digital collectibles and in-app purchases.
- Push notifications and analytics pipelines you have set up yourself.
Apply
Keep the cover letter short and let the work do the talking — a repository, a portfolio, a system you designed, a bug you are proud of finding. Anything that shows how you think.
06/AI & Data — new squad
AI engineer
A property acquisition arrives as several thousand pages of title, survey and lease documents; an artwork arrives with a folder of letters and invoices. You would build the tools that turn both into a structured record, and the evaluation harness that proves they got it right.
At a glance
- Squad
- AI & Data — new squad
- Shape
- Full-time
- Location
- Remote — global, 4h overlap with US Central
- Compensation
- TBD
- Reports to
- CTO
Tech stack
- Python
- TypeScript
- LLM APIs
- pgvector
- PyTorch
- FastAPI
- Evaluation harnesses
What we genuinely need
- LLM-backed features shipped to production, including retrieval, structured extraction and tool use.
- Evaluation as a first-class deliverable — golden sets, regression suites and error analysis you can explain to a non-engineer.
- Strong Python or TypeScript, and the engineering habits that keep model code maintainable after the demo.
- A clear-eyed view of where models fail, and product designs that keep a human reviewer in the loop where it matters.
- Care with sensitive data: PII handling, access controls, and knowing what must never leave our infrastructure.
What would help, but is not a filter
- Document AI — OCR, layout parsing, legal or financial documents.
- Fine-tuning or distilling smaller models for narrow tasks.
- Classical ML for valuation or anomaly detection.
- Agent frameworks, and the discipline not to use one when a function will do.
Apply
Keep the cover letter short and let the work do the talking — a repository, a portfolio, a system you designed, a bug you are proud of finding. Anything that shows how you think.
07/Editions — Art & Design
Product designer
Our visual language is currently set by the property programme by default, and Editions has been art-directed by people whose job is something else. You would own the design system, the product flows built on it, and the artwork surfaces across the games estate.
At a glance
- Squad
- Editions — Art & Design
- Shape
- Staff, or long-term contract
- Location
- Remote, or Austin
- Compensation
- TBD
- Reports to
- Director of Editions
Tech stack
- Figma
- Adobe Creative Cloud
- Blender
- Rive
- Protopie
- Prototyping in code
What we genuinely need
- A portfolio of shipped product work with a point of view we can describe after looking at it. Volume is not the signal; coherence is.
- Systems thinking: a component library, a type scale and a grid that hold up across three very different products.
- Command of typography and layout — collection pages, certificates, statements and the mint flow are all yours.
- Interaction design for high-stakes actions, where a confirmation screen is the last line of defence before an irreversible transaction.
- Comfort working directly with engineers, including being told that something will not fit on-chain and having a second idea ready.
What would help, but is not a filter
- NFT, fintech or collector-facing product experience.
- Motion design, for the moving-image collections and the games estate.
- Illustration or generative work — the fifteen Elemental RPS Arena reward tiers and the Twenty-One Showdown characters are ours to keep refining.
- Physical output experience: print, plotter, risograph. Half of what we release ends up on paper.
Apply
Keep the cover letter short and let the work do the talking — a repository, a portfolio, a system you designed, a bug you are proud of finding. Anything that shows how you think.
08/Infrastructure
DevOps engineer
We run our own Tezos nodes, indexers and signing infrastructure, because a third-party outage cannot be the reason a distribution is late. You would own that estate, the CI/CD around it, and the security posture of everything that holds a key.
At a glance
- Squad
- Infrastructure
- Shape
- Full-time
- Location
- Remote — global, 4h overlap with US Central
- Compensation
- TBD
- Reports to
- CTO
Tech stack
- Terraform
- Kubernetes
- AWS
- GitHub Actions
- Prometheus & Grafana
- HashiCorp Vault
- Octez
What we genuinely need
- Infrastructure as code in production — Terraform, Pulumi or similar — on at least one major cloud.
- Kubernetes or an equivalent orchestrator, run by you rather than by a platform team you filed tickets with.
- Observability you designed rather than installed: metrics, logs, traces and alerts that page for the right reasons.
- Secrets and key management with the paranoia appropriate to infrastructure that signs financial transactions.
- Incident-response experience, including writing the blameless post-mortem afterwards.
What would help, but is not a filter
- Running blockchain nodes or bakers on any network.
- HSM or cloud-KMS signing setups.
- SOC 2 or ISO 27001 evidence collection.
- Cost management at the scale where it becomes a line item someone asks about.
Apply
Keep the cover letter short and let the work do the talking — a repository, a portfolio, a system you designed, a bug you are proud of finding. Anything that shows how you think.
09/Quality
QA engineer / tester
Our contracts are formally verified; the software around them is not. You would own the test strategy for the portal, the mint and the games: exploratory testing on every release, and the automated suites that stop a regression reaching production twice.
At a glance
- Squad
- Quality
- Shape
- Full-time, or long-term contract
- Location
- Remote — global, 4h overlap with US Central
- Compensation
- TBD
- Reports to
- CTO
Tech stack
- Playwright
- TypeScript
- Vitest
- Postman
- k6
- Tezos testnets
What we genuinely need
- Experience testing web applications end to end, with a genuine instinct for the edge case nobody wrote down.
- Test automation in Playwright, Cypress or similar, maintained well enough that the team trusts a red build.
- Clear, reproducible bug reports — steps, expected, actual, evidence — that an engineer can act on without a follow-up call.
- API testing, and reading enough code to understand what actually changed in a release.
- Patience with money-moving flows: wallets, testnets, pending transactions and every way they can fail.
What would help, but is not a filter
- Testing blockchain applications or wallet integrations.
- Accessibility testing with screen readers.
- Performance and load testing.
- Experience in regulated or financial products.
Apply
Keep the cover letter short and let the work do the talking — a repository, a portfolio, a system you designed, a bug you are proud of finding. Anything that shows how you think.
10/Any squad
Other — open application
Some of our best people did not fit a listing when they arrived. If you build games, grow communities, close partnerships, research protocols or have an idea we have not had, apply here and describe the role in your own words. We read every one and reply to every one.
At a glance
- Squad
- Any squad
- Shape
- Full-time, contract or advisory
- Location
- Remote — global
- Compensation
- TBD
- Reports to
- Depends on the role
Tech stack
- Whatever the work needs
What we genuinely need
- A concrete answer to one question: what would you do here in your first ninety days?
- Evidence of work you have done — a link, a project, a result — rather than a list of titles.
- Genuine interest in real estate, art, games or blockchain, and in what Tezos makes possible for them.
What would help, but is not a filter
- Game design, economy design or live-ops experience.
- Community management across Discord, Slack or Telegram.
- Business development, partnerships or investor relations.
- Research in cryptography, mechanism design or tokenization law.
Apply
Keep the cover letter short and let the work do the talking — a repository, a portfolio, a system you designed, a bug you are proud of finding. Anything that shows how you think.
11/Process
Five steps, about three weeks
The same shape for every role. Tomás Guerrero runs all of it — you will not be passed between recruiters or asked to repeat your background to five different people.
Blockchain, full-stack or backend, and want to take on the poker project? Its paid evaluation is published in full.
Introduction
Forty-five minutes with Tomás. Your background, which role fits you best, and your questions about us. No whiteboard.
Role conversation
Ninety minutes with the person you would report to. We go through work you are proud of and a real problem from the role you applied for.
Paid evaluation
A scoped slice of real work in your discipline — a feature, a design brief, a pipeline, a test plan. Ten calendar days, and we pay whether or not we proceed.
Review & debrief
You walk two people through what you made and why. You receive written feedback in every case, including rejection.
Offer
Commercial terms, a start date, and your first piece of work — which will already be waiting.
12/Questions
The things candidates actually ask
Which role should I apply for?
The one closest to the work you want to be doing in a year, not the one closest to your current title. If you sit between two — full-stack and backend is the common case — pick either and say so in your cover letter. Tomás reads every application himself and will move it if another role fits better. If none fits, use Other and describe the role in your own words.
Can I apply for more than one role?
Yes, but send one application and name both roles in it. We would rather have one clear application than three near-identical ones, and you will only go through the process once.
Are the roles remote?
Every role is remote and open worldwide. Most ask for about four hours of overlap with US Central, because code review and incident response need real overlap. The designer seat can also be taken from a desk in Austin if you would like one.
Do I need blockchain or Tezos experience?
Only for the blockchain engineer role. It helps for backend and DevOps, but strong people who have never touched a chain pick up what they need in the first few weeks, and we fund the time to do it. What we screen for is the discipline — correctness, ownership, clear writing — not the ecosystem.
Why does every listing say compensation is TBD?
Because we hire worldwide and set each package against the candidate's region and seniority rather than publishing one number that fits nobody. We discuss the range openly in the first conversation, before you spend any time on the evaluation.
What is the paid evaluation?
A narrow, representative slice of the role you applied for: a small feature for full-stack and frontend, a pipeline problem for backend, the poker test project for blockchain, a small wallet-connected screen for mobile, an extraction-and-evaluation task for AI, a design brief for the designer, an infrastructure exercise for DevOps, and a test plan against a staging build for QA. Ten calendar days, and we pay for it whether or not we make an offer.
Is the paid evaluation real work you'll ship?
No. Every brief is deliberately narrowed so that it is representative but not useful to us. We pay for it because your time has value, and the work stays yours — publish it, reuse it, put it on your GitHub.
Full-time or contract?
Most roles are open to both, and each listing says which. The AI and DevOps roles are full-time only, because both involve access to systems and data we are not comfortable handing to someone on a short engagement.
Can I use AI tools in the evaluation?
Yes — it is fine and expected. Tell us what you used. You will be asked to defend every decision in the review, so do not submit anything you cannot explain.
What happened to the poker project?
It still needs an owner. The specification, the reviewed architecture and the exploratory contract work are all still there. If you are applying as a blockchain, full-stack or backend engineer and want to take it on, say so at the introduction — the paid evaluation for that path is the poker test project, published in full.
I am an artist, not a designer. Can I still work with you?
Yes, and that is a different door. The Editions programme takes submissions year-round and about one in forty becomes a collection; the terms are published on the art page rather than negotiated in private, and they do not change based on how well known you are. Write to the Editions address with work rather than a proposal.
13/Apply
Apply in about ten minutes
One form for all 10 openings, including Other. It goes straight to the hiring inbox, and Tomás reads every application himself.
You apply
Role, contact details, a short cover letter and your resume.
A 45-minute introduction
With Tomás — your background and your questions. No whiteboard.
A paid evaluation
A scoped slice of real work, paid whether or not we proceed.
Written feedback, either way
Everyone who completes the evaluation hears exactly why.
Apply
Send us something real
Use the form above for any of the 10 roles, or write to us directly. Artists who want to be in a collection rather than to design one should write to Editions instead.
Everyone who completes a paid evaluation receives written feedback