About Bolna

Bolna is a platform to seamlessly build and deploy multilingual human-like Voice AI Agents capable of handling inbound and outbound calls. We're built for enterprises and fast-scaling teams handling high-volume phone workflows across recruitment, support, operations, and collections.

Bolna dynamically routes each call across the best ASR, LLM, and TTS models by language, latency, and cost - so you get human-like conversations at scale without tuning infrastructure. We're solving the real-world bottleneck of scaling phone-based interactions without needing to hire, train, or manage large human agent teams.

Why our Customers love us

Ability to train agents and go live with 1,000s of calls in less than 2 days
Massive increase in ROI - with agents matching human performance at 50% of the cost
Effortless upscaling and downscaling based on calling requirements
Transparent pricing (only per minute) and best-in-class support

We are just getting started. If you want to work hard and create lasting impact, We'd like to hear from you.

How we work

High-velocity: Rapid experimentation, lean autonomous teams, and minimal bureaucracy.
Impact not job titles: We don't have job titles. Instead, it's about the impact you have. No task is above or beneath you.
AI first: We use AI to move faster with higher-quality results. We do this across the whole company—from engineering to growth to operations.
Excellence everywhere: Everything we do should match the quality of our product.

What we offer

Innovative culture: You'll be part of a generational opportunity to define the trajectory of AI, surrounded by a team pushing the boundaries of what's possible.
Growth paths: Joining Bolna means joining a dynamic team with countless opportunities to drive impact - beyond your immediate role and responsibilities.
Learning & development: Bolna proactively supports professional development, the processes for which are being set up.

About the role

Most product roles at Bolna own a slice of the platform - Studio, Customer Intelligence, Graph Agents, Data Platform. This role is different. You own the flow of insight between our field and our roadmap, and you ship against it.

Today, when our Forward Deployed Engineers solve a hard problem inside a customer deployment - context management for order-taking at a D2C merchant, a tricky compliance workflow for a BFSI pilot, a Hinglish disposition pattern that doesn't generalize - that learning often lives in a Lovable workaround or a Slack thread. Two months later, a different FDE rebuilds something similar for the next customer. The platform doesn't compound from what the field already figured out.

This role exists to close that loop. You'll embed with FDEs across our most strategic deployments, spot the patterns that recur across customers, write the spec, and then co-own the build with whichever surface PM the feature belongs to (Studio, Customer Intelligence, Graph, Data Platform, soon Runtime) - all the way through to ship. You'll also own the library of vertical pre-builts (templates, modules, integrations, playbooks) that we hand to the next customer so they don't pay the same cost in time and effort.

The closest reference points for this role are the Anthropic's Applied team and the platform-product layer behind Palantir's FDEs. Your loyalty is to the platform, not to any single customer - but you can only do the job if you're constantly in the field.

You'll report to the Head of Product.

What you'll own

Cross-deployment pattern recognition. Across BFSI pilots, e-commerce rollouts, recruitment and collections customers - what are the three or four problems the field is solving from scratch each time? Spot them, name them, write them up before anyone asks. This is the work no other PM at Bolna can do, and it's the work that quietly atrophies first if you don't protect it. We will protect it.
Productization, from spec to ship. Convert recurring field workarounds into PRDs, then co-own the build with the surface PM through to launch. You own the outcome - does the shipped feature actually solve the field pattern? They own implementation against their surface - coherence, sequencing, fit with the rest of the roadmap. Two PRD authors, one product. To keep the synthesis work from being crowded out, you'll cap concurrent build engagements at 2-3 at any time; beyond that, the pattern queue grows but doesn't get worked.
The pre-builts library. Templates, prompts, modules, integrations, vertical playbooks. Built from our highest-performing live deployments, indexed by vertical (BFSI, e-commerce, recruitment, collections), with a "here's why this works" explanation so customers understand what they're inheriting. This is the one product surface you own outright.
FDE backlog sequencing. Partner with the FDE lead and the founders on what FDEs build for customers - biasing toward solutions with productization potential. When a true one-off is justified, you write down why it can't be generalized, so we don't have the same debate next quarter.
The productization rate. Industry leaders track at least one feature shipped back to the core platform per active engagement per quarter. You'll define ours, instrument it, and report against it.

What this role is not

It is not a customer-facing PM owning the why/what of any single pilot. That work sits with FDEs and founders today, and that's where it should stay.
It is not the roadmap PM for any single surface. Studio, Customer Intelligence, Graph, and Data Platform all have their own PMs who own their surface end-to-end. You co-own the features that come from the field, alongside them.
It is not solutions engineering or pre-sales. We have FDEs for field implementation. Your output is product - specs, pre-builts, shipped features - not customer-facing code.

If you find yourself pulled into hands-on customer delivery, or if your concurrent build load drifts above three, something has broken in the role's boundaries. We'd want to know early.

What you bring

We do not require formal credentials or a specific number of years. Show us a past project where you sat between a field/customer team and a product team, and made the platform compound from field learnings.

Field instinct. You're comfortable inside a customer environment. You can spend three days on-site at a BFSI client and come back with a sharp written synthesis of what the FDE actually solved and what the platform should have done instead.
Pattern recognition. When you see the same workaround twice, you can't sleep until you've named the underlying abstraction. You write it up unprompted.
PRD craft and shipping instinct. Your specs are precise enough that you and the surface PM can sit down on day one of build and have alignment on outcome, scope, and trade-offs. You've shipped product before - you know what production-ready actually means, and you close the gap.
Comfort with shared ownership. This role lives in the seam between FDEs and core PMs. Co-owning features means you'll sometimes feel like you're slowing the surface PM down, and they'll sometimes feel like they're slowing you down. You should be okay with that and able to resolve it without escalating every time.
Indian enterprise context. BFSI compliance, collections workflows, e-commerce merchant operations, recruitment funnels - you don't need to know all of it on day one, but you should be excited to learn it deeply. Our customers are Simplilearn, Meritto, Alibaba, GoKwik, and 200+ others across the verticals we serve.
A bias to writing. A lot of this job is documents - pattern memos, PRDs, pre-built explanations, post-mortem syntheses. You should enjoy writing them.

Nice to have

Previous time in an Applied / Forward Deployed / Solutions / Field PM role at an enterprise AI or platform company.
Prior experience as an FDE, Solutions Engineer, or Implementation Consultant with a transition into product management.
Background in voice AI, contact centers, CPaaS, or conversational AI.
Founder background, especially if you sold into Indian enterprises.

Success in this role looks like

A documented productization rate (features shipped back to core platform per quarter) that grows across your first three quarters.
Pre-built libraries for at least BFSI and e-commerce that measurably reduce FDE deployment time on new customers - specifically, median days from contract signed to first 1,000 live calls trending down.
Three to five field patterns named, specced, and shipped into core product within your first six months - co-owned with the relevant surface PM, on their surface, on time.
Zero of those patterns require you to be in the room a second time when a new customer hits the same problem. The platform absorbs it.

Location

This role is hybrid, based out of Bangalore. You'll also be on customer sites - expect 30-40% travel during the first year as you build pattern coverage across our top deployments.

Applied PM

Job Description