Careers

Why should you join Bamboo?

At Bamboo, we are building the future of financial infrastructure by enabling seamless, secure, and scalable payments across global markets. We partner with businesses, platforms, and institutions to make moving money simple, reliable, and connected. Joining us means contributing to meaningful work that spans borders, impacts merchants, and supports innovation in the fintech space.

If you’re passionate about turning data and design into actionable insights, defining metrics that matter, and building products people love, this role is for you.

What you’ll do

• Own the Core product surface: the platform layer (authentication, merchant configuration, orchestration between services, notifications, observability) and the billing engine (fee calculations, ledger movements, balance adjustments, reconciliation, statements). Core is the substrate of every other squad, sits on top of, and it is the single owner of merchant-level accuracy, reliability and financial truth.
• Lead the core business squad day-to-day, as their product counterpart. Own the ceremonies: sprint planning, refinement, daily stand-ups, retros, and quarterly roadmap reviews. You are the person who keeps both squads moving in the same direction and unblocked.
• Design the pricing, fee, and ledger primitives that let merchants trust every number they see. Own how contracts are modelled, how per-transaction fees are calculated pre-authorization, how post-settlement movements land in the ledger, and how balances adjust for chargebacks, refunds, retentions and holdbacks.
• Turn platform reliability into a productised discipline. Uptime, API latency, webhook delivery SLAs, orchestration retries, environment parity, these are your KPIs, not just Engineering’s. You define what “good” looks like and you drive the roadmap to get there.
• Run the support-to-roadmap loop. Triage the incoming ticket queue that hits Core, separate one-offs from systemic issues, and turn recurring pain into product work. You own the prioritisation call between new capabilities, tech-debt paydown, and support-driven fixes — with a framework the whole company understands.
• Partner deeply with Engineering Leads on architecture decisions that shape multi-quarter horizons: event-driven post-processing, ledger schema evolution, orchestration patterns, observability upgrades. You are technical enough to sit in those rooms, challenge trade-offs, and hold the merchant-facing outcome as the anchor.
• Coordinate horizontally across every other squad. Because Core is upstream of everything, every Payins/Payouts/Gateway/Integrations initiative eventually touches you. You are the single point of contact for platform dependencies, the negotiator on shared roadmap slots, and the person who protects Core capacity from being fragmented across too many parallel tasks.
• Own the Core roadmap for the year and translate it into quarterly commitments aligned with Bamboo’s 2026 objectives.. Every initiative you take on has an explicit rationale, target KPI, and success criteria, no orphan work.
• Keep the technical documentation of Core alive, architecture, transactional flows (pre-auth → capture, refund online/offline, chargebacks), ledger states, event contracts.

Requirements

• Systems Engineering degree (Ingeniería en Sistemas / Computer Science / equivalent) must. This is a technical PM role; you need to hold your own in architectural discussions.
• 2+ years of experience in the payments industry, payments processor, PSP, acquirer, fintech, cross-border. You know what a chargeback lifecycle looks like, how card acquiring settles, and what a ledger looks like inside a payment platform.
• 2+ years of Product Management experience on technical / platform / infrastructure products, not consumer-facing UX. You have shipped roadmaps where the customer was another engineering team or an ops team, not an end user.
• Fluent English (reading, writing, speaking) must. You will interact daily with Engineering, other PMs, and international merchants.
• Track record running agile ceremonies for one or more squads, planning, refinement, retros, daily stand-ups. You know how to keep them useful and short.
• Demonstrable framework for support-ticket triage and prioritisation, you have owned an incoming queue before and can show how you separated noise from signal and turned recurring tickets into product work.
• Strong understanding of billing engines, ledger systems, and money-movement architectures. You know why a post-settlement ledger diverges from a pre-authorisation snapshot, and why that matters.
• Familiarity with event-driven architectures, microservices, and cloud-native platforms (AWS / EKS a plus). You do not need to code production, but you need to understand a system diagram, and reason about failure modes.
• Bias for writing over meetings. PRDs, decision records, roadmap docs, incident post-mortems. Your team should be able to read what you decided and why without booking a call.

What Success Looks Like

• Core reliability targets are owned and reported quarterly platform uptime, API latency percentiles, webhook delivery SLAs, ledger consistency. Regression against target triggers a documented action plan, not a Slack thread.
• Billing accuracy is measurable and improves quarter over quarter, the count of merchant-reported billing discrepancies, the average time-to-resolve for reconciliation tickets, and the % of statements accepted on first submission are all trending in the right direction.
• Sprint commitments land on time in ≥ 80% of sprints. Quarterly roadmap commitments land in ≥ 70% of scope. When they don’t, the miss is explained in a Q retrospective, not absorbed silently.
• Recurring support-ticket categories translate into product work within 1–2 quarters of being identified. New categories are surfaced early, not after they become a weekly incident.
• Cross-squad Product Managers rate the Core PM highly as a partner (measured through an internal PM NPS or equivalent). Their initiatives get platform dependencies unblocked on time; disagreements on priority are surfaced early and resolved with a written trade-off, not a status-meeting standoff.
• Tech debt on Core is not just tracked, it is paid down on a schedule. The known-debt list documented in the platform knowledge base shrinks quarter over quarter, with each closed item traceable to a concrete piece of shipped work.
• New Bamboo capabilities that depend on Core launch on the platform without one-off patches, the primitives you designed absorb them cleanly.
• The Core knowledge base is trusted. A new engineer or PM joining the platform can read the documentation and be operational in days. Ambiguity in the docs is treated as a bug, not as tribal knowledge.