Senior Product Manager - Platform Infrastructure
Apex Fintech Solutions · Austin, TX · 1 mo ago
HybridInformation TechnologyFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "Who We Are", "About This Role", "About The Team", "The Role", "What You'll Do", "What We're Looking For", "Why Join Us?", "Our Rewards". Also there is "EEO Statement" and "Disability Statement" which we must remove (boilerplate). Also "Please note this job description is not designed..." is boilerplate, remove. Also "Our Rewards" includes benefits. Also "Why Join Us?" includes description. Also "Our Rewards" includes benefits list. Also "Our Rewards" includes hybrid work schedule (schedule). Also "Our Rewards" includes healthcare benefits etc. Also "Our Rewards" includes paid subscription to Calm app, learning reimbursement. Also "Our Rewards" includes hybrid work schedule. Also "Our Rewards" includes 401k match, parental leave, HSA contribution match.
We need sections: About the role? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content accordingly.
We have "About This Role" which includes "About The Team", "The Role". Could be "About the role". We'll combine that into a section
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content accordingly.
We have "About This Role" which includes "About The Team", "The Role". Could be "About the role". We'll combine that into a section About the role
with prose.
Then "What You'll Do" is responsibilities -> Responsibilities
with - items.
Then "What We're Looking For" is qualifications/requirements -> could be
Requirements
or Qualifications
. Use Requirements.
Then "Why Join Us?" maybe could be part of Benefits? But we have separate "Our Rewards" which includes benefits and schedule. So we can have Benefits
with list of benefits. Also schedule: hybrid work schedule -> Schedule
. Pay: not mentioned, so omit Pay section.
We also have "Who We Are" which is company overview; could be omitted? The instruction: 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
"Who We Are" is substantive about company; we could include as a section maybe "About the company"? But not in the list of headings. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. Probably we should stick to those headings only if content exists. "Who We Are" could be considered "About the role"? No. Might be better to include as a
before sections? The instruction: preserve ALL substantive information. So we need to include that info somewhere. Could put it as a
before the first heading, or as a section like
About the company
but not in list. However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for sections; but we could also use other headings if needed? Safer to follow the pattern: we can treat "Who We Are" as part of "About the role"? Not exactly. Could incorporate into "About the role" section as introductory prose. That would preserve info.
Thus we will create:
About the role
Who We Are ... (the company description) ... About This Role ... About The Team ... The Role ...
But that may be too long; but okay.
Then responsibilities list.
Then requirements list.
Then benefits list.
Then schedule.
We must not include Pay.
Now extract details.
Let's parse the posting.
Who We Are: Apex Fintech Solutions (Apex) powers innovation... (full paragraph). We'll keep that.
About This Role: includes About The Team, The Role.
We'll combine.
Let's extract About The Team paragraph:
"About The Team The Cloud Build, Provisioning & Automation team builds and runs the cloud platform infrastructure behind Apex's core business. We handle cloud platform builds across AWS, GCP, and Azure, manage cloud costs, enable migrations between on-prem and cloud environments, and drive infrastructure automation. Our goal is simple: keep Apex's cloud fast, reliable, and cost-efficient."
The Role paragraph:
"The Role You'll co-own the product roadmap for our cloud infrastructure portfolio — from migrations and provisioning automation to cost optimization and AI-driven platform improvements across AWS, GCP, and Azure. You'll work side-by-side with other Product leaders, engineers and stakeholders, turning business needs into clear priorities and shipping results. You'll also be the team's voice across the organization, making sure our impact is visible and well understood. This role is hands-on. You'll dig into technical problems, evaluate build vs. buy decisions, and use AI to drive strategic value across the platform. Over time, you'll grow into a technical product leader and become the face of the team."
We'll combine these into About the role section.
Now Responsibilities: "What You'll Do" bullet points (they are sentences but not bullet list). We need to turn each into - . Let's list them:
- Roadmap & Strategy
* Own and prioritize the roadmap for cloud migrations, provisioning automation, and platform builds across AWS, GCP, and Azure
* Develop and share strategic insights that impact key projects in your product area.
* Build an AI-first roadmap — identify where AI and automation can accelerate delivery, reduce cost, and improve platform reliability
* Evaluate build vs. buy for technology solutions; make clear, data-backed recommendations
* Break large initiatives into well-defined epics, stories, and requirements that are well-understood by both business and technical oriented audiences
* Independently maintain a well refined product backlog spanning at least 2 quarters
* Drive the creation of 1-2 year feature area strategy based on team priorities and market research
* Produce data-driven insights through qualitative and quantitative means that inform strategy for your product area
- Cloud Cost & Engineering
* Analyze cloud usage across AWS, GCP, and Azure to identify cost optimization opportunities
* Partner with engineering and finance to implement cost-saving measures and track results
* Develop a working understanding of cloud engineering and architectural concepts (networking, compute, storage, IaC, CI/CD) across major cloud providers
- Delivery & Execution
* Effectively manage end-to-end delivery of infrastructure projects — on time, in scope, both independently and in partnership with Program Management.
* Lead an engineering group to remove roadblocks and streamline execution while ensuring quality standards are met
* Drive the creation and efficacy of all team ceremonies
* Set OKRs, track success metrics (project timelines, cost savings, migration milestones), and communicate progress
* Manage projects with some ambiguity and multiple inbound/outbound dependencies independently
* Effectively balance speed and quality
- Cross-Functional Collaboration & Vendor Management
* Work with cross-functional teams to design scalable solutions and get hands-on when needed
* Maintain and grow partnerships with cloud vendors (AWS, GCP, Azure) and tooling partners
* Coordinate objectives, timelines, and dependencies (both inbound & outbound) across teams to minimize operational impact
- AI & Technology Curiosity
* Use AI tools and techniques to bring strategic value — from automating workflows to generating insights from platform data
* Stay curious about emerging cloud and AI technologies; bring ideas back to the team and roadmap
- Team Advocacy & Development
* Serve as the face of the team — communicate progress, wins, and impact to leadership and stakeholders
* Provide advice and mentorship to junior team members; share customer and platform insights to elevate the team
* Build the team's reputation for reliability and delivery excellence
We'll output each as
- .
Now Requirements: "What We're Looking For" bullet list:
- 8+ years in product management, program management, solution architecture or a similar role in cloud infrastructure or platform engineering
- Working knowledge of cloud platforms (GCP, AWS, Azure), infrastructure provisioning (Terraform, Ansible), and platform engineering and a proven track record leveraging & optimizing these technologies.
- Experience evaluating build vs. buy decisions for technology solutions
- Strong analytical skills — you can compile research, analyze data, and produce insights independently
- Good understanding of cloud cost levers and FinOps concepts across multiple cloud providers
- Comfort with technical product design discussions across multiple engineering teams
- Strong written and verbal communication — you can create AI prototypes, PRDs, status updates, and stakeholder-facing docs with minimal oversight
- Ability to manage multiple projects, balance competing priorities, and deliver in a fast-paced environment
- Genuine curiosity about AI, automation, and how to apply them to platform and infrastructure problems
- Experience managing or growing vendor relationships is a plus
We'll output as
- .
Now Benefits: "Our Rewards" paragraph:
"We offer a robust package of employee perks and benefits, including healthcare benefits (medical, dental and vision, EAP), competitive PTO, 401k match, parental leave, and HSA contribution match. We also provide our employees with a paid subscription to the Calm app and offer generous external learning and tuition reimbursement benefits."
We'll list each benefit as
- .
Now Schedule: "At AFS, we offer a hybrid work schedule for most roles that allows employees to have the flexibility of working from home and one of our primary offices."
We'll output as
maybe under Schedule heading:
Schedule
Hybrid work schedule: flexibility to work from home and one of our primary offices.
Now we must not include EEO statement etc.
Now ensure we don't repeat job title as heading. We are not.
Now output HTML fragment only.
Let's craft.
We'll start with About the role
... combined text ...
Make sure to preserve all substantive info from Who We Are, About The Team, The Role.
We'll combine them into a single paragraph maybe with sentences.
Let's write:
Who We Are: Apex Fintech Solutions (Apex) powers innovation and the future of digital wealth management by building tech-forward solutions that help simplify, automate, and facilitate access to financial markets for all. Our robust suite of fintech software enables us to support clients such as Stash, Betterment, SoFi, Webull, and eToro, amongst many others; collectively, Apex powers access to the stock market for over 22+ million end customers. At Apex, we are changing how the securities industry operates by reinventing the status quo, which was manual, slow, and accessible only by the ultra-wealthy. We're digitizing and democratizing systems so that everyone has an opportunity to invest. When you're at Apex, you drive this change. You're part of a global team with a clear vision: to be the trusted technology that powers the digital economy. Our offices in Austin, Dallas, Chicago, New York, Portland, Belfast, and Manila are home to over 1,000 employees. Together, we’re shaping the future of financial innovation. Embrace change. Solve big. Win together. And be G.R.E.A.T. — grit, results, empathy, accountability, and teamwork — with Apex. We’re proud to be recognized for the innovative work we do, the purpose-driven nature of our work, and the collaborative culture we’ve created. Here are just a few of the many awards we’ve recently received: Best Places to Work 20
Requirements
orQualifications
. Use Requirements. Then "Why Join Us?" maybe could be part of Benefits? But we have separate "Our Rewards" which includes benefits and schedule. So we can haveBenefits
with list of benefits. Also schedule: hybrid work schedule ->Schedule
. Pay: not mentioned, so omit Pay section. We also have "Who We Are" which is company overview; could be omitted? The instruction: 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 shortor drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Who We Are" is substantive about company; we could include as a section maybe "About the company"? But not in the list of headings. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. Probably we should stick to those headings only if content exists. "Who We Are" could be considered "About the role"? No. Might be better to include as a
before sections? The instruction: preserve ALL substantive information. So we need to include that info somewhere. Could put it as a
before the first heading, or as a section like
About the company
but not in list. However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for sections; but we could also use other headings if needed? Safer to follow the pattern: we can treat "Who We Are" as part of "About the role"? Not exactly. Could incorporate into "About the role" section as introductory prose. That would preserve info.
Thus we will create:
About the role
Who We Are ... (the company description) ... About This Role ... About The Team ... The Role ...
But that may be too long; but okay. Then responsibilities list. Then requirements list. Then benefits list. Then schedule. We must not include Pay. Now extract details. Let's parse the posting. Who We Are: Apex Fintech Solutions (Apex) powers innovation... (full paragraph). We'll keep that. About This Role: includes About The Team, The Role. We'll combine. Let's extract About The Team paragraph: "About The Team The Cloud Build, Provisioning & Automation team builds and runs the cloud platform infrastructure behind Apex's core business. We handle cloud platform builds across AWS, GCP, and Azure, manage cloud costs, enable migrations between on-prem and cloud environments, and drive infrastructure automation. Our goal is simple: keep Apex's cloud fast, reliable, and cost-efficient." The Role paragraph: "The Role You'll co-own the product roadmap for our cloud infrastructure portfolio — from migrations and provisioning automation to cost optimization and AI-driven platform improvements across AWS, GCP, and Azure. You'll work side-by-side with other Product leaders, engineers and stakeholders, turning business needs into clear priorities and shipping results. You'll also be the team's voice across the organization, making sure our impact is visible and well understood. This role is hands-on. You'll dig into technical problems, evaluate build vs. buy decisions, and use AI to drive strategic value across the platform. Over time, you'll grow into a technical product leader and become the face of the team." We'll combine these into About the role section. Now Responsibilities: "What You'll Do" bullet points (they are sentences but not bullet list). We need to turn each into- . Now Benefits: "Our Rewards" paragraph: "We offer a robust package of employee perks and benefits, including healthcare benefits (medical, dental and vision, EAP), competitive PTO, 401k match, parental leave, and HSA contribution match. We also provide our employees with a paid subscription to the Calm app and offer generous external learning and tuition reimbursement benefits." We'll list each benefit as
- .
Now Schedule: "At AFS, we offer a hybrid work schedule for most roles that allows employees to have the flexibility of working from home and one of our primary offices."
We'll output as
maybe under Schedule heading:
Schedule
Hybrid work schedule: flexibility to work from home and one of our primary offices.
Now we must not include EEO statement etc. Now ensure we don't repeat job title as heading. We are not. Now output HTML fragment only. Let's craft. We'll start withAbout the role
... combined text ...
Make sure to preserve all substantive info from Who We Are, About The Team, The Role. We'll combine them into a single paragraph maybe with sentences. Let's write: Who We Are: Apex Fintech Solutions (Apex) powers innovation and the future of digital wealth management by building tech-forward solutions that help simplify, automate, and facilitate access to financial markets for all. Our robust suite of fintech software enables us to support clients such as Stash, Betterment, SoFi, Webull, and eToro, amongst many others; collectively, Apex powers access to the stock market for over 22+ million end customers. At Apex, we are changing how the securities industry operates by reinventing the status quo, which was manual, slow, and accessible only by the ultra-wealthy. We're digitizing and democratizing systems so that everyone has an opportunity to invest. When you're at Apex, you drive this change. You're part of a global team with a clear vision: to be the trusted technology that powers the digital economy. Our offices in Austin, Dallas, Chicago, New York, Portland, Belfast, and Manila are home to over 1,000 employees. Together, we’re shaping the future of financial innovation. Embrace change. Solve big. Win together. And be G.R.E.A.T. — grit, results, empathy, accountability, and teamwork — with Apex. We’re proud to be recognized for the innovative work we do, the purpose-driven nature of our work, and the collaborative culture we’ve created. Here are just a few of the many awards we’ve recently received: Best Places to Work 20