Engineering Manager- Growth
openfx · Bengaluru
## About Us
OpenFX is on a mission to move money as freely as data, unrestricted by time zones, banking hours, or legacy systems. We are building the infrastructure that will power the next generation of cross-border payment systems for institutions. The team's execution has been exceptional, and we're scaling at a remarkable pace. Our stellar early team comes with experience in companies like J.P. Morgan, Goldman Sachs, FalconX, PayPal, Affirm, Polygon, Kraken, Nium & others. We're backed by Accel, Lightspeed, NfX and other top-tier investors.
## Role Overview
OpenFX processes billions of dollars in transaction volume every month across global corridors. The Growth pod owns everything a client touches before and while they become a paying, trading customer: the public API they integrate against, the onboarding and verification journey that gets them approved, the activation surface that gets them to their first trade, and the marketing site that brings them in.
Client onboarding runs today on third-party tooling and is being brought in-house, which means rebuilding KYB and KYC as our own product rather than a vendor workflow. And onboarding policy is still effectively global, when the business needs requirements that vary by jurisdiction and customer segment.
Every point of friction across those surfaces is a client who does not activate, or who activates slowly and expensively. The work is also unusually dependency-heavy: nearly every onboarding item depends on Compliance and Legal, the API programme depends on Platform, Payments, Banking, and Client Trading, and the website work depends on Brand Design.
We need an Engineering Manager who can hold four surfaces at once, ship inside a stage-gated product process without letting it become theatre, and keep a correctness bar on flows that touch identity, compliance, and the money path.
If we do not solve this well, activation stays gated on manual work and vendor tooling, and growth stays bottlenecked on ad hoc engineering requests.
## Key Responsibilities
• Run the Growth pod of roughly 6 to 10 engineers and QA across frontend, backend, and integrations. You own the roadmap, the delivery, and the standards.
• Own the API as a product. Land the V3 overhaul, our largest and most cross-dependent programme, while V2 stays supported. Ship client-facing API.
• Bring onboarding in-house. Move the client onboarding experience off third-party tools onto OpenFX, and build the rules engine that replaces global policy with dynamic KYB and KYC requirements by jurisdiction and customer segment.
• Extend onboarding to new segments — self-serve signup through to first trade with no sales touch, enterprise (large entities, directors, UBO, bespoke verification), channel partners and platform-of-platforms, multi-product onboarding across banking and payments, and eventually agent-based customers.
• Own the activation surface: digital signatures, in-product activation checklists, recovery and lifecycle client comms, and a self-serve notification centre.
• Own the marketing site as a growth surface, partnering with Brand Design and the visual explainers that both generate market intelligence and give sales what they need to close.
• Run the product development process credibly. Take work from discovery through solution, design, and RFC validation into delivery and beta, own or assign RFCs, and hold the design-ready and delivery-ready gates so nothing enters a sprint half-shaped.
• Manage a dependency-saturated roadmap. Compliance, Legal, Platform, Payments, Banking, Currencies, TPV, Client Trading, Brand Design, and GTM all sit on your critical path. Sequencing around them is a core part of the job, not an interruption to it.
• Own the interface with GTM and Product: one intake for growth and sales requests, joint prioritisation with the Growth PM, and an expedite lane whose cost in displaced work is explicit rather than silently absorbed.
• Stay hands-on. You review designs, and you still write and ship code, debug production, and set the implementation bar by example, including the standard for AI-assisted development.
• Hold the bar where correctness is not optional: identity and KYC deduplication, idempotency on quote and trade paths, permission and compliance boundaries, money precision and rounding.
• Hire and grow the team: close open roles, grow your team, run 30-60-90 ramps, set explicit performance expectations, and act on them early.
## What We Are Looking For
Must-haves:
• EM-level scope: 2 or more years managing a full team of 5 or more, with a Tech Lead or senior IC reporting in, on top of a strong individual contributor track record.
• Still writes code. You can design an API, model a schema, and produce idiomatic, runnable, tested code. Design fluency without hands-on ability is not enough at this level.
• Experience owning a public or partner-facing API as a product, including versioning and running an old and a new major version side by side.
• Shipped client-facing product end to end, including the unglamorous parts: migrations, deprecations, and error states.
• Has delivered against Compliance and Legal as hard dependencies, not as a review step at the end. Onboarding at OpenFX is a compliance surface first and a product surface second.
• Comfortable running a stage-gated product process — discovery, solution and design validation, RFC, delivery — without letting it slow the team down or become box-ticking.
• Can take a one-line placeholder and turn it into shaped, sized, sequenced work. A large share of the forward roadmap is deliberately undefined.
• Demonstrated hiring and performance management, including at least one underperformance case you saw through to an outcome.
• Has worked directly with Product and a commercial or GTM function, and can say no with a reason that holds.
• High agency: operates with low oversight on ambiguous problems, in a demanding environment.
• Can articulate and enforce a correctness bar under commercial time pressure.
What helps you stand out:
• Fintech, payments, or another regulated domain where onboarding is a compliance surface.
• KYB and KYC in production, and replacing a vendor onboarding or verification workflow with an in-house build.
• Jurisdiction-aware or segment-aware policy engines, where requirements are configuration rather than code branches.
• Developer experience work: API documentation, SDKs, sandbox environments, webhook delivery, or developer funnels.
• Activation and lifecycle engineering: in-product onboarding checklists, transactional and lifecycle comms, notification preferences.
• Marketing site or growth-experiment engineering in partnership with Brand Design.
• Growth instrumentation and analytics tooling, and comfort reading a funnel yourself.
• Onboarding for enterprise entities (directors, UBO) or for channel partners and platform-of-platforms models.
## What Success Looks Like
• Share of TPV through the API, with a target of 60%. The V3 overhaul, webhook reliability, and API observability are the levers.
• Activated customers, with a target of 200+. Onboarding, digital signatures, and the activation surface are the levers.
• Annualised TPV, contributing to an annualised
50B dollar goal.
• Zero lights-out compliance and financial crime findings on the flows you own.
• Predictable delivery: commitments land on the dates given, and when they slip you flag it early with a revised plan rather than late with an explanation.
• Dependencies land: work with Compliance, Legal, Platform, and Brand Design closes on schedule because you drove it, not because it happened to unblock.
• Discovery converts: ambiguous placeholder initiatives become shaped, sized, RFC-validated work rather than sitting at low confidence for a quarter.
• Quality on the identity and money path: onboarding and API defects are caught by tests and monitoring, not by clients.
• Team strength: fully staffed and ramped, your Tech Lead is growing, strong performers stay, and weak performance is addressed rather than tolerated.
• Talent magnetism: you bring strong engineers with you and raise the bar of every loop you sit on.
## Why This Role
• Impact: You own the surfaces that decide whether a client activates and whether their volume comes through our API. Both are company-level KPIs.
• Ownership: The pod, the roadmap, the quality bar, and the GTM interface are all yours to set.
• Scope: Four surfaces, not one: public API, onboarding and verification, activation, and the marketing site. Few EM roles span that much of the customer journey.
• Build, not maintain: Onboarding is coming off vendor tooling, the API is being overhauled, and much of the Q4 roadmap is still undefined. You are shaping it, not inheriting it.
• Learning: Cross-border payments, FX, and settlement, with compliance and correctness constraints that make the problems genuinely hard.
• Access: Direct partnership with the Growth PM, the Head of GTM, Compliance and Legal leadership, and senior engineering leadership.
## What We Offer
• Competitive salary and benefits package.
• Equity in a rapidly growing company.
• Opportunity to work in a fast-paced startup at the forefront of fintech innovation.
• Opportunity to make a significant impact on global financial infrastructure.
• Collaborative work culture with emphasis on personal and professional growth.
We are committed to building a diverse and inclusive workplace. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability, or veteran status.
OpenFX is on a mission to move money as freely as data, unrestricted by time zones, banking hours, or legacy systems. We are building the infrastructure that will power the next generation of cross-border payment systems for institutions. The team's execution has been exceptional, and we're scaling at a remarkable pace. Our stellar early team comes with experience in companies like J.P. Morgan, Goldman Sachs, FalconX, PayPal, Affirm, Polygon, Kraken, Nium & others. We're backed by Accel, Lightspeed, NfX and other top-tier investors.
## Role Overview
OpenFX processes billions of dollars in transaction volume every month across global corridors. The Growth pod owns everything a client touches before and while they become a paying, trading customer: the public API they integrate against, the onboarding and verification journey that gets them approved, the activation surface that gets them to their first trade, and the marketing site that brings them in.
Client onboarding runs today on third-party tooling and is being brought in-house, which means rebuilding KYB and KYC as our own product rather than a vendor workflow. And onboarding policy is still effectively global, when the business needs requirements that vary by jurisdiction and customer segment.
Every point of friction across those surfaces is a client who does not activate, or who activates slowly and expensively. The work is also unusually dependency-heavy: nearly every onboarding item depends on Compliance and Legal, the API programme depends on Platform, Payments, Banking, and Client Trading, and the website work depends on Brand Design.
We need an Engineering Manager who can hold four surfaces at once, ship inside a stage-gated product process without letting it become theatre, and keep a correctness bar on flows that touch identity, compliance, and the money path.
If we do not solve this well, activation stays gated on manual work and vendor tooling, and growth stays bottlenecked on ad hoc engineering requests.
## Key Responsibilities
• Run the Growth pod of roughly 6 to 10 engineers and QA across frontend, backend, and integrations. You own the roadmap, the delivery, and the standards.
• Own the API as a product. Land the V3 overhaul, our largest and most cross-dependent programme, while V2 stays supported. Ship client-facing API.
• Bring onboarding in-house. Move the client onboarding experience off third-party tools onto OpenFX, and build the rules engine that replaces global policy with dynamic KYB and KYC requirements by jurisdiction and customer segment.
• Extend onboarding to new segments — self-serve signup through to first trade with no sales touch, enterprise (large entities, directors, UBO, bespoke verification), channel partners and platform-of-platforms, multi-product onboarding across banking and payments, and eventually agent-based customers.
• Own the activation surface: digital signatures, in-product activation checklists, recovery and lifecycle client comms, and a self-serve notification centre.
• Own the marketing site as a growth surface, partnering with Brand Design and the visual explainers that both generate market intelligence and give sales what they need to close.
• Run the product development process credibly. Take work from discovery through solution, design, and RFC validation into delivery and beta, own or assign RFCs, and hold the design-ready and delivery-ready gates so nothing enters a sprint half-shaped.
• Manage a dependency-saturated roadmap. Compliance, Legal, Platform, Payments, Banking, Currencies, TPV, Client Trading, Brand Design, and GTM all sit on your critical path. Sequencing around them is a core part of the job, not an interruption to it.
• Own the interface with GTM and Product: one intake for growth and sales requests, joint prioritisation with the Growth PM, and an expedite lane whose cost in displaced work is explicit rather than silently absorbed.
• Stay hands-on. You review designs, and you still write and ship code, debug production, and set the implementation bar by example, including the standard for AI-assisted development.
• Hold the bar where correctness is not optional: identity and KYC deduplication, idempotency on quote and trade paths, permission and compliance boundaries, money precision and rounding.
• Hire and grow the team: close open roles, grow your team, run 30-60-90 ramps, set explicit performance expectations, and act on them early.
## What We Are Looking For
Must-haves:
• EM-level scope: 2 or more years managing a full team of 5 or more, with a Tech Lead or senior IC reporting in, on top of a strong individual contributor track record.
• Still writes code. You can design an API, model a schema, and produce idiomatic, runnable, tested code. Design fluency without hands-on ability is not enough at this level.
• Experience owning a public or partner-facing API as a product, including versioning and running an old and a new major version side by side.
• Shipped client-facing product end to end, including the unglamorous parts: migrations, deprecations, and error states.
• Has delivered against Compliance and Legal as hard dependencies, not as a review step at the end. Onboarding at OpenFX is a compliance surface first and a product surface second.
• Comfortable running a stage-gated product process — discovery, solution and design validation, RFC, delivery — without letting it slow the team down or become box-ticking.
• Can take a one-line placeholder and turn it into shaped, sized, sequenced work. A large share of the forward roadmap is deliberately undefined.
• Demonstrated hiring and performance management, including at least one underperformance case you saw through to an outcome.
• Has worked directly with Product and a commercial or GTM function, and can say no with a reason that holds.
• High agency: operates with low oversight on ambiguous problems, in a demanding environment.
• Can articulate and enforce a correctness bar under commercial time pressure.
What helps you stand out:
• Fintech, payments, or another regulated domain where onboarding is a compliance surface.
• KYB and KYC in production, and replacing a vendor onboarding or verification workflow with an in-house build.
• Jurisdiction-aware or segment-aware policy engines, where requirements are configuration rather than code branches.
• Developer experience work: API documentation, SDKs, sandbox environments, webhook delivery, or developer funnels.
• Activation and lifecycle engineering: in-product onboarding checklists, transactional and lifecycle comms, notification preferences.
• Marketing site or growth-experiment engineering in partnership with Brand Design.
• Growth instrumentation and analytics tooling, and comfort reading a funnel yourself.
• Onboarding for enterprise entities (directors, UBO) or for channel partners and platform-of-platforms models.
## What Success Looks Like
• Share of TPV through the API, with a target of 60%. The V3 overhaul, webhook reliability, and API observability are the levers.
• Activated customers, with a target of 200+. Onboarding, digital signatures, and the activation surface are the levers.
• Annualised TPV, contributing to an annualised
Careeroza — One-stop Zone for Aspirants
Study material, Careeroza mentorship, tech jobs, and career guidance on careeroza.com.
Public study materials
- Express.js — Web APIs & middleware (expressjs)
- Application setup · basic
- Routing deep dive · basic
- 1. MVC / Layered Architecture · medium
- Validation · medium
- File uploads · medium
- Sessions & auth (stateful) · medium
- Passport & strategies · medium
- Templating & SSR · medium
- WebSockets & SSE · medium
- Security middleware · advance
- Reverse proxies & trust · advance
- Performance · advance
- API design & versioning · advance
- Testing with Supertest · advance
- GraphQL & tRPC (overview) · advance
- Deployment checklist · advance
- Middlewares · basic
- Request & Response · basic
- AWS Crash Course (AWS)
- What is Cloud ? · basic
- What is AWS ? · basic
- If not cloud ? · basic
- Cloud Computing · basic
- AWS Pricing · basic
- AWS Shared Responsibility Model · basic
- AWS Management Console · basic
- AWS SDKs · basic
- AWS IAM · medium
- Users, Groups, Roles · medium
- Policies · medium
- AWS Organizations · medium
- AWS Cognito · medium
- AWS Directory Service · medium
- AWS KMS (Key Management Service) · medium
- AWS Secrets Manager · medium
- AWS Shield · medium
- AWS WAF · medium
- AWS Inspector · medium
- AWS GuardDuty · medium
- EC2 · advance
- Launching EC2 Instances · advance
- EBS Volumes · advance
- Security Groups · advance
- Key Pairs · advance
- Elastic IP · advance
- User Data Scripts · advance
- Auto Scaling · advance
- Load Balancers · advance
- ALB · advance
- NLB · advance
- Serverless Compute ,AWS Lambda, Lambda Layers · advance
- Event-Driven Architecture · advance
- ECS · advance
- EKS · advance
- Django (Django)
- What is Django · basic
- Installing Django · basic
- Features of Django · basic
- MVT Architecture · basic
- Django vs Flask · basic
- Creating Project & Creating App · basic
- Django Project Structure · basic
- URL Routing · basic
- Views · basic
- Templates · basic
- Static & Media Files · medium
- Models · medium
- ORM (Object Relational Mapping) · medium
- Model Relationships · medium
- Migrations · medium
- Django Admin · medium
- Forms · medium
- Authentication · medium
- Authorization · medium
- Middleware · medium
- Signals · medium
- Class Based Views Deep Dive · advance
- Generic Views · advance
- File Handling · advance
- Django REST Framework (DRF) · advance
- Advanced ORM · advance
- Caching · advance
- Asynchronous Django · advance
- Background Tasks · advance
- Interview Questions · interview-questions
- System Designing (System Designing)
- Day-1 : What is system Designing ? · basic
- Day-2 : Vertical vs. Horizontal Scaling · basic
- Day-3:How to do vertical scaling ? · basic
- Day4:How to do horizaontal scaling ? · basic
- Day:5TCP vs UDP · basic
- Day6:IP & DNS · basic
- Day7:Client-Server Model · basic
- Day8:HTTP & HTTPS · basic
- Databases (SQL vs NoSQL) · medium
- Caching · medium
- Day9:Latency & Throughput · basic
- Load Balancing · medium
- Indexes & Query Optimization · medium
- CDN · medium
- Proxies · medium
- Message Queues · medium
- Horizontal vs Vertical Scaling · medium
- Database Replication · advance
- Database Sharding · advance
- Consistent Hashing · advance
- CAP Theorem · advance
- Rate Limiting · advance
- Service Discovery · advance
- Event-Driven Architecture · advance
- API Gateway · advance
- Distributed Consensus · expert
- Microservices · expert
- Observability · expert
- Idempotency · expert
- PACELC Theorem · expert
- Two-Phase Commit · expert
- Back-of-Envelope Estimation · expert
- Designing for Failure · expert
- Node.js — Server-side JavaScript (nodejs)
- Getting started · basic
- JavaScript on the server · basic
- CommonJS modules · basic
- ES modules (ESM) · basic
- npm & package management · basic
- Asynchronous JavaScript in Node · basic
- The event loop · basic
- Essential core utilities · basic
- process & configuration · basic
- File system basics · basic
- HTTP & HTTPS servers · medium
- Streams · medium
- Events & EventEmitter · medium
- Advanced filesystem · medium
- crypto · medium
- Compression & encoding · medium
- Child processes · medium
- net, dgram & DNS · medium
- readline, timers & scheduling · medium
- Testing & diagnostics (intro) · medium
- Worker threads · advance
- cluster & multi-process scaling · advance
- Performance & tuning · advance
- Debugging & observability · advance
- Security hardening · advance
- Native addons & N-API · advance
- Architecture patterns · advance
- Graceful shutdown · advance
- 100 Questions · interview questions
- Python (Python)
- Python Fundamentals · basic
- Control Flow · basic
- Strings · basic
- Collections / Data Structures · basic
- Functions · basic
- Modules and Packages · basic
- File Handling · basic
- Exception Handling · basic
- Object-Oriented Programming (OOP · medium
- Advanced Python Concepts · advance
- Functional Programming · advance
- Multithreading & Multiprocessing · advance
- Async Programming · advance
- JavaScript (JavaScript)
- JS Introduction · basic
- Variables & Data Types · basic
- Operators · basic
- Control Flow · basic
- Functions · basic
- Scope & Execution · basic
- Closures · basic
- Objects · basic
- Arrays · basic
- Strings · basic
- DOM Manipulation · basic
- Browser APIs · medium
- Asynchronous JavaScript · medium
- Fetch & APIs · medium
- ES6+ Features · medium
- OOP in JavaScript · medium
- Prototype & Inheritance · advance
- Advanced Functions · advance
- Memory Management · advance
- Error Handling · advance
- Modules · advance
- Advanced Async Concepts · advance
- Functional Programming · advance
- JavaScript Internals · advance
- Performance Optimization · advance
- MongoDB — Documents & data modeling (MongoDB)
- Introduction · basic
- Shell, Compass & tools · basic
- Databases & collections · basic
- CRUD operations · basic
- Indexes deep dive · medium
- Explain plans & performance · medium
- Aggregation framework · medium
- Schema design patterns · medium
- Mongoose basics · medium
- Mongoose advanced · medium
- Drivers & connection · medium
- Operators for updates & arrays · medium
- Replication & read preferences · advance
- Write concern & read concern · advance
- Multi-document transactions · advance
- Change streams · advance
- Sharding (overview) · advance
- Atlas Search & full-text · advance
- GridFS & large files · advance
- Backup, restore & ops · advance
- SQL (SQL)
- SQL Fundamentals · basic
- Database Operations · basic
- Table Operations · basic
- CRUD Operations · basic
- Filtering & Operators · basic
- SQL Functions · basic
- GROUPING Data · basic
- Joins · medium
- Constraints · basic
- Subqueries · medium
- Set Operators · medium
- Views · medium
- Indexes · medium
- Normalization · advance
- Transactions · advance
- Stored Procedures & Functions · advance
- Triggers · advance
- Advanced SQL · advance
- Query Optimization · advance
- Database Design · advance
- SQL Security · advance
- Backup & Recovery · advance
- Questions · interview questions
- System Architecture (System Architecture)
- Fundamentals of System Architecture · basic
- Distributed System Basics · basic
- System Reliability Concepts · basic
- Scaling Concepts · basic
- Networking Basics · basic
- Web Communication · basic
- API Communication · basic
- Proxy & Delivery Systems · basic
- Web Architecture Basics · basic
- Rendering Architectures · basic
- Frontend Advanced Concepts · basic
- Message Queue Basics · medium
- What is Load Balancer · medium
- Load Balancing Algorithms · medium
- API Design Basics · medium
- API Protection · medium
- Authentication Basics · medium
- Security Tokens · medium
- Security Threats · medium
- Encryption & Security · medium
- SQL Database Basics · medium
- SQL Scaling Concepts · medium
- NoSQL Databases · medium
- Database Optimization · medium
- Replication Strategies · medium
- Caching Basics · medium
- Cache Storage Systems · medium
- Cache Strategies · medium
- Event-Driven Systems · advance
- Queue Reliability · advance
- Microservices Basics · advance
- Microservice Communication · advance
- Distributed Transactions · advance
- DevOps Basics · advance
- Automation Tools · advance
- Deployment Strategies · advance
- Monitoring Basics · advance
- Monitoring Tools · advance
- Distributed System Concepts · advance
- Distributed Algorithms · advance
- Angular (Angular)
- Angular Fundamentals · basic
- Project Structure · basic
- Components & Templates · basic
- Data Binding · basic
- Directives · basic
- Pipes · basic
- Component Communication · basic
- Lifecycle Hooks · basic
- Routing Basics · basic
- Routing · basic
- API Calls · basic
- Forms · medium
- Routing · medium
- Services & Dependency Injection · medium
- RxJS & Observables · medium
- Authentication & Security · medium
- Component Interaction · medium
- State Management Basics · medium
- Error Handiling · medium
- Perfomance Basic · medium
- Real World Features · medium
- Advanced Angular Architecture · advance
- Change Detection · advance
- Advanced RxJS · advance
- State Management · advance
- Dynamic Rendering · advance
- Perfomance Optimization · advance
- Modern Angular · advance
- STAR (Situation, Task, Action, and Result) (Situation Based Questions)
• Zero lights-out compliance and financial crime findings on the flows you own.
• Predictable delivery: commitments land on the dates given, and when they slip you flag it early with a revised plan rather than late with an explanation.
• Dependencies land: work with Compliance, Legal, Platform, and Brand Design closes on schedule because you drove it, not because it happened to unblock.
• Discovery converts: ambiguous placeholder initiatives become shaped, sized, RFC-validated work rather than sitting at low confidence for a quarter.
• Quality on the identity and money path: onboarding and API defects are caught by tests and monitoring, not by clients.
• Team strength: fully staffed and ramped, your Tech Lead is growing, strong performers stay, and weak performance is addressed rather than tolerated.
• Talent magnetism: you bring strong engineers with you and raise the bar of every loop you sit on.
## Why This Role
• Impact: You own the surfaces that decide whether a client activates and whether their volume comes through our API. Both are company-level KPIs.
• Ownership: The pod, the roadmap, the quality bar, and the GTM interface are all yours to set.
• Scope: Four surfaces, not one: public API, onboarding and verification, activation, and the marketing site. Few EM roles span that much of the customer journey.
• Build, not maintain: Onboarding is coming off vendor tooling, the API is being overhauled, and much of the Q4 roadmap is still undefined. You are shaping it, not inheriting it.
• Learning: Cross-border payments, FX, and settlement, with compliance and correctness constraints that make the problems genuinely hard.
• Access: Direct partnership with the Growth PM, the Head of GTM, Compliance and Legal leadership, and senior engineering leadership.
## What We Offer
• Competitive salary and benefits package.
• Equity in a rapidly growing company.
• Opportunity to work in a fast-paced startup at the forefront of fintech innovation.
• Opportunity to make a significant impact on global financial infrastructure.
• Collaborative work culture with emphasis on personal and professional growth.
We are committed to building a diverse and inclusive workplace. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability, or veteran status.