Role description
Operations Lead
FinAbout Fin
Fin is a next-generation payments platform built for high-value, global, and instant transactions. We are a Series A-stage company backed by Sequoia, Circle, and other notable investors. Powered by stablecoins, Fin enables users and businesses to move millions of dollars in seconds - whether to other Fin users, directly into bank accounts, or across crypto rails. By combining the speed of crypto with the reliability and trust of traditional finance, Fin reimagines how money moves worldwide. If banks and payment products were reinvented today, they would look like Fin.
Role Description
Fin is building financial infrastructure for businesses moving money globally. We’re a small team, which means some of the most important problems we encounter don’t fit neatly into product, operations, growth, or engineering.
We’re looking for someone who likes those problems.
You’ll take on important projects that need an owner, figure out what actually needs to happen, and drive them from an ambiguous problem to a working solution. Sometimes that means building a new internal process. Sometimes it means working directly with customers or partners. Sometimes it means digging into data, writing requirements, building lightweight tooling, or working with engineering to turn an operational problem into a product.
The problems will change as Fin grows. We want someone who is excited by that.
What you’ll do
Own high-priority projects that cut across product, operations, customers, and our external partners.
Take loosely defined problems, determine what needs to be done, and drive them through execution.
Work directly with customers and internal teams to understand problems and translate them into clear requirements.
Build new processes and operating systems where none exist today.
Identify recurring operational problems that should be solved through better tooling, automation, or product.
Write requirements and work closely with engineering to build internal and customer-facing tools.
Use data to understand how processes are working, identify bottlenecks, and determine where we should invest.
Build lightweight tools and automations yourself when that is faster than building something into the core product.
Help launch new products, partners, workflows, and markets by owning the operational pieces required to make them work.
Jump into areas of the business that need additional ownership and leave them more scalable than you found them.
Your initial projects could include improving the systems behind customer onboarding and CDD, building better internal tooling, automating manual workflows, helping us launch new financial partners or markets, or owning operational pieces of new product initiatives.
What we’re looking for
You’re a strong generalist who is unusually good at getting things done.
You’re comfortable starting with an ambiguous problem rather than a detailed set of instructions.
You’ve owned projects across multiple functions and can keep a lot of moving pieces organized.
You can understand a stakeholder’s problem, turn it into a concrete plan, and coordinate the people necessary to deliver it.
You naturally think about systems. When you encounter a repetitive process, your instinct is to ask why it works that way and whether there’s a better solution.
You’re comfortable working directly with customers and external partners.
You’re analytically minded and comfortable using data to make decisions.
You have enough technical fluency to work closely with engineers and understand technical products. SQL, APIs, automation tools, or experience building lightweight internal tools are all useful.
You’re equally comfortable writing a requirements document, digging into a broken workflow, coordinating a complicated project, or doing the manual work necessary to understand a problem firsthand.
You learn quickly and don’t need previous experience in every problem you’re asked to solve.
Experience at an early-stage startup, in product or operations, consulting, banking, or another environment where you’ve had to operate across functions can all translate well.