wallionDownload

Careers at Wallion

Good work.
Real ownership.

Bring your craft to the way people move through crypto. Help turn complex technology into a wallet that feels clear, considered and human.

Explore open roles

Global remote. A shared ambition.

Two illustrated hands assemble Wallion’s opposing brackets, bringing different skills together.

Behind the experience

A simple action.
A team’s worth
of thinking.

A transfer can take one tap. Making that tap understandable means asking the right questions together: what does the person see, what does the network do, and what exactly have they authorized?

Design

Turn an amount, a network and a fee into a decision someone can understand at a glance.

Engineering

Handle changing fees, slow networks and interrupted requests without losing track of the transaction.

Security

Trace what a signature can authorize, which assets it can reach and where that access ends.

How we approach the work

Care about the details.
See the whole picture.

01

Start with
a real problem.

A useful feature begins with something a person is trying to do. Trace the confusion, question the assumption and define what a better outcome would look like.

02

Make your
thinking visible.

Share the constraints and alternatives alongside the solution. A small prototype, a clear technical note or a concrete example gives other disciplines something useful to challenge.

03

Follow it
all the way through.

The first version is a starting point. Consider slow networks, interrupted sessions and unclear outcomes. Bring what you learn back into the next decision.

Working across time zones

Leave context
someone can use.

In a remote team, the next person may pick up a task while you are offline. A useful handover lets them continue without reconstructing the conversation that came before it.

The current state

Identify the version under discussion and what is ready to use. Link to the relevant design, code or document so an old draft does not become the starting point by accident.

The open decision

State the question that remains, who needs to answer it and which part of the work depends on that answer. Separate a request for input from a decision already made.

The next move

Make the next action and its owner clear. If the work is blocked, include what would unblock it and what can still move forward independently.

Find your place

What do you want
to make yours?

10OPEN ROLES

10 roles shown

01Senior Blockchain EngineerEngineering · Global remote · Full-time$160k – $224k / yearUSD · Base compensation02Mobile App Engineer iOS / AndroidEngineering · Global remote · Full-time$165k – $229k / yearUSD · Base compensation03Security EngineerEngineering · Global remote · Full-time$230k – $274k / yearUSD · Base compensation04Product Manager Web3Product & Design · Global remote · Full-time$164k – $221k / yearUSD · Base compensation05UX / Product DesignerProduct & Design · Global remote · Full-time$132k – $184k / yearUSD · Base compensation06DevOps / Infrastructure EngineerEngineering · Global remote · Full-time$165k – $229k / yearUSD · Base compensation07Growth & Partnerships ManagerGrowth & Community · Global remote · Full-time$165k – $222k / yearUSD · Base compensation08Community & Education LeadGrowth & Community · Global remote · Full-time$150k – $207k / yearUSD · Base compensation09Marketing ManagerGrowth & Community · Global remote · Full-time$134k – $191k / yearUSD · Base compensation10Product & Ecosystem AdvisorAdvisory · Global remote · AdvisoryDiscussed individuallyCompensation

Your introduction

Show us
how you think.

The work you choose and the reasoning behind it tell us more than a long list of tools. Bring an example that helps us understand your contribution.

  1. 01

    Choose a piece of work.

    Explain the problem, what you owned and what changed because of your work. A repository, case study or portfolio gives the story context.

  2. 02

    Include the difficult part.

    A rejected approach or a result that surprised you can reveal a lot. Tell us what you learned and what you did differently.

  3. 03

    Add the practical details.

    Include your country, time zone and the role that interests you. Share work you have permission to discuss; confidential files are unnecessary.

Your questions matter too

Understand the work.
Assess the fit.

Use the role’s outcomes and collaboration details to prepare a conversation about the work itself. These questions can help you explore what the responsibility would mean in practice.

Which decisions would I own?

Clarify where the role can make a decision, where another discipline needs to contribute and who resolves a disagreement across those boundaries.

What does the work depend on?

Ask about the information, systems or partner teams an outcome relies on. Understanding a dependency makes the scope of the role easier to assess.

How would we recognize progress?

Discuss the evidence that would show an improvement and the constraints around it. An outcome in a role brief is a useful starting point for that discussion.

Product & ecosystem advisory

Experience that
opens a new angle.

Help sharpen product priorities, challenge wallet and agent assumptions, and assess ecosystem partnerships. Bring operating experience and a perspective we can work through together.

Explore the advisory role