Senior Platform Product Manager
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EOE etc. Also remove cookie/navigation/legal/EEO etc. Also remove duplicated lines. Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes Salary range, profit sharing, benefits description, flexible schedules. So we can have Pay (salary), Benefits, Schedule (flexible schedules). Also About the role (maybe "A Little Bit About Us" is about company, not role). But we need sections like About the role? The posting includes "What You'd Do In This Role" (responsibilities), "You're Probably a Match If" (requirements/qualifications/skills), "What Winning Looks Like" (maybe responsibilities or success metrics). Also "Other Stuff To Know" (mission etc). We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which sections have content.
We must not invent sections. Use for each heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information. Let's extract:
- Team: CDP Platform Team (maybe minor metadata, can be short p)
- Location: Franklin, TN—on-site, relocation assistance available, flexible schedules available
- Salary: $105,240–$156,600/year* + profit sharing + benefits Range depends on skill level and overall experience.
- A Little Bit About Us: description of Ramsey Solutions, mission.
- Our Mission: Ramsey Solutions provides biblically based...
- Here's a Taste Of Our Benefits: list of benefits.
- Where And How You'd Work: description of headquarters, on-site, flexible schedules, workspace, zones.
- What You'd Do In This Role: responsibilities.
- You're Probably a Match If: qualifications/requirements/skills.
- What Winning Looks Like: success metrics (maybe responsibilities or outcomes).
- Other Stuff To Know: mission passion, etc.
- EOE etc (remove).
We need to decide sections:
- About the role: maybe combine "A Little Bit About Us" and "Our Mission" and "Where And How You'd Work"? Actually "About the role" could be description of role context. But we have "What You'd Do In This Role" for responsibilities. So "About the role" could be overview of the role (maybe from "What You'd Do In This Role" summary?). But we need to not duplicate. Let's think: The posting includes a description of the role's purpose: "Ramsey is knitting together products... you'd stand right at the center of that work. You'll own the strategy and growth..." That's responsibilities. So we could put that under Responsibilities.
- About the role could be brief summary: maybe from "Team: CDP Platform Team" and location? But location is separate.
Better to use sections: About the role (maybe short paragraph about the role's purpose), Responsibilities (detailed duties), Requirements (qualifications), Skills (maybe separate), Benefits, Pay, Schedule.
We must not create sections with filler. Ensure each has real content.
Let's extract content for each:
About the role: Could be "You'll own the strategy and growth of our company-wide customer data platform, the operational backbone that helps product squads understand customers, spot high-leverage opportunities, and make faster, sharper decisions." plus maybe "You'll run discovery... partner closely with engineering..." That's responsibilities though.
Maybe we treat "What You'd Do In This Role" as Responsibilities. Then About the role could be a brief overview: maybe from "Team: CDP Platform Team" and "Location: Franklin, TN—on-site, relocation assistance available, flexible schedules available". But that's more metadata.
Alternatively, we could skip About the role if no specific content besides team and location. But we need to include sections only when posting has real specific content. The posting does have "Team: CDP Platform Team" and location details. That's specific. So we can make About the role section containing team and location info.
But location also relevant to Schedule? Actually schedule is flexible schedules.
Let's decide:
Section About the role: includes team (CDP Platform Team) and location (Franklin, TN—on-site, relocation assistance available). Also maybe mention that it's on-site with relocation assistance.
Section Responsibilities: from "What You'd Do In This Role" paragraph(s). Also maybe "What Winning Looks Like" could be considered responsibilities or success metrics; but we could incorporate into Responsibilities as bullet points.
Section Requirements: from "You're Probably a Match If" bullet points (5+ years product management experience, comfortable talking to stakeholders, built and tested product hypotheses, lead without formal authority, discovery mindset, explain complex CDP value). Also maybe "We're open to a background in engineering or another product-adjacent field, as long as you've recently worked in product management". That's requirement.
Section Skills: maybe we could extract skills like stakeholder communication, hypothesis testing, leadership without authority, discovery mindset, explaining complex concepts. But those overlap with requirements. Could combine Requirements and Skills? But we need to decide if we have enough distinct content for Skills separate. Might be better to put those under Requirements and not create Skills section if not distinct. However we can still create Skills section if we can list specific skills: stakeholder communication, product hypothesis testing, leadership without authority, discovery and discernment, explaining complex CDP value, roadmap creation, cross-functional leadership, risk management, measuring impact. Those are derived from responsibilities and winning looks like. Could be considered skills. But we must not invent; we need to base on posting. The posting does mention those as qualities. So we can treat them as skills.
But we need to avoid duplication. Perhaps better to have Requirements (experience, background) and Skills (abilities). Let's extract:
Requirements (experience/background):
- 5+ years of product management experience (open to engineering or product-adjacent background if recently worked in product management)
- Comfortable talking to stakeholders at every level, from product squad to senior leadership and board
- Built and tested product hypotheses by putting real concepts in front of users and learning from what actually happens
- Lead without needing formal authority, comfortable challenging a plan as executing one
- Bring a discovery and discernment mindset, always asking what customers actually need rather than assuming you already know
- Able to explain something as complex as a customer data platform's value to anyone in the building, whether engineer or executive
Skills could be similar; maybe we can combine. But we need to decide.
Alternatively, we could have Requirements (experience) and Skills (abilities). Let's split:
Requirements:
- 5+ years of product management experience (we're open to a background in engineering or another product-adjacent field, as long as you've recently worked in product management)
Skills:
- Comfortable talking to stakeholders at every level
- Built and tested product hypotheses by putting real concepts in front of users and learning from what actually happens
- Lead without needing formal authority, comfortable challenging a plan as executing one
- Bring a discovery and discernment mindset, always asking what customers actually need rather than assuming you already know
- Able to explain something as complex as a customer data platform's value to anyone in the building, whether engineer or executive
That seems reasonable.
Now Benefits: list from "Here's a Taste Of Our Benefits":
- Health insurance (includes plans eligible for an HSA—with a company match up to $500!)
- 401(k) retirement plan with 4% match/company contribution
- Annual wellness, counseling and grocery membership reimbursement
- On-campus cafe with subsidized pricing for breakfast, lunch and coffee bar
- Dependent care FSA
- Tons of cultural activities, like weekly devotional, leadership development courses, Battle of the Bands, and one epic Christmas party!
Pay: Salary range: $105,240–$156,600/year* + profit sharing + benefits. Range depends on skill level and overall experience.
Schedule: flexible schedules available (mentioned in location and Where And How You'd Work). Also "flexible work schedules to take the stress out of appointments, family obligations and other needs". So we can include schedule info.
Now About the role: Could include team and location details: Team: CDP Platform Team; Location: Franklin, TN—on-site, relocation assistance available. Also maybe mention that it's on-site with relocation assistance.
We also have "Where And How You'd Work" describing headquarters, on-site, flexible schedules, workspace, zones. Some of that overlaps with schedule and location. But we can incorporate location details there.
We need to avoid duplication. Let's craft About the role paragraph: "The role is on the CDP Platform Team at Ramsey Solutions headquarters in Franklin, TN (on-site). Relocation assistance is available." That's concise.
Now Responsibilities: combine "What You'd Do In This Role" and "What Winning Looks Like". Let's extract responsibilities:
From "What You'd Do In This Role":
- Own the strategy and growth of our company-wide customer data platform, the operational backbone that helps product squads understand customers, spot high-leverage opportunities, and make faster, sharper decisions.
- Run discovery rigorous enough to actually shape what gets built.
- Translate what you learn into a roadmap that connects platform capabilities to real outcomes.
- Partner closely with engineering to turn priorities into shipped work.
- Spend as much time building trust and clarity across the building as you do building the roadmap itself.
From "What Winning Looks Like":
- Build and own a customer data platform strategy that product squads actually use to move faster and make sharper decisions.
- Run a discovery rhythm rigorous enough to change direction, not just confirm it, and keep that evidence connected to what gets built.
- Translate discovery findings into requirements engineering can act on, including sizing effort and knowing when to push back.
- Lead cross-functional squads and stakeholders toward clear priorities without relying on formal authority.
- Keep a steady communication rhythm so stakeholders always know what's needed, what's coming, and what shipped.
- Raise risks and blockers early, with a plan attached, instead of absorbing them quietly.
- Tie platform decisions back to measurable business and product impact, in dollars where possible.
We can combine these into a bulleted list.
Now Requirements (experience): bullet: "5+ years of product management experience (we're open to a background in engineering or another product-adjacent field, as long as you've recently worked in product management)". That's one bullet.
Skills: bullet list of the abilities.
Now Benefits: bullet list.
Pay: paragraph with salary range and profit sharing.
Schedule: paragraph about flexible schedules.
Now we must ensure we don't include boilerplate like EOE etc. Remove.
Now produce HTML fragment: use
for each section heading. Use - for lists. Use
for prose.
We must not include or . Just fragment.
Let's order sections logically: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule.
Check each has content.
About the role: p with team and location.
Responsibilities: ul with li items.
Requirements: ul with li (one item).
Skills: ul with li items.
Benefits: ul with li items.
Pay: p.
Schedule: p.
Now ensure we preserve all substantive information. Did we miss any? Let's review original text for any other details:
- "Three decades later, Ramsey Solutions is a household name in personal finance, with a mission to change the toxic money culture for good." That's part of About Us; we omitted that. Could be included in About the role? Maybe we could add a sentence about mission in About the role? But About the role is about role, not company. However we could include
- for any list of duties/requirements/benefits. Use
for prose. We need to preserve all substantive information. Let's extract: - Team: CDP Platform Team (maybe minor metadata, can be short p) - Location: Franklin, TN—on-site, relocation assistance available, flexible schedules available - Salary: $105,240–$156,600/year* + profit sharing + benefits Range depends on skill level and overall experience. - A Little Bit About Us: description of Ramsey Solutions, mission. - Our Mission: Ramsey Solutions provides biblically based... - Here's a Taste Of Our Benefits: list of benefits. - Where And How You'd Work: description of headquarters, on-site, flexible schedules, workspace, zones. - What You'd Do In This Role: responsibilities. - You're Probably a Match If: qualifications/requirements/skills. - What Winning Looks Like: success metrics (maybe responsibilities or outcomes). - Other Stuff To Know: mission passion, etc. - EOE etc (remove). We need to decide sections: - About the role: maybe combine "A Little Bit About Us" and "Our Mission" and "Where And How You'd Work"? Actually "About the role" could be description of role context. But we have "What You'd Do In This Role" for responsibilities. So "About the role" could be overview of the role (maybe from "What You'd Do In This Role" summary?). But we need to not duplicate. Let's think: The posting includes a description of the role's purpose: "Ramsey is knitting together products... you'd stand right at the center of that work. You'll own the strategy and growth..." That's responsibilities. So we could put that under Responsibilities. - About the role could be brief summary: maybe from "Team: CDP Platform Team" and location? But location is separate. Better to use sections: About the role (maybe short paragraph about the role's purpose), Responsibilities (detailed duties), Requirements (qualifications), Skills (maybe separate), Benefits, Pay, Schedule. We must not create sections with filler. Ensure each has real content. Let's extract content for each: About the role: Could be "You'll own the strategy and growth of our company-wide customer data platform, the operational backbone that helps product squads understand customers, spot high-leverage opportunities, and make faster, sharper decisions." plus maybe "You'll run discovery... partner closely with engineering..." That's responsibilities though. Maybe we treat "What You'd Do In This Role" as Responsibilities. Then About the role could be a brief overview: maybe from "Team: CDP Platform Team" and "Location: Franklin, TN—on-site, relocation assistance available, flexible schedules available". But that's more metadata. Alternatively, we could skip About the role if no specific content besides team and location. But we need to include sections only when posting has real specific content. The posting does have "Team: CDP Platform Team" and location details. That's specific. So we can make About the role section containing team and location info. But location also relevant to Schedule? Actually schedule is flexible schedules. Let's decide: Section About the role: includes team (CDP Platform Team) and location (Franklin, TN—on-site, relocation assistance available). Also maybe mention that it's on-site with relocation assistance. Section Responsibilities: from "What You'd Do In This Role" paragraph(s). Also maybe "What Winning Looks Like" could be considered responsibilities or success metrics; but we could incorporate into Responsibilities as bullet points. Section Requirements: from "You're Probably a Match If" bullet points (5+ years product management experience, comfortable talking to stakeholders, built and tested product hypotheses, lead without formal authority, discovery mindset, explain complex CDP value). Also maybe "We're open to a background in engineering or another product-adjacent field, as long as you've recently worked in product management". That's requirement. Section Skills: maybe we could extract skills like stakeholder communication, hypothesis testing, leadership without authority, discovery mindset, explaining complex concepts. But those overlap with requirements. Could combine Requirements and Skills? But we need to decide if we have enough distinct content for Skills separate. Might be better to put those under Requirements and not create Skills section if not distinct. However we can still create Skills section if we can list specific skills: stakeholder communication, product hypothesis testing, leadership without authority, discovery and discernment, explaining complex CDP value, roadmap creation, cross-functional leadership, risk management, measuring impact. Those are derived from responsibilities and winning looks like. Could be considered skills. But we must not invent; we need to base on posting. The posting does mention those as qualities. So we can treat them as skills. But we need to avoid duplication. Perhaps better to have Requirements (experience, background) and Skills (abilities). Let's extract: Requirements (experience/background): - 5+ years of product management experience (open to engineering or product-adjacent background if recently worked in product management) - Comfortable talking to stakeholders at every level, from product squad to senior leadership and board - Built and tested product hypotheses by putting real concepts in front of users and learning from what actually happens - Lead without needing formal authority, comfortable challenging a plan as executing one - Bring a discovery and discernment mindset, always asking what customers actually need rather than assuming you already know - Able to explain something as complex as a customer data platform's value to anyone in the building, whether engineer or executive Skills could be similar; maybe we can combine. But we need to decide. Alternatively, we could have Requirements (experience) and Skills (abilities). Let's split: Requirements: - 5+ years of product management experience (we're open to a background in engineering or another product-adjacent field, as long as you've recently worked in product management) Skills: - Comfortable talking to stakeholders at every level - Built and tested product hypotheses by putting real concepts in front of users and learning from what actually happens - Lead without needing formal authority, comfortable challenging a plan as executing one - Bring a discovery and discernment mindset, always asking what customers actually need rather than assuming you already know - Able to explain something as complex as a customer data platform's value to anyone in the building, whether engineer or executive That seems reasonable. Now Benefits: list from "Here's a Taste Of Our Benefits": - Health insurance (includes plans eligible for an HSA—with a company match up to $500!) - 401(k) retirement plan with 4% match/company contribution - Annual wellness, counseling and grocery membership reimbursement - On-campus cafe with subsidized pricing for breakfast, lunch and coffee bar - Dependent care FSA - Tons of cultural activities, like weekly devotional, leadership development courses, Battle of the Bands, and one epic Christmas party! Pay: Salary range: $105,240–$156,600/year* + profit sharing + benefits. Range depends on skill level and overall experience. Schedule: flexible schedules available (mentioned in location and Where And How You'd Work). Also "flexible work schedules to take the stress out of appointments, family obligations and other needs". So we can include schedule info. Now About the role: Could include team and location details: Team: CDP Platform Team; Location: Franklin, TN—on-site, relocation assistance available. Also maybe mention that it's on-site with relocation assistance. We also have "Where And How You'd Work" describing headquarters, on-site, flexible schedules, workspace, zones. Some of that overlaps with schedule and location. But we can incorporate location details there. We need to avoid duplication. Let's craft About the role paragraph: "The role is on the CDP Platform Team at Ramsey Solutions headquarters in Franklin, TN (on-site). Relocation assistance is available." That's concise. Now Responsibilities: combine "What You'd Do In This Role" and "What Winning Looks Like". Let's extract responsibilities: From "What You'd Do In This Role": - Own the strategy and growth of our company-wide customer data platform, the operational backbone that helps product squads understand customers, spot high-leverage opportunities, and make faster, sharper decisions. - Run discovery rigorous enough to actually shape what gets built. - Translate what you learn into a roadmap that connects platform capabilities to real outcomes. - Partner closely with engineering to turn priorities into shipped work. - Spend as much time building trust and clarity across the building as you do building the roadmap itself. From "What Winning Looks Like": - Build and own a customer data platform strategy that product squads actually use to move faster and make sharper decisions. - Run a discovery rhythm rigorous enough to change direction, not just confirm it, and keep that evidence connected to what gets built. - Translate discovery findings into requirements engineering can act on, including sizing effort and knowing when to push back. - Lead cross-functional squads and stakeholders toward clear priorities without relying on formal authority. - Keep a steady communication rhythm so stakeholders always know what's needed, what's coming, and what shipped. - Raise risks and blockers early, with a plan attached, instead of absorbing them quietly. - Tie platform decisions back to measurable business and product impact, in dollars where possible. We can combine these into a bulleted list. Now Requirements (experience): bullet: "5+ years of product management experience (we're open to a background in engineering or another product-adjacent field, as long as you've recently worked in product management)". That's one bullet. Skills: bullet list of the abilities. Now Benefits: bullet list. Pay: paragraph with salary range and profit sharing. Schedule: paragraph about flexible schedules. Now we must ensure we don't include boilerplate like EOE etc. Remove. Now produce HTML fragment: use
for each section heading. Use
- for lists. Use
for prose. We must not include or . Just fragment. Let's order sections logically: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Check each has content. About the role: p with team and location. Responsibilities: ul with li items. Requirements: ul with li (one item). Skills: ul with li items. Benefits: ul with li items. Pay: p. Schedule: p. Now ensure we preserve all substantive information. Did we miss any? Let's review original text for any other details: - "Three decades later, Ramsey Solutions is a household name in personal finance, with a mission to change the toxic money culture for good." That's part of About Us; we omitted that. Could be included in About the role? Maybe we could add a sentence about mission in About the role? But About the role is about role, not company. However we could include
- for lists. Use