The role

Bland is hiring a Product Manager to own the developer experience for building on and with Bland.

Developers use Bland within their own toolkit to send calls through our API, build agents with Codex or Claude, manage them through a CLI and GitHub, and use our models in their own voice products. You’ll bring our APIs, MCP, CLI, plugins, and documentation together into a curated product offering that developers and their coding agents can understand and use.

You’ll own the experience of developers building on and with Bland. Your job is to make that experience exceptional, from a developer’s first integration to a call running in production. You’ll bring our developer tools together into a cohesive platform and define how we bring our models to market, including which capabilities we offer, how customers consume them, and how we package and price access.

You’ll work with engineering, research, Customer Engineering, and marketing to turn those capabilities into products developers adopt and keep using.

We’re looking for a technical product builder who loves working with developers, knows what makes a great self-serve developer experience, and loves to win. You’ll set product direction, lead developers across the stack, and ship improvements yourself. You’ll engage the developer community and shape how people build at the frontier of voice AI.

The outcome objectives for this role are:

1. Grow the number of developers building on and with Bland.

2. Increase the share of meaningful usage beyond our UI.

3. Grow the proportion of ARR driven by Bland’s models.

What you'd own

• Our APIs and developer tools. Shape a consistent experience across the API, MCP, CLI, and plugins. Simplify common tasks, make configuration understandable, and establish clear conventions that developers and coding agents can rely on.

• Documentation and developer enablement. Own the quality and completeness of our API docs, quickstarts, sample integrations, and guides. Make sure new capabilities ship with a documented path to a working result, and keep those materials current as the platform changes.

• Developer activation and retention. Understand what developers are trying to build, where they get stuck, and why they leave. Instrument the journey from signup to production, work directly with customers, and turn recurring support issues into product improvements alongside Customer Engineering.

• Model consumption and commercialization. Own the strategy for bringing our voice models to developers building their own voice experiences. Define which capabilities we offer, how developers integrate them, and how we package and price access. Own the APIs and product surfaces through which customers try, configure, and consume our models, and partner with research on the behaviors and controls they need.

• Developer relationships and the product story. Help developers understand what they can build and why Bland is a good fit. Work with marketing and Customer Engineering on demos, technical content, launches, and internal enablement. Bring developers together through workshops, hackathons, or other events where they help people build and adopt the product.

What you'd be working on

• The shortest path to a production agent. Make it possible for a developer to go from nothing to a working agent in production via our developer tools as quickly as possible.

• A coherent platform developers can navigate. Make it clear which capabilities are available and how to combine them. Build complete examples for common use cases, establish consistent API patterns, and carry that clarity through documentation and every new release.

• Commercializing our suite of voice models. Build the commercial strategy for developers creating their own voice experiences with individual Bland models. Start with Bland’s Text-to-Speech v3 and shape how we bring future models across the voice stack to market, from choosing the right use cases to packaging, pricing, integration, and adoption.

You’ll explore the range of AI applications in phone calls, from full-duplex models to research into the dynamics of conversation, and help turn those advances into capabilities developers can build with.

What we're looking for

• A competitive generalist mindset. You love to win, hate to lose, and make progress without waiting for direction. You learn quickly and take failures on the chin. You hold yourself to a very high bar and demand excellence from your teammates. You welcome direct feedback, challenge ideas openly, and assume good intent.

• An engineering foundation. You’ve worked as a software engineer and have at least three years of experience across engineering, data science, or product management. You’ve used APIs firsthand and built real integrations. You seek out new tools before they’re widely adopted, get unfinished technology working, and build things on your own initiative.

• Experience building for developers. You’ve built developer-facing products or tools and use APIs, CLIs, MCPs, and coding agents in your own work. You have opinions about what makes a developer experience great and can explain them through examples.

• Comfort shipping code. You can build sample integrations, test your own assumptions, improve documentation and tooling, and make product changes directly. We welcome engineers moving into product who can demonstrate strong product judgment through what they’ve built.

• Enthusiasm for working with customers and enabling others. You enjoy watching developers build, understanding their problems, explaining what’s possible, and helping them succeed. You can turn a technical capability into clear documentation, a compelling demo, and a product story that equips both customers and teammates.

• An active interest in voice AI. You’ve gone out of your way to build with voice products and follow the models, tools, and companies shaping the category.

Bonus

• You’ve owned developer programs and helped developers adopt and succeed with a product.

• You’ve curated or participated in events for the developer community, such as hackathons, technical workshops, and speaker series.

How we work

This role requires high ownership, pace, and commitment. We expect you to be reachable on weekends, and Fridays are always in person.

You’ll work closely with engineering, research, Customer Engineering, and marketing, coordinating contributions while staying accountable for the developer experience. You should be comfortable with changing priorities and willing to take on product work beyond your initial remit.