jobsearch v0.0.1

← alpaca / Product Manager, New Assets

brief / art_ooiQyAvyUPM

role
alpaca / Product Manager, New Assets
model
anthropic/claude-sonnet-4.6
created
2026-06-09T05:00

Company snapshot

Alpaca is a US-headquartered self-clearing broker-dealer providing brokerage infrastructure APIs for stocks, ETFs, options, crypto, fixed income, and 24/5 trading, serving hundreds of financial institutions across 40 countries with over 9 million brokerage accounts. The company raised a Series D bringing total funding to over $320 million, signaling aggressive expansion into new asset classes and global markets. Alpaca's core value proposition is developer-first, institutional-grade APIs enabling the B2B2C correspondent/broker-as-a-service model. The company is known for its open-source contributions and award-winning developer experience. Engineering reputation is generally positive in the fintech/API space; specific internal team culture details are not publicly confirmed beyond their stated values of curiosity, empathy, and accountability.

Team stack

Based on the JD and public signals: REST and likely FIX protocol APIs for trading (explicitly mentioned in JD); Go or Python microservices likely given fintech API norms; PostgreSQL or similar relational DB for order/account data (likely); cloud infrastructure likely AWS given industry norms (uncertain); BI tooling likely Looker, Metabase, or similar with SQL-based data access (JD requires SQL + BI tool); internal OMS/EMS systems for order routing (based on JD references to smart order routing and venue connectivity); compliance and regulatory reporting pipelines (CAT/OATS referenced in JD); partner-facing SDKs in Python and possibly JavaScript/TypeScript (based on developer-facing API focus); documentation tooling likely Readme.io or similar (inferred from developer portal emphasis).

Likely questions (10)

areaquestionwhy
domain Walk us through a specific asset class or trading product you've shipped end-to-end — what was the API surface, what compliance or regulatory constraints did you navigate, and how did you measure partner adoption post-GA? The JD's #1 must-have is demonstrated depth on at least one trading surface shipped to production scale; this is the core qualification screen.
system_design How would you design the API contract for a new asset class — say, Money Market Funds — for a B2B2C broker-as-a-service platform? Walk through the key endpoints, order lifecycle states, error handling, and what documentation you'd ship alongside it. The role explicitly requires owning API design and producing documentation partners can implement against; MMFs are listed as a target asset class.
behavioral Tell me about a time you had to push back on a partner or stakeholder request that didn't fit the platform. How did you handle it without over-promising, and what was the outcome? The JD explicitly calls out 'push back on requests that don't fit the platform without over-promising' as a core behavior expected in discovery and backlog management.
domain How familiar are you with Reg NMS, Reg SHO, or FINRA best execution rules? Describe a product decision you made that was directly shaped by one of these regulatory frameworks. The JD lists US market structure and regulatory frameworks as a nice-to-have but the role requires shipping in parallel with compliance/legal in a regulated environment — this will be probed.
coding Given a table of partner orders with columns (partner_id, order_id, asset_class, status, created_at, filled_at), write a SQL query to identify partners with order success rates below 80% in the last 30 days, ranked by total order volume. The JD explicitly requires SQL and BI tool proficiency; tracking order success rate is listed as a key metric the PM owns.
behavioral Describe how you currently use AI tools (Cursor, Claude, ChatGPT, or custom agents) in your day-to-day PM workflow — PRD drafting, customer call synthesis, data exploration, or prototyping. The JD lists 'AI-native PM workflow' as a nice-to-have and Alpaca is a tech-forward company; your background building AI tooling makes this a strong differentiator to probe.
behavioral You're shipping a new trading capability and compliance has a blocker that could delay GA by 6 weeks. Engineering is ready. Partners are waiting. How do you manage the situation? The JD emphasizes 'shipping in parallel with compliance, legal, and market-structure teams' — this tests judgment in a regulated, multi-stakeholder environment.
domain Alpaca's customers are developers and financial institutions, not retail end users. How does your approach to discovery, PRD writing, and success metrics change when the primary customer is a developer integrating an API versus a consumer using a UI? B2B/developer-facing product experience is a must-have; the JD stresses partner adoption and production usage as the success measure, not ship dates.
culture This role is globally distributed and requires coordinating across engineering, broker-dealer ops, compliance, legal, and partnerships simultaneously. How do you stay aligned and maintain velocity across that many async stakeholders? Alpaca is 380+ globally distributed; the role touches the most cross-functional stakeholder set in the trading area — async coordination ability is implicitly required.
system_design How would you think about exception handling and operational automation for a new asset class integration — what are the failure modes in a trading pipeline, and how would you prioritize building partner-facing tooling to surface and resolve them? The JD explicitly calls out 'exception handling, partner-facing tooling, automation of repetitive ops' as owned by this PM — this tests operational depth beyond pure product thinking.

Talking points