Opportunities

Open Roles

Fifteen roles across engineering, infrastructure, blockchain and payments, design, legal and growth. Most are remote-friendly, and several are fractional or contract rather than full-time.

Responsibilities

• Own the architecture and the boundaries between modules.
• Make code review a routine part of the week, on both sides of the table.
• Hold the backlog: sequence it, scope it, and know when to say no.
• Own releases: what ships, when, and what the rollback looks like.

Qualifications

• Production Rust on a codebase you did not start, working comfortably with ownership, lifetimes and trait design.
• Confident async Rust with tokio, and a clear understanding of why blocking inside an async context is a bug.
• axum or an equivalent framework (actix, warp, poem), plus a real database layer (sqlx, diesel).
• You have shipped, deployed, and been on call. You know what breaks at 3am.

Nice to have

• A Rust codebase of roughly 20,000 lines that you personally maintained.
• You can explain a design decision and its trade-off in the same breath.
• You ask what the invariants are before writing code.
• You prefer evolving a working system to replacing it.

Responsibilities

• Deliver features independently across the backlog, including the code, the tests and the documentation.
• Work on server-rendered surfaces and the request path.
• Take part in review, and in the design conversations that precede the code.

Qualifications

• Solid Rust, with comfort in async code.
• Able to read maud, or any compile-time templating, without hand-holding.
• SQL fluency.
• A working understanding of HTTP and cookies as protocols, beyond library calls.
• Careful error handling. You notice an unwrap() sitting in a request path.

Nice to have

• Server-rendered applications, extending past JSON APIs.
• Prior work on authentication or sessions.

Responsibilities

• Own deployment and packaging, and the path from commit to running service.
• Run Postgres and Redis: tuning, capacity, and restore drills.
• Own backups, secrets, CI, observability and uptime.

Qualifications

• Real Linux depth.
• Postgres tuning experience, and backup and restore drills you have actually run.
• Container or equivalent packaging experience.
• You treat a backup you have not restored as a hypothesis.

Nice to have

• You have run a small production system on your own.
• You automate first and document second.
• You think in failure modes.

Responsibilities

• Build payment flows, including intents and matching an incoming transfer to the right order.
• Read and act on on-chain transfer events.
• Set and defend confirmation depth, and handle chain reorganisations.
• Keep entitlements correct when the chain changes its mind.

Qualifications

• You have verified on-chain payments in production.
• You know why confirmations exist, and what a chain reorganisation does to an entitlement.
• Familiarity with blockchain RPC endpoints, network fees, and the difference between tokens and native currency.
• You know the difference between a wallet and an account.

Nice to have

• You raise under-payment and over-payment handling before anyone asks.

Responsibilities

• Own the third-party generation service we rely on, from configuration through to live behaviour.
• Build and maintain the internal tooling that keeps our output consistent.
• Evaluate output and hold the quality bar.
• Keep the licensing and provenance records current.

Qualifications

• Real hands-on craft with generation tooling.
• A systematic approach to tuning settings rather than guessing.
• You read terms and licences without being asked.

Nice to have

• You have run a repeatable generation process before.
• You have opinions about which model suits which job.

Responsibilities

• Own the design system and its integrity across the product.
• Design every user-facing surface.
• Take the internal tooling from concept to shipped.

Qualifications

• A real product UI you shipped.
• A systems mindset, and a body of work that shows it.
• You are comfortable writing CSS directly.

Nice to have

• You can critique an existing design system and find its real problems quickly.

Responsibilities

• Own the end-user terms.
• Own the privacy policy and our GDPR and CCPA posture.
• Review model licensing exposure.
• Advise on crypto-payment tax treatment.

Qualifications

• You have done privacy work, with terms drafting as part of the brief.
• Comfort with a business whose pitch rests on data minimisation.

Nice to have

• You ask what we store before you ask what we promise.

Responsibilities

• Own the test suite and CI.
• Extend browser automation across the product's real user journeys.
• Harden verification around our storage and credential flows.

Qualifications

• Headless browser automation, Playwright or similar.
• You treat a test that never fails as decoration.

Nice to have

• You would read our existing end-to-end test and improve it rather than replace it.

Responsibilities

• Build the desktop and mobile clients.
• Own packaging, signing and updates.
• Handle native integration and the parts that touch our core.

Qualifications

• Rust-adjacent systems experience.
• Real client packaging experience. You have shipped something that had to be installed or updated on a machine you do not control.

Nice to have

• Code signing, notarisation, and auto-update failure modes.
• You treat the shipping build as a product surface in its own right.

Responsibilities

• Build and ship one platform's widget surface.
• Work within that platform's lifecycle and review constraints.

Platforms

• WinUI3 (C#/WinRT)
• WidgetKit (Swift)
• GJS (JavaScript)
• QML (Qt)

Qualifications

• Production experience on the platform you are applying for.
• Familiarity with that platform's widget lifecycle.

Nice to have

• You have shipped a widget or extension that passed platform review.
• You will tell us plainly when a platform cannot do something, and what to build instead.

Responsibilities

• Own organic acquisition.
• Own page text, structure, and the pipeline that produces it at scale.

Qualifications

• Working knowledge of programmatic SEO: templating, indexation control, cannibalisation.
• You can tell a genuinely good generated page from a doorway page.

Nice to have

• A site you grew, and a clear explanation of why the pages ranked.
• You can read a crawl report and find the real problem.

Responsibilities

• Own the public API documentation and reference.
• Own key issuance, quota behaviour, and the failure messages developers actually see.
• Run developer relations: onboarding, feedback, and community.

Qualifications

• A public API you built or documented that others integrated without needing a call.
• You write for developers, and the register holds up for that audience.

Nice to have

• You care about error messages and status codes as user experience.
• You have run a changelog or developer newsletter that people actually read.

Responsibilities

• Design, write, and audit smart contracts using Aiken and Plutus.
• Implement token minting policies, multi-asset standards, and on-chain validation logic.
• Work with backend engineers to connect off-chain code to on-chain contracts.
• Ensure contract security, efficiency and correctness through rigorous testing and formal verification methods.

Qualifications

• 2+ years writing smart contracts on Cardano (Aiken or Plutus).
• Strong understanding of the eUTXO model, native assets, and Cardano ledger rules.
• Experience with transaction building libraries (Lucid, Mesh or similar).
• Familiarity with token economics and incentive mechanism design.
• Rust proficiency is a strong plus for off-chain integration work.

Responsibilities

• Build Rust-based backend services that construct, submit and monitor Cardano transactions.
• Integrate with Cardano node APIs or self-hosted indexer services.
• Design and implement off-chain state management and synchronisation with on-chain data.
• Build APIs and services that frontend layers can consume.
• Deploy and maintain the services you build on our own infrastructure.

Qualifications

• 3+ years of backend development experience, preferably in Rust.
• Understanding of Cardano blockchain architecture, the eUTXO model, and transaction construction.
• Experience with async Rust, database systems, and API design.
• Familiarity with Cardano SDKs and transaction building libraries.
• A self-hosted mindset, and the willingness to run what you write.

Responsibilities

• Develop responsive, interactive user interfaces for Web3 applications.
• Integrate Cardano wallet connectivity and transaction signing.
• Build real-time features that interact with blockchain state and backend APIs.
• Work with backend and smart contract engineers to keep data flowing cleanly.

Qualifications

• 3+ years of frontend development experience.
• Expert-level JavaScript/TypeScript, HTML5, CSS3, and a modern framework (React, Vue or Svelte).
• Experience integrating Web3 wallets and blockchain interactions into frontend applications.
• Familiarity with Cardano wallet APIs (CIP-30, CIP-95) is a strong plus.
• A grasp of UX for blockchain applications: transaction states, confirmations, and graceful error handling.