Senior Product Manager, Data & AI Products
for each section heading. Use - for lists. Use
for prose.
We must not repeat job title. No Job ID. Remove boilerplate like EEO etc. Also remove navigation etc. Keep substantive info.
We need to capture:
- About the Role: paragraph(s) describing role.
- Responsibilities: bullet list from "What You’ll Do:" items.
- Requirements/Qualifications: bullet list from "What You'll Bring:" items (including typical experience, track record, etc). Also maybe "Preferred" items could be separate but we can include as part of qualifications or separate section? The instruction: include a section ONLY when posting has real, specific content for it. We have qualifications (required) and preferred. Could combine into one "Qualifications" section with both required and preferred bullet lists, but we need to differentiate? Could have two sub-sections? Not required. Simpler: one "Qualifications" section with bullet list of required and preferred combined? Might be okay but we lose distinction. Could have "Required Qualifications" and "Preferred Qualifications" as subheadings? But only allowed headings are those listed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "Qualifications" for required, and maybe "Skills" for preferred? But better to put all under "Qualifications". We'll include both required and preferred bullet points.
- Benefits: list from "How We Reward You:" bullet points.
We must not include sections like Pay or Schedule if not present.
We need to preserve all substantive info; not invent or summarize away detail. So we need to keep details like "Inclusive and Competitive medical, Rx, dental, and vision coverage", etc.
We need to remove boilerplate like "Diversity is important to us..." etc. Also remove "How We Work:" maybe not a heading; but it's substantive? It's about work arrangement (in-person). Could be considered part of benefits? Not exactly. It's about work arrangement; maybe we can include under "About the role"? Not appropriate. Could create a section "Work Arrangement"? Not allowed. Could drop it as it's not in allowed headings. The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't say we must include all possible headings; we can omit sections not matching allowed headings if content doesn't fit. The "How We Work:" is about in-person collaboration; could be considered part of benefits? Not exactly. Might be okay to omit as not under allowed headings. However, we might lose some substantive info. But maybe we can incorporate into "About the role" as a paragraph? It's about company culture; could be included there. But the "About the role" section already has description of role; we could add a sentence about work arrangement. That would preserve info.
Similarly "How success will be measured" could be part of responsibilities or qualifications? Could be under responsibilities as metrics. We'll incorporate.
We need to avoid duplication.
Let's extract sections:
About the Role: paragraphs from "About the Role:" up to before "What You’ll Do:"? Actually the posting includes:
"About the Role: At Realtor.com, we help people make confident decisions across the journey of buying, selling, renting and living in homes. Behind every one of those experiences is data, an enormous and constantly moving volume of it. Our Data & Analytics organization turns that raw signal into certified, trusted information that powers decisions across the company.The Data & AI Products team turns that data into reusable, well-documented products that teams across the company can find, trust and use and it powers the internal marketplace where those products live. This role owns a core part of that work: the tools and marketplace that make data products easy to publish, discover and reuse; the pipeline of internal product and enhancement requests; and readying selected products for use beyond the company.We are looking for a Senior Product Manager who gets things done. You take a steady stream of data needs and enhancement requests and turn them into a clear, prioritized roadmap and shipped products. You own a product area end to end, from deciding what to build to getting it live, adopted and supported.You work closely with engineering, analytics, data governance, privacy and legal and the business teams that use the data. You lead through influence rather than formal authority, keep many stakeholders aligned and keep delivery moving.You are comfortable moving between planning and detail: framing the problem, setting the next quarter's priorities, writing clear requirements, reviewing a build with an engineer, checking adoption and making the call when the path is unclear."
That's the About the Role.
Then "What You’ll Do:" list.
Then "What You'll Bring:" list (required and preferred).
Then "How success will be measured:" list.
Then "Why join RDC:" paragraph.
Then "How We Work:" paragraph.
Then "How We Reward You:" benefits list.
Then "Do the best work of your life at Realtor.com®" paragraph.
Then diversity statement etc (boilerplate) to remove.
We need to include all substantive info.
We'll create sections:
About the role
... (the About the Role paragraph(s) )
Responsibilities
- ... each bullet from What You’ll Do
Qualifications
- ... each bullet from What You'll Bring (required and preferred)
Maybe also a section for "Success metrics" but not in allowed headings. Could incorporate into Responsibilities as bullet about measuring and improving? Actually responsibilities already include "Measure and improve" bullet. So we can keep that.
We also have "Why join RDC:" paragraph; could be part of About the role? Or maybe we can add a section "About the company"? Not allowed. Could incorporate into About the role as additional paragraph.
Similarly "How We Work:" could be added to About the role or Benefits? Might be okay to add a short paragraph under About the role about work arrangement.
We'll keep Benefits section.
Thus final HTML:
About the role
At Realtor.com, we help people make confident decisions across the journey of buying, selling, renting and living in homes. Behind every one of those experiences is data, an enormous and constantly moving volume of it. Our Data & Analytics organization turns that raw signal into certified, trusted information that powers decisions across the company. The Data & AI Products team turns that data into reusable, well-documented products that teams across the company can find, trust and use and it powers the internal marketplace where those products live. This role owns a core part of that work: the tools and marketplace that make data products easy to publish, discover and reuse; the pipeline of internal product and enhancement requests; and readying selected products for use beyond the company. We are looking for a Senior Product Manager who gets things done. You take a steady stream of data needs and enhancement requests and turn them into a clear, prioritized roadmap and shipped products. You own a product area end to end, from deciding what to build to getting it live, adopted and supported. You work closely with engineering, analytics, data governance, privacy and legal and the business teams that use the data. You lead through influence rather than formal authority, keep many stakeholders aligned and keep delivery moving. You are comfortable moving between planning and detail: framing the problem, setting the next quarter's priorities, writing clear requirements, reviewing a build with an engineer, checking adoption and making the call when the path is unclear. Our employees work four or more days in our offices, where they have the opportunity to collaborate in-person, adding richness to our culture and knitting us closer together. You will own part of the data foundation Realtor.com runs on and turn it into products people trust and rely on. You will work in a hands-on, outcome-driven team where product, engineering, analytics and governance build and ship together. Here, you’ll partner with a diverse team of experts as you use leading-edge tech to empower everyone to meet a crucial goal: finding their way home. And you’ll find your way home too. At Realtor.com®, you’ll bring your full self to work as you innovate with speed, serve our consumers, and champion your teammates. In return, we’ll provide you with a warm, welcoming, and inclusive culture; intellectual challenges; and the development opportunities you need to grow.
Responsibilities
- Set direction and own the roadmap: own the roadmap for your product area and keep it current as priorities change.
- Turn company and data-team goals into a concrete, prioritized plan of products to build and improve.
- Decide what to build, what to defer and what to stop and make those calls clearly.
- Find ways to make data easier to find and reuse and cut duplicated, one‑off work.
- Run intake and manage the request pipeline: own intake for internal product and enhancement requests; capture, triage and prioritize them into the roadmap; keep a single, visible backlog so the team and stakeholders know what is coming and why; keep stakeholders informed on status, decisions and timelines and push back when an ask is not worth it.
- Know the users and the work: engage internal teams who use the data (analysts, product managers, engineers, business teams) and where relevant, external customers, to understand what they need and where they get stuck; use usage data and direct feedback to decide what to build and to confirm it worked; make sure the team solves the underlying need, not just the specific table or report someone asked for.
- Ship and deliver: turn ambiguous asks into clear briefs, requirements and acceptance criteria engineers can build from; partner with engineering to ship in small, value‑adding increments; take products through build, certification, launch and ongoing support; set up documentation, ownership, adoption and service‑level expectations for each product; remove blockers and keep partners aligned on decisions, dependencies and risks.
- Measure and improve: define the few metrics that show whether a product is used, trusted and valuable, such as adoption, time‑to‑answer, quality and revenue where relevant; watch those metrics and act on them: scale what works, fix or stop what does not; hold the team to outcomes, not activity or feature count.
- Work across teams: keep engineering, analytics, governance, privacy and business partners aligned on shared goals; build trust with senior stakeholders and communicate progress, trade‑offs and decisions plainly; represent your area in planning and portfolio reviews; support other product managers and help improve how the team works.
Qualifications
- Typically 8 or more years of product management experience in technology, marketplace, data, platform, SaaS, or a related environment; equivalent experience will be considered.
- A track record of owning a product area and shipping outcomes that people actually used.
- Experience running an intake and backlog: taking many competing requests and turning them into a prioritized plan people can see.
- Strong data and analytics fluency: you understand how data is produced, managed, served and consumed and why clear definitions, ownership, quality and trust matter; you can discuss pipelines, data models and data quality with technical and non‑technical audiences.
- Strong at discovery: talking to users, reading usage data and turning both into decisions.
- Able to define product metrics, use data to make decisions and make the case for what to fund.
- Excellent prioritization and problem‑solving in ambiguous, fast‑changing situations.
- Experience writing clear requirements and working closely with engineering through delivery.
- Clear communicator who
for prose. We must not repeat job title. No Job ID. Remove boilerplate like EEO etc. Also remove navigation etc. Keep substantive info. We need to capture: - About the Role: paragraph(s) describing role. - Responsibilities: bullet list from "What You’ll Do:" items. - Requirements/Qualifications: bullet list from "What You'll Bring:" items (including typical experience, track record, etc). Also maybe "Preferred" items could be separate but we can include as part of qualifications or separate section? The instruction: include a section ONLY when posting has real, specific content for it. We have qualifications (required) and preferred. Could combine into one "Qualifications" section with both required and preferred bullet lists, but we need to differentiate? Could have two sub-sections? Not required. Simpler: one "Qualifications" section with bullet list of required and preferred combined? Might be okay but we lose distinction. Could have "Required Qualifications" and "Preferred Qualifications" as subheadings? But only allowed headings are those listed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "Qualifications" for required, and maybe "Skills" for preferred? But better to put all under "Qualifications". We'll include both required and preferred bullet points. - Benefits: list from "How We Reward You:" bullet points. We must not include sections like Pay or Schedule if not present. We need to preserve all substantive info; not invent or summarize away detail. So we need to keep details like "Inclusive and Competitive medical, Rx, dental, and vision coverage", etc. We need to remove boilerplate like "Diversity is important to us..." etc. Also remove "How We Work:" maybe not a heading; but it's substantive? It's about work arrangement (in-person). Could be considered part of benefits? Not exactly. It's about work arrangement; maybe we can include under "About the role"? Not appropriate. Could create a section "Work Arrangement"? Not allowed. Could drop it as it's not in allowed headings. The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't say we must include all possible headings; we can omit sections not matching allowed headings if content doesn't fit. The "How We Work:" is about in-person collaboration; could be considered part of benefits? Not exactly. Might be okay to omit as not under allowed headings. However, we might lose some substantive info. But maybe we can incorporate into "About the role" as a paragraph? It's about company culture; could be included there. But the "About the role" section already has description of role; we could add a sentence about work arrangement. That would preserve info. Similarly "How success will be measured" could be part of responsibilities or qualifications? Could be under responsibilities as metrics. We'll incorporate. We need to avoid duplication. Let's extract sections: About the Role: paragraphs from "About the Role:" up to before "What You’ll Do:"? Actually the posting includes: "About the Role: At Realtor.com, we help people make confident decisions across the journey of buying, selling, renting and living in homes. Behind every one of those experiences is data, an enormous and constantly moving volume of it. Our Data & Analytics organization turns that raw signal into certified, trusted information that powers decisions across the company.The Data & AI Products team turns that data into reusable, well-documented products that teams across the company can find, trust and use and it powers the internal marketplace where those products live. This role owns a core part of that work: the tools and marketplace that make data products easy to publish, discover and reuse; the pipeline of internal product and enhancement requests; and readying selected products for use beyond the company.We are looking for a Senior Product Manager who gets things done. You take a steady stream of data needs and enhancement requests and turn them into a clear, prioritized roadmap and shipped products. You own a product area end to end, from deciding what to build to getting it live, adopted and supported.You work closely with engineering, analytics, data governance, privacy and legal and the business teams that use the data. You lead through influence rather than formal authority, keep many stakeholders aligned and keep delivery moving.You are comfortable moving between planning and detail: framing the problem, setting the next quarter's priorities, writing clear requirements, reviewing a build with an engineer, checking adoption and making the call when the path is unclear." That's the About the Role. Then "What You’ll Do:" list. Then "What You'll Bring:" list (required and preferred). Then "How success will be measured:" list. Then "Why join RDC:" paragraph. Then "How We Work:" paragraph. Then "How We Reward You:" benefits list. Then "Do the best work of your life at Realtor.com®" paragraph. Then diversity statement etc (boilerplate) to remove. We need to include all substantive info. We'll create sections:
About the role
... (the About the Role paragraph(s) )
Responsibilities
- ... each bullet from What You’ll Do
Qualifications
- ... each bullet from What You'll Bring (required and preferred)
About the role
At Realtor.com, we help people make confident decisions across the journey of buying, selling, renting and living in homes. Behind every one of those experiences is data, an enormous and constantly moving volume of it. Our Data & Analytics organization turns that raw signal into certified, trusted information that powers decisions across the company. The Data & AI Products team turns that data into reusable, well-documented products that teams across the company can find, trust and use and it powers the internal marketplace where those products live. This role owns a core part of that work: the tools and marketplace that make data products easy to publish, discover and reuse; the pipeline of internal product and enhancement requests; and readying selected products for use beyond the company. We are looking for a Senior Product Manager who gets things done. You take a steady stream of data needs and enhancement requests and turn them into a clear, prioritized roadmap and shipped products. You own a product area end to end, from deciding what to build to getting it live, adopted and supported. You work closely with engineering, analytics, data governance, privacy and legal and the business teams that use the data. You lead through influence rather than formal authority, keep many stakeholders aligned and keep delivery moving. You are comfortable moving between planning and detail: framing the problem, setting the next quarter's priorities, writing clear requirements, reviewing a build with an engineer, checking adoption and making the call when the path is unclear. Our employees work four or more days in our offices, where they have the opportunity to collaborate in-person, adding richness to our culture and knitting us closer together. You will own part of the data foundation Realtor.com runs on and turn it into products people trust and rely on. You will work in a hands-on, outcome-driven team where product, engineering, analytics and governance build and ship together. Here, you’ll partner with a diverse team of experts as you use leading-edge tech to empower everyone to meet a crucial goal: finding their way home. And you’ll find your way home too. At Realtor.com®, you’ll bring your full self to work as you innovate with speed, serve our consumers, and champion your teammates. In return, we’ll provide you with a warm, welcoming, and inclusive culture; intellectual challenges; and the development opportunities you need to grow.
Responsibilities
- Set direction and own the roadmap: own the roadmap for your product area and keep it current as priorities change.
- Turn company and data-team goals into a concrete, prioritized plan of products to build and improve.
- Decide what to build, what to defer and what to stop and make those calls clearly.
- Find ways to make data easier to find and reuse and cut duplicated, one‑off work.
- Run intake and manage the request pipeline: own intake for internal product and enhancement requests; capture, triage and prioritize them into the roadmap; keep a single, visible backlog so the team and stakeholders know what is coming and why; keep stakeholders informed on status, decisions and timelines and push back when an ask is not worth it.
- Know the users and the work: engage internal teams who use the data (analysts, product managers, engineers, business teams) and where relevant, external customers, to understand what they need and where they get stuck; use usage data and direct feedback to decide what to build and to confirm it worked; make sure the team solves the underlying need, not just the specific table or report someone asked for.
- Ship and deliver: turn ambiguous asks into clear briefs, requirements and acceptance criteria engineers can build from; partner with engineering to ship in small, value‑adding increments; take products through build, certification, launch and ongoing support; set up documentation, ownership, adoption and service‑level expectations for each product; remove blockers and keep partners aligned on decisions, dependencies and risks.
- Measure and improve: define the few metrics that show whether a product is used, trusted and valuable, such as adoption, time‑to‑answer, quality and revenue where relevant; watch those metrics and act on them: scale what works, fix or stop what does not; hold the team to outcomes, not activity or feature count.
- Work across teams: keep engineering, analytics, governance, privacy and business partners aligned on shared goals; build trust with senior stakeholders and communicate progress, trade‑offs and decisions plainly; represent your area in planning and portfolio reviews; support other product managers and help improve how the team works.
Qualifications
- Typically 8 or more years of product management experience in technology, marketplace, data, platform, SaaS, or a related environment; equivalent experience will be considered.
- A track record of owning a product area and shipping outcomes that people actually used.
- Experience running an intake and backlog: taking many competing requests and turning them into a prioritized plan people can see.
- Strong data and analytics fluency: you understand how data is produced, managed, served and consumed and why clear definitions, ownership, quality and trust matter; you can discuss pipelines, data models and data quality with technical and non‑technical audiences.
- Strong at discovery: talking to users, reading usage data and turning both into decisions.
- Able to define product metrics, use data to make decisions and make the case for what to fund.
- Excellent prioritization and problem‑solving in ambiguous, fast‑changing situations.
- Experience writing clear requirements and working closely with engineering through delivery.
- Clear communicator who