Product Manager - Derivatives
. Use - for lists,
for prose. Remove boilerplate: EEO etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. We need to preserve all substantive information.
We need to decide sections: About the role (maybe "Your Role" content). Responsibilities (THINGS YOU GET TO DO). Requirements (WHO YOU ARE (MUST-HAVES)). Qualifications maybe same as Requirements? Could combine but we need separate if content. Skills maybe from WHO YOU MIGHT BE (NICE-TO-HAVES). Benefits from "How We Take Care of You". Pay and Schedule only if present: there is no explicit pay or schedule; only "Competitive Salary & Stock Options" under benefits. No explicit schedule. So we should not create Pay or Schedule sections.
We need to avoid headings with filler. So include sections: About the role, Responsibilities, Requirements, Skills, Benefits. Possibly Qualifications could be merged with Requirements but we can include Qualifications if we have content like degree, years experience. The "WHO YOU ARE (MUST-HAVES)" includes degree, experience, etc. That could be Qualifications. Requirements could be the same? Actually typical: Requirements are must-haves, Qualifications are nice-to-haves. But we have both must-haves and nice-to-haves. So we can map: Requirements = MUST-HAVES, Qualifications = NICE-TO-HAVES. Skills maybe from nice-to-haves? But we already have nice-to-haves as Qualifications. However the instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should try to map content to these headings. We have:
- About the role: could be "Your Role" paragraph describing role.
- Responsibilities: "THINGS YOU GET TO DO" list.
- Requirements: "WHO YOU ARE (MUST-HAVES)" list.
- Qualifications: maybe "WHO YOU MIGHT BE (NICE-TO-HAVES)" list.
- Skills: maybe we could extract technical skills from must-haves/nice-to-haves? But we could also leave Skills empty? But we must not emit heading with filler. So if we don't have specific skills content separate, we should omit Skills section. However we could treat some of the nice-to-haves as skills (e.g., technical background, NFA Series 3, etc.) but they are already in Qualifications. To avoid duplication, maybe we combine must-haves as Requirements, nice-to-haves as Qualifications, and omit Skills.
- Benefits: "How We Take Care of You" list.
We need to preserve all substantive information: include who we are? The "Who We Are" paragraph is about company; maybe we could include as part of About the role? But the instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. The "Who We Are" is company overview; could be included as a paragraph before sections? The instruction says output only HTML fragment; we can include a
for company overview if we want, but we need to follow heading usage. There's no heading for company overview; we could just put a
at start.
We must remove boilerplate: EEO, recruitment privacy policy, etc.
Let's extract content:
Who We Are: Alpaca is a US-headquartered, global leader in agent-first brokerage infrastructure for stocks, ETFs, options, crypto, fixed income, 24/5 trading, and more. Amongst our subsidiaries, Alpaca is a licensed financial services company, serving hundreds of financial institutions across 40 countries with our institutional-grade APIs. This includes broker-dealers, investment advisors, wealth managers, hedge funds, and crypto exchanges, totalling over 10 million brokerage accounts. Our global team is a diverse group of experienced engineers, traders, and brokerage professionals who are working to achieve our mission of opening financial services to everyone on the planet. We're deeply committed to open-source contributions and fostering a vibrant community, continuously enhancing our award-winning, developer-friendly API and the robust infrastructure behind it. Alpaca is proudly backed by $400 million in funding from top-tier global investors including Portage Ventures, Spark Capital, Tribe Capital, Social Leverage, Horizons Ventures, Opera Tech Ventures, SBI Group, Derayah Financial, Unbound, Peak XV, Elefund, and Y Combinator. Our Team Members: We're a dynamic team of 400+ globally distributed members who thrive working from our favorite places around the world, with teammates spanning the USA, Canada, Japan, Hungary, Nigeria, Brazil, the UK, and beyond! We're searching for passionate individuals eager to contribute to Alpaca's rapid growth. If you align with our core values—Stay Curious, Have Empathy, and Be Accountable—and are ready to make a significant impact, we encourage you to apply.
Your Role: Alpaca's brokerage product team is looking for a Product Manager to define and drive new product initiatives and manage a portfolio of existing products across Alpaca Derivatives, the firm's regulated FCM. In this role you will be responsible for the creation and delivery of the roadmap for futures and prediction markets features while closely collaborating with internal management and business stakeholders across Alpaca. With a deep understanding of the derivatives regulatory landscape - including the CFTC, NFA, designated contract markets, trading, settlement, market data, and clearing organizations - you will shape the product strategy that enables Alpaca to launch and scale its FCM, and to bring listed futures and prediction markets onto the Alpaca platform.
THINGS YOU GET TO DO
Product Ownership & Strategy
Own derivatives products for Alpaca, with a primary focus on listed futures and prediction markets.
Drive derivatives product strategy by analyzing ROI, market competition, regulatory requirements, and build-vs-buy scenarios across venues, clearing, and execution.
Contribute to the product roadmap and product strategy with a focus on FCM launch readiness, CFTC/NFA-compliant features, and partner demand for futures and prediction markets.
Write product requirements and work with engineers to execute builds that meet regulatory, exchange, and clearing standards.
Stakeholder Engagement & Regulatory
Lead customer and partner calls around derivatives process and product issues to gain insights and translate them into product improvements for Broker API and Trading API clients.
Participate in engagements with the CFTC, NFA, exchanges, and clearing organizations to drive product strategy and ensure regulatory alignment.
Report timely and accurately on product status and results to internal and external stakeholders, including regional partners and institutional clients.
Operations & Efficiency
Improve derivatives operation efficiency by providing solutions and owning the metrics, with a focus on margin, clearing, settlement, and trading-risk workflows.
Collaborate with operations, risk, and compliance teams to ensure seamless integration between Alpaca's global platform and the FCM market infrastructure.
Ad hoc duties and projects as assigned.
WHO YOU ARE (MUST-HAVES)
Excited about what Alpaca is building and passionate about expanding derivatives infrastructure for futures and prediction markets.
Strong understanding of CFTC and NFA frameworks, FCM market structure, and the listed derivatives landscape.
Bachelor's degree in computer science, engineering, finance, or equivalent.
5+ years of experience in Product Management, Engineering, Consulting, and/or starting a startup, preferably within financial services, fintech, or derivatives.
Demonstrated interest and experience in futures, prediction markets, listed derivatives, or adjacent trading / brokerage infrastructure.
Strong communication skills, both written and verbal, with excellent collaboration abilities.
Business acumen to understand tradeoffs between stakeholders and technology feasibility with time and budget constraints.
WHO YOU MIGHT BE (NICE-TO-HAVES)
Experience and background working on and developing futures, prediction markets, or other listed derivatives products.
Technical background working with APIs, particularly in financial services or trading platforms.
NFA Series 3 (or the ability to obtain it), or other CFTC/NFA-recognized credentials.
Experience launching or operating inside an FCM, DCM, DCO, or other regulated derivatives venue.
Familiarity with portfolio margin, cross-asset margin, institutional execution, or Prime Brokerage-adjacent workflows.
Experience working at a fintech, startup, broker-dealer, FCM, or exchange.
Knowledge of prediction market structure, event-contract design, and the regulatory overlay that sits on top of it.
How We Take Care of You:
Competitive Salary & Stock Options
Health Benefits
New Hire Home-Office Setup: One-time USD $500
Monthly Stipend: USD $150 per month via a Brex Card
We need to output HTML fragment.
We'll start with a
for company overview (Who We Are + Team Members + values). Could combine into one or two paragraphs.
Then
About the role
with containing the "Your Role" paragraph.
Then
Responsibilities
with - for each bullet under THINGS YOU GET TO DO. Need to preserve subheadings? Could treat each bullet as list item; subheadings like "Product Ownership & Strategy" could be bold? But we should not add extra formatting beyond HTML; we could keep them as part of list item text.
We need to preserve all substantive information; we can keep the subheadings as part of the list item text.
Similarly for Requirements (MUST-HAVES) as
- .
Qualifications (NICE-TO-HAVES) as
- .
Benefits as
- .
We must not include Pay or Schedule sections.
We must not include any filler like "commensurate with experience". Not present.
We must remove duplicated lines: none.
We must remove boilerplate: EEO etc.
Let's craft HTML.
We'll need to escape any special characters? Not needed.
We'll produce:
Alpaca is a US-headquartered, global leader in agent-first brokerage infrastructure for stocks, ETFs, options, crypto, fixed income, 24/5 trading, and more. Amongst our subsidiaries, Alpaca is a licensed financial services company, serving hundreds of financial institutions across 40 countries with our institutional-grade APIs. This includes broker-dealers, investment advisors, wealth managers, hedge funds, and crypto exchanges, totalling over 10 million brokerage accounts. Our global team is a diverse group of experienced engineers, traders, and brokerage professionals who are working to achieve our mission of opening financial services to everyone on the planet. We're deeply committed to open-source contributions and fostering a vibrant community, continuously enhancing our award-winning, developer-friendly API and the robust infrastructure behind it. Alpaca is proudly backed by $400 million in funding from top-tier global investors including Portage Ventures, Spark Capital, Tribe Capital, Social Leverage, Horizons Ventures, Opera Tech Ventures, SBI Group, Derayah Financial, Unbound, Peak XV, Elefund, and Y Combinator. Our Team Members: We're a dynamic team of 400+ globally distributed members who thrive working from our favorite places around the world, with teammates spanning the USA, Canada, Japan, Hungary, Nigeria, Brazil, the UK, and beyond! We're searching for passionate individuals eager to contribute to Alpaca's rapid growth. If you align with our core values—Stay Curious, Have Empathy, and Be Accountable—and are ready to make a significant impact, we encourage you to apply.
About
for prose. Remove boilerplate: EEO etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. We need to preserve all substantive information. We need to decide sections: About the role (maybe "Your Role" content). Responsibilities (THINGS YOU GET TO DO). Requirements (WHO YOU ARE (MUST-HAVES)). Qualifications maybe same as Requirements? Could combine but we need separate if content. Skills maybe from WHO YOU MIGHT BE (NICE-TO-HAVES). Benefits from "How We Take Care of You". Pay and Schedule only if present: there is no explicit pay or schedule; only "Competitive Salary & Stock Options" under benefits. No explicit schedule. So we should not create Pay or Schedule sections. We need to avoid headings with filler. So include sections: About the role, Responsibilities, Requirements, Skills, Benefits. Possibly Qualifications could be merged with Requirements but we can include Qualifications if we have content like degree, years experience. The "WHO YOU ARE (MUST-HAVES)" includes degree, experience, etc. That could be Qualifications. Requirements could be the same? Actually typical: Requirements are must-haves, Qualifications are nice-to-haves. But we have both must-haves and nice-to-haves. So we can map: Requirements = MUST-HAVES, Qualifications = NICE-TO-HAVES. Skills maybe from nice-to-haves? But we already have nice-to-haves as Qualifications. However the instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should try to map content to these headings. We have: - About the role: could be "Your Role" paragraph describing role. - Responsibilities: "THINGS YOU GET TO DO" list. - Requirements: "WHO YOU ARE (MUST-HAVES)" list. - Qualifications: maybe "WHO YOU MIGHT BE (NICE-TO-HAVES)" list. - Skills: maybe we could extract technical skills from must-haves/nice-to-haves? But we could also leave Skills empty? But we must not emit heading with filler. So if we don't have specific skills content separate, we should omit Skills section. However we could treat some of the nice-to-haves as skills (e.g., technical background, NFA Series 3, etc.) but they are already in Qualifications. To avoid duplication, maybe we combine must-haves as Requirements, nice-to-haves as Qualifications, and omit Skills. - Benefits: "How We Take Care of You" list. We need to preserve all substantive information: include who we are? The "Who We Are" paragraph is about company; maybe we could include as part of About the role? But the instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. The "Who We Are" is company overview; could be included as a paragraph before sections? The instruction says output only HTML fragment; we can include a
for company overview if we want, but we need to follow heading usage. There's no heading for company overview; we could just put a
at start. We must remove boilerplate: EEO, recruitment privacy policy, etc. Let's extract content: Who We Are: Alpaca is a US-headquartered, global leader in agent-first brokerage infrastructure for stocks, ETFs, options, crypto, fixed income, 24/5 trading, and more. Amongst our subsidiaries, Alpaca is a licensed financial services company, serving hundreds of financial institutions across 40 countries with our institutional-grade APIs. This includes broker-dealers, investment advisors, wealth managers, hedge funds, and crypto exchanges, totalling over 10 million brokerage accounts. Our global team is a diverse group of experienced engineers, traders, and brokerage professionals who are working to achieve our mission of opening financial services to everyone on the planet. We're deeply committed to open-source contributions and fostering a vibrant community, continuously enhancing our award-winning, developer-friendly API and the robust infrastructure behind it. Alpaca is proudly backed by $400 million in funding from top-tier global investors including Portage Ventures, Spark Capital, Tribe Capital, Social Leverage, Horizons Ventures, Opera Tech Ventures, SBI Group, Derayah Financial, Unbound, Peak XV, Elefund, and Y Combinator. Our Team Members: We're a dynamic team of 400+ globally distributed members who thrive working from our favorite places around the world, with teammates spanning the USA, Canada, Japan, Hungary, Nigeria, Brazil, the UK, and beyond! We're searching for passionate individuals eager to contribute to Alpaca's rapid growth. If you align with our core values—Stay Curious, Have Empathy, and Be Accountable—and are ready to make a significant impact, we encourage you to apply. Your Role: Alpaca's brokerage product team is looking for a Product Manager to define and drive new product initiatives and manage a portfolio of existing products across Alpaca Derivatives, the firm's regulated FCM. In this role you will be responsible for the creation and delivery of the roadmap for futures and prediction markets features while closely collaborating with internal management and business stakeholders across Alpaca. With a deep understanding of the derivatives regulatory landscape - including the CFTC, NFA, designated contract markets, trading, settlement, market data, and clearing organizations - you will shape the product strategy that enables Alpaca to launch and scale its FCM, and to bring listed futures and prediction markets onto the Alpaca platform. THINGS YOU GET TO DO Product Ownership & Strategy Own derivatives products for Alpaca, with a primary focus on listed futures and prediction markets. Drive derivatives product strategy by analyzing ROI, market competition, regulatory requirements, and build-vs-buy scenarios across venues, clearing, and execution. Contribute to the product roadmap and product strategy with a focus on FCM launch readiness, CFTC/NFA-compliant features, and partner demand for futures and prediction markets. Write product requirements and work with engineers to execute builds that meet regulatory, exchange, and clearing standards. Stakeholder Engagement & Regulatory Lead customer and partner calls around derivatives process and product issues to gain insights and translate them into product improvements for Broker API and Trading API clients. Participate in engagements with the CFTC, NFA, exchanges, and clearing organizations to drive product strategy and ensure regulatory alignment. Report timely and accurately on product status and results to internal and external stakeholders, including regional partners and institutional clients. Operations & Efficiency Improve derivatives operation efficiency by providing solutions and owning the metrics, with a focus on margin, clearing, settlement, and trading-risk workflows. Collaborate with operations, risk, and compliance teams to ensure seamless integration between Alpaca's global platform and the FCM market infrastructure. Ad hoc duties and projects as assigned. WHO YOU ARE (MUST-HAVES) Excited about what Alpaca is building and passionate about expanding derivatives infrastructure for futures and prediction markets. Strong understanding of CFTC and NFA frameworks, FCM market structure, and the listed derivatives landscape. Bachelor's degree in computer science, engineering, finance, or equivalent. 5+ years of experience in Product Management, Engineering, Consulting, and/or starting a startup, preferably within financial services, fintech, or derivatives. Demonstrated interest and experience in futures, prediction markets, listed derivatives, or adjacent trading / brokerage infrastructure. Strong communication skills, both written and verbal, with excellent collaboration abilities. Business acumen to understand tradeoffs between stakeholders and technology feasibility with time and budget constraints. WHO YOU MIGHT BE (NICE-TO-HAVES) Experience and background working on and developing futures, prediction markets, or other listed derivatives products. Technical background working with APIs, particularly in financial services or trading platforms. NFA Series 3 (or the ability to obtain it), or other CFTC/NFA-recognized credentials. Experience launching or operating inside an FCM, DCM, DCO, or other regulated derivatives venue. Familiarity with portfolio margin, cross-asset margin, institutional execution, or Prime Brokerage-adjacent workflows. Experience working at a fintech, startup, broker-dealer, FCM, or exchange. Knowledge of prediction market structure, event-contract design, and the regulatory overlay that sits on top of it. How We Take Care of You: Competitive Salary & Stock Options Health Benefits New Hire Home-Office Setup: One-time USD $500 Monthly Stipend: USD $150 per month via a Brex Card We need to output HTML fragment. We'll start with a
for company overview (Who We Are + Team Members + values). Could combine into one or two paragraphs. Then
About the role
withcontaining the "Your Role" paragraph. Then
Responsibilities
with- for each bullet under THINGS YOU GET TO DO. Need to preserve subheadings? Could treat each bullet as list item; subheadings like "Product Ownership & Strategy" could be bold? But we should not add extra formatting beyond HTML; we could keep them as part of list item text.
We need to preserve all substantive information; we can keep the subheadings as part of the list item text.
Similarly for Requirements (MUST-HAVES) as
- .
Qualifications (NICE-TO-HAVES) as
- .
Benefits as
- .
We must not include Pay or Schedule sections.
We must not include any filler like "commensurate with experience". Not present.
We must remove duplicated lines: none.
We must remove boilerplate: EEO etc.
Let's craft HTML.
We'll need to escape any special characters? Not needed.
We'll produce:
Alpaca is a US-headquartered, global leader in agent-first brokerage infrastructure for stocks, ETFs, options, crypto, fixed income, 24/5 trading, and more. Amongst our subsidiaries, Alpaca is a licensed financial services company, serving hundreds of financial institutions across 40 countries with our institutional-grade APIs. This includes broker-dealers, investment advisors, wealth managers, hedge funds, and crypto exchanges, totalling over 10 million brokerage accounts. Our global team is a diverse group of experienced engineers, traders, and brokerage professionals who are working to achieve our mission of opening financial services to everyone on the planet. We're deeply committed to open-source contributions and fostering a vibrant community, continuously enhancing our award-winning, developer-friendly API and the robust infrastructure behind it. Alpaca is proudly backed by $400 million in funding from top-tier global investors including Portage Ventures, Spark Capital, Tribe Capital, Social Leverage, Horizons Ventures, Opera Tech Ventures, SBI Group, Derayah Financial, Unbound, Peak XV, Elefund, and Y Combinator. Our Team Members: We're a dynamic team of 400+ globally distributed members who thrive working from our favorite places around the world, with teammates spanning the USA, Canada, Japan, Hungary, Nigeria, Brazil, the UK, and beyond! We're searching for passionate individuals eager to contribute to Alpaca's rapid growth. If you align with our core values—Stay Curious, Have Empathy, and Be Accountable—and are ready to make a significant impact, we encourage you to apply.
About
- .
We must not include Pay or Schedule sections.
We must not include any filler like "commensurate with experience". Not present.
We must remove duplicated lines: none.
We must remove boilerplate: EEO etc.
Let's craft HTML.
We'll need to escape any special characters? Not needed.
We'll produce:
- .
Benefits as
- .
Qualifications (NICE-TO-HAVES) as