Product Lead; Crypto​/DeFi | Remote

Shape the future of crypto tax with a product people actually need.

Koinly helps people do their crypto taxes without losing their minds. The bar is simple to describe and hard to deliver: a user should be able to do their taxes in under 20 minutes. That only works if the product is correct. Not “mostly correct.” Correct in the messy corners: LPs, bridges, aggregators, weird fees, rounding, missing legs and duplicates.

We’re hiring a Product Lead who is excited by that kind of complexity and can ship. This is ideal for someone who’s strategic, technical, and passionate about crypto.

We’re a fully remote-first, async-first startup with product‑market fit in a niche (and booming) domain: crypto taxes. If you value autonomy, technical excellence, and clear communication over meetings and process complexity, Koinly is the place for you.

• Scope of role:
  • Delivery operating system
  • Tax completion speed with correctness
  • Data discrepancy reduction
• Team:
  Product
• Report to:
  Our Founder/CEO
• Location:
  
  Anywhere, with a stronger preference for significant overlap with Europte timezones
• Employment: B2B
• Experience level: 5+ years as a Product Lead, Engineering Lead, or SaaS Founder (we care more about evidence than titles).
• Team size: A company of 35 people.
• Visa sponsorship:
  No
• Recording +  may be recorded for note taking and  purposes. Formal  required before offer.

You’ll own product execution and delivery end-to-end: how features are defined, built, and shipped, working closely with our engineering teams (Core + Imports) and Design, and our CEO/founder.

• Own the end-to-end flow.
• Own Kanban flow: prioritise the board, keep work unblocked, and drive day-to-day delivery with engineering.
• Turn messy user problems and edge cases into clear requirements, UX flows, and acceptance criteria.
• Keep a high bar for quality, accuracy, and long-term maintainability.
• Reduce data discrepancies (the “$1 mismatch” kind of work) by partnering with engineering on root-cause fixes.
• Have an eye for UX more than UI: simplify flows and resolve pain points using simple wireframes.
• Participate in on-call / incident involvement when needed (because tax accuracy has real-world consequences).

Within 30-90 days you should:

• Understand the product deeply enough to map the “tax in