From Business Analyst to Technical API Product Manager: My Career Journey

5 MINS

Starting as a Business Analyst at Amazon and evolving into a Technical API Product Manager at US Bank taught me that great API products come from understanding both business problems and technical constraints.

The Amazon Foundation

My career started at Amazon, where I learned how data-driven companies operate.

What Amazon taught me:

Scale thinking : Building for millions of transactions, not hundreds

Customer obsession : Every decision starts with customer impact

Data-driven decisions : Gut feelings backed by metrics

Operational excellence : Systems that work reliably under pressure These principles now guide how I approach API product development.

The RealPage Evolution

At RealPage, I moved from pure analysis to product ownership as a Techno-Functional Product Owner.

Key transitions:

From documenting requirements to owning the backlog

From analyzing problems to defining solutions

From supporting decisions to making them

From project timelines to product roadmaps This role bridged my analytical background with product thinking.

Understanding the "Technical" in Technical PM

Technical API Product Manager isn't just a title; it's a way of working.

What it means in practice:

| Non-Technical Approach | Technical Approach |

|----------------------|-------------------|

| "We need an API" | "We need REST vs GraphQL for this use case" |

| "It should be fast" | "P95 latency under 200ms" |

| "Make it secure" | "OAuth 2.0 with specific scopes" |

| "Document it" | "OpenAPI spec with examples" |

Understanding technical details helps me make better product decisions.

API Products Are Different

API products have unique characteristics that change how you manage them.

API-specific considerations:

Developers are your users : They have different needs than end users

Breaking changes are expensive : Versioning strategy matters from day one

Documentation is product : Bad docs mean failed adoption

Errors are features : How your API fails matters as much as how it succeeds

Latency is a feature : Performance is part of the value proposition These realities shape every decision I make.

Banking APIs at Scale

At US Bank, I work on APIs that power enterprise banking operations.

Banking API challenges:

Regulatory compliance is non-negotiable

Security requirements exceed typical standards

Availability expectations approach 100%

Integration with legacy systems is inevitable

Audit trails are built into everything These constraints make banking API products uniquely challenging.

Lessons from the Journey

Each role taught me something essential:

From Business Analyst:

How to translate business problems into clear requirements

The value of thorough analysis before building **From Product Owner:**

How to prioritize ruthlessly when resources are limited

The importance of stakeholder alignment **From Technical API PM:**

How technical decisions create or destroy business value

Why developer experience determines API success

Advice for the Transition

For analysts considering product management:

What to focus on:

Learn enough technical depth to have meaningful conversations

Practice thinking in outcomes, not just outputs

Build relationships across engineering, design, and business

Start making decisions, even small ones, and own the results

Get comfortable with ambiguity; product work is never fully defined The analytical skills you have are assets. The product skills can be learned.

Looking Forward

My journey from Amazon BA to Technical API PM taught me that the best product managers combine domain expertise, technical understanding, and business acumen. Each role prepared me for the next, and the path continues to evolve.

Building API Products in Enterprise Banking: What I've Learned

Pallavi skipped presentations and built real AI products.

Pallavi Rajmohan was part of the November 2025 cohort at Curious PM, alongside 20 other talented participants.