At Koinly, we operate async-first by default. That means:

• Written communication is prioritized over meetings
• Proposals, decisions, and updates are clearly documented
• Meetings are intentional and reserved for collaboration or complex discussions
• Team members are trusted to manage their time without micromanagement
• Individuals are expected to operate with high ownership and navigate ambiguity

We value clarity, autonomy, and accountability.

While time zones are flexible, some roles require collaboration overlap. In those cases, UK morning hours serve as our “golden hours” for real-time coordination.

This allows for focused work, better documentation, and more inclusive collaboration.

Collaboration is structured to work well across time zones and minimize unnecessary meetings.

• We use Slack for day-to-day communication and coordination
• Notion for documentation, proposals, and decisions
• Google Meet for live discussions when needed
• Jira to plan and track work
• Figma for product and design collaboration

As an async-first team, we keep meetings intentional. Engineering teams generally avoid a rigid meeting cadence and rely more on written updates, planning artifacts, and PR-based collaboration.

Some other teams choose to run more structured recurring meetings based on what works best for them. This reflects our vision for a bottom-up culture, where teams shape their own collaboration rhythms rather than following a one-size-fits-all schedule.

People who do well here tend to be:

• Self-directed and comfortable with autonomy.
• Strong written communicators.
• Pragmatic problem-solvers.
• Comfortable working with evolving requirements.
• Focused on outcomes rather than activity.
• Practical and functional technical depth.

Ownership means being accountable for outcomes, not just tasks.

In practice, this looks like:

• Taking responsibility for a problem from definition to delivery
• Proactively identifying risks, gaps, or improvements
• Making informed decisions without waiting for constant direction
• Communicating progress and blockers clearly in writing
• Following through after launch to ensure quality and impact

We operate with high trust and low micromanagement. Ownership at Koinly requires comfort with autonomy, the ability to navigate ambiguity, and a focus on delivering meaningful results.

Yes. We operate as a remote-first company. 

Specific location requirements (if any) are listed in the job description.

Some roles may be limited to specific regions due to legal, payroll, or collaboration requirements. 

When restrictions apply, they will be clearly stated in the job posting.

Expectations vary by role and team. Where collaboration overlap is important, this is noted in the job description.

In general, we keep collaboration async-friendly. When real-time coordination is needed, UK morning hours are our “golden hours” for overlap and meetings.

We currently do not offer visa sponsorship unless explicitly stated in the job description.

No, we don't offer relocation support. We're a remote-first company, so there's no need to relocate to a specific region to be able to work with us. 

While steps may vary by role, our hiring process at Koinly typically includes:

1. Application review (async).

2. Initial screening call (sync).

3. Technical or role-specific assessment (async).

4. Interview(s) with team members and hiring manager (sync).

5. Final discussion and offer (sync + async).

Most processes take between 2–6 weeks from application to decision. Timelines may vary depending on role complexity and interview availability.

Our technical assessments are designed to reflect real-world scenarios relevant to the role. 

We value structured thinking, clarity, and practical decision-making over perfection.

For engineering roles, we evaluate:

• Code quality and clarity.
• Problem-solving approach.
• Handling of trade-offs.
• Structure and maintainability.

Yes, AI tools may be used. 

However, we expect you to:

• Guide and structure the tool effectively
• Critically evaluate the output
• Explain their reasoning and decisions

Using AI without understanding or validating the output will be apparent during follow-up discussions.

We recommend:

• Reviewing the job description carefully.

• Understanding our product and customers.

• Preparing examples of past work and impact.

• Being ready to discuss trade-offs, decisions, and lessons learned.

We aim to provide feedback whenever possible. Due to application volume, detailed feedback may not always be feasible at early stages.

Yes. If multiple roles align with your experience, you are welcome to apply. Please tailor your application to each position.

Strong applications are clear, concise, and impact-focused. 

To stand out:

• Show measurable outcomes (what improved, scaled, reduced, or shipped).
• Demonstrate ownership of complex problems from start to finish.
• Explain trade-offs and decision-making, not just implementation details.
• Communicate clearly and concisely.
• Tailor your application to the specific role and stack (e.g., Ruby on Rails experience for engineering roles).
• Demonstrate high levels of curiosity and show that you’ve researched Koinly, our product, and the problems we solve

In interviews and assessments, structured thinking and practical judgment matter more than polished perfection.

We work in the crypto and fintech space, where trust, data security, and regulatory compliance are critical. Background checks help us:

• Protect customer data and company assets.

• Meet compliance and regulatory obligations.

• Maintain a secure working environment.

Checks are proportionate to the role and conducted in accordance with applicable local laws. We are transparent about what is required and obtain consent before proceeding.

Yes.

We use identity verification at different points in the process to protect our team members and company assets, ensuring a fair, secure hiring experience.

• Earlier in the process, all interviews will be recorded so we can confirm we’re speaking with the same person throughout the process and that it matches the identity presented (e.g., LinkedIn profile photo or a photo on a CV, where provided).
• Later in the process, we use Zinc for formal ID verification using a government-issued ID, to confirm eligibility and meet compliance requirements.

Candidate data is handled in accordance with our privacy policy and applicable data protection regulations.

• Information is used only for recruitment purposes
• Data is stored securely and access is restricted
• Where we use tools such as interview recording or Zinc verification, they are used only for hiring and compliance purposes and handled according to relevant data protection requirements.

See more here. 

Perks include:

• Competitive compensation.

• Flexible working hours.

• Remote work setup.

• Async-first operation mode.

• 32 days of paid time off.

• Home-office stipend.

• Co-working space stipend (optional).

Specific details are shared during the interview process.

We don’t provide company-issued equipment. Most team members prefer using their own setup.

We do offer a home-office stipend, which you can use to upgrade your workspace (including hardware) if needed to perform your role effectively.

We don’t run company-wide offsites or retreats at this time.

Team members who live in the same city are encouraged to meet informally, such as for occasional co-working sessions or coffee meetups, if they choose.

Our core product is primarily built with Ruby and Ruby on Rails. 

Depending on the role, you may also work with APIs, background processing, data pipelines, and supporting infrastructure. The exact stack details are outlined in each job description.

Our engineering work typically involves:

• Processing and reconciling large volumes of transaction data.
• Data reconciliation and accuracy.
• Performance and reliability optimization.
• Integrating with third-party exchange and wallet APIs.
• Handling edge cases in financial and tax-related logic
• Maintaining strong security and privacy of financial data.

The focus is on accuracy, reliability, and real-world impact.

The work you do directly affects whether people can trust their numbers at tax time. Getting it right means customers spend less time untangling transactions, avoid costly mistakes, and feel confident that their reporting is accurate, especially when the underlying data is messy, inconsistent, and constantly changing.

Engineering decisions directly affect customers as follows:

• Technical correctness → tax accuracy
• Reliability → user trust
• Performance → user experience

Small technical improvements have significant downstream impact for users.

Success typically means:

• Taking ownership of meaningful problems.
• Shipping reliable solutions.
• Improving existing systems where needed.
• Contributing thoughtfully to architectural decisions.
• Communicating clearly in an async environment.

Most of our Ruby on Rails roles sit at the intersection of product and platform.

You’ll work on customer-facing functionality- features that directly impact user experience and tax accuracy- while also contributing to the underlying systems that ensure accuracy, reliability, and scalability.

Depending on the role and seniority level, you may:

• Ship product features end-to-end.
• Improve core data processing and reconciliation logic.
• Strengthen integrations with external APIs.
• Contribute to architectural and performance improvements.

We value engineers who can think beyond isolated features and understand how product decisions and system design influence each other.