Careers at Argent Wallet

Build the wallet people can understand and trust.

Working on self-custody means treating product details as real decisions with real consequences. We are interested in people who combine technical depth with clear thinking and care for the person on the other side of the screen.

Contact us
Argent team working together

Small groups take a problem from first questions through shipped improvements.

Distributed work is supported by written context and intentional collaboration.

How we work

Serious work without unnecessary theatre.

A wallet team needs focus, candid communication, and respect for the risks users take. These are the habits we want the working environment to reinforce.

Own the outcome

Understand the problem, involve the right people, and stay accountable after a feature ships—not only until a task is closed.

Write the context down

Clear decisions travel better across disciplines and time zones. We document trade-offs so the team can challenge and improve them.

Protect focused work

Not every question needs a meeting. We preserve time to think deeply and use shared hours for conversations that benefit from being live.

Where people contribute

One product, different kinds of expertise.

Wallet quality is not created by engineering alone. It comes from several disciplines examining the same user decision from different angles.

Wallet engineering

Build reliable product flows, integrations, and infrastructure while making failure states visible and recoverable where possible.

Security and protocol

Analyse assumptions, review critical paths, and turn network-level risks into practical product requirements and guidance.

Product and design

Shape complex wallet actions into interfaces that provide context without hiding responsibility or important technical detail.

Support and education

Help people solve problems safely, recognise recurring confusion, and bring evidence from real questions back into the product.

Hiring process

A clear process in both directions.

Interviews should help both sides understand the work, expectations, and fit. The exact format can vary by role, but the purpose of each stage should be explained in advance.

  1. 01

    Introduction

    A short review of relevant experience, motivation, location, and the practical requirements attached to the role.

  2. 02

    Role conversation

    Discuss the problems the team is working on and explore how your experience relates to the decisions the role will own.

  3. 03

    Work discussion

    Examine a relevant problem or previous project. Any preparation, expected time, and evaluation criteria should be stated clearly.

  4. 04

    Decision and details

    Share the outcome, answer remaining questions, and confirm responsibilities, working arrangements, and terms before either side commits.

Contacts