New York, NY | In office | Full-time | Mid-level (3 to 6 years) | $110k to $140k + early equity
About InstaSwitch
InstaSwitch automates business bank account switching. Banks and fintechs lose a huge share of the accounts they open because customers never fund them or move real activity over. We fix that. We connect a customer's prior bank, map their income, payroll, vendors, and spend, and then automate the switch across 35+ tools so funding and operational activity actually move. We work with leading fintechs and banks through both hosted and embedded integrations, and our team is small, fast, and hands-on.
About This Role
This is a hands-on Product Operations role at the center of how InstaSwitch runs internally and how we turn what we learn into what we build. You will map how our processes actually work, fix the parts that are manual or broken, and own the translation of business intent into the structured specs engineering needs to execute. It is a builder role: you will do the work yourself, not direct others to do it, and the scope will grow as the company grows.
This is not a customer implementations role. Over time, the right person could pinch-hit on implementations, but that is not the core of this job. This is also not a leadership hire and not a junior hire. It sits squarely in the middle: experienced enough to operate without a playbook, early enough in career to be deep in the details every day.
What You Will Do
Internal Process Mapping
- Map how our internal processes actually work today, end to end, and find the manual, duplicated, or broken steps.
- Rebuild those processes so they scale and do not fall apart when the team is busy.
- Set up the queues, trackers, and operating rhythms that keep work moving across product, engineering, and go-to-market.
Product Workflow Mapping
- Map our product workflows and how features behave across the many platforms and tools we integrate with.
- Document how the automation extension, manual instructions, and automations fit together so the whole team has a shared, accurate picture.
- Keep internal product documentation current as the product changes, so it reflects how things actually work, not how they used to.
Technical Project Management
- Translate business intent into structured written specs: clear requirements, acceptance criteria, and definitions that remove ambiguity before it becomes rework.
- Understand what engineers need from a well-written ticket, and what a vague one costs.
- Coordinate work across people & workstreams, keep timelines honest, surface risks early.
- QA workflows and test new features in the context of real use, catching issues before they ship.
Feedback Loop and Cross-functional Execution
- Bring what we learn from the field back into product prioritization in an organized way, not as anecdotes but as structured input the team can act on.
- Spot friction across product, engineering, and operations and clear it before it compounds. Be the person who picks things up without being asked.
- Jump in across product / go-to-market where the company needs an experienced generalist.
What We Are Looking For
- 3 to 6 years of experience across product operations, technical program management, implementation, or a closely related generalist role, ideally at a startup.
- A track record of building or rebuilding processes from scratch in a technical environment, with clear documentation and defined handoffs.
- You write specs and process documentation that other people actually use, and you know what good looks like.
- You are a systems thinker who naturally breaks problems down, sees how the pieces connect, and goes after root causes rather than symptoms.
- You are resourceful and self-directed. You figure things out without a playbook, and when you build one, you make it usable for everyone after you.
- You communicate clearly with engineers, operators, and the founding team alike, in writing and in conversation.
- Based in New York City and able to work in office.
Nice to Have
- Experience at a fintech, payments, or banking infrastructure company where the product had real technical complexity.
- Comfort with tools for tracking, automating, or analyzing operational workflows.
- A track record of owning outcomes well beyond a formal job description.
What This Is Not
This is not a role for someone who needs a team under them to get leverage. For the foreseeable future, you will be doing the work yourself and owning outcomes directly.
This is not a pure product management role. You will have real influence on what gets built and when, but your work is operational: process mapping, documentation, specs, and feedback translation. Feature strategy sits with the founding team.