Senior Product Manager, Data & AI Products
Realtor.com · Austin, TX · Yesterday
HybridMarketingFull-time
We need to output HTML fragment with sections for headings that have real content. Must not repeat job title. No Job ID. Must include sections only if posting has real specific content. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info.
We need to parse the posting and extract relevant sections.
Let's identify content:
First paragraph: description of company, mission. Could be "About the role"? Actually it's about company. Could be "About the role" or maybe not. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can decide which sections have content.
We have:
- About the role: description of what the role does, mission, etc. Could include paragraphs about Data & AI Products team, owning tools and marketplace, etc. That seems like role description.
- Responsibilities: bullet list of what you will do: "Set direction and own the roadmap", "Run intake and manage the request pipeline", "Know the users and the work", "Ship and deliver", "Measure and improve", "Work across teams", "Portfolio emphasis", "Native Data access". Those are responsibilities.
- Requirements / Qualifications: "What you will bring: Must-have" list: 8+ years product management experience, track record, experience running intake/backlog, strong data fluency, strong at discovery, able to define product metrics, excellent prioritization, experience writing clear requirements, clear communicator, high bar for product quality, Bachelor's degree or equivalent.
- Preferred: list of preferred qualifications.
- Skills: maybe combine must-have and preferred? But we have separate sections for Requirements and Qualifications. Could treat Must-have as Requirements, Preferred as Qualifications? Or Qualifications could be education etc. We'll decide.
- Benefits: list of benefits under "How We Reward You": Inclusive and Competitive medical, Rx, dental, vision coverage; Family forming benefits; 13 Paid Holidays; Flexible Time Off; 8 hours paid Volunteer Time off; Immediate eligibility into Company 401(k) plan with 3.5% company match; Tuition Reimbursement program; 1:1 personalized Financial Planning Sessions; Student Debt Retirement Savings Match program; Free snacks and refreshments.
- Pay: Not mentioned. No salary info. So we should NOT include Pay section.
- Schedule: Not mentioned. No schedule info. So omit.
We also have "How We Work": in-person collaboration 3+ days office. Could be part of Benefits? Not exactly. Could be under "About the role"? Might be considered as part of company culture. Could be omitted or included as a paragraph under About the role? The instruction: include a section ONLY when posting has real, specific content for it. The "How We Work" is specific content about work arrangement. Could be placed under a section like "About the role" or maybe a separate section like "Work Arrangement"? Not in allowed headings. So we could incorporate into About the role as prose.
Also "Diversity is important..." EEO boilerplate should be removed.
Also "Do the best work of your life at Realtor.com®" etc is marketing fluff but still substantive? Might be considered boilerplate but it's about culture. Could be included in About the role.
We need to preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep all details from the posting, except boilerplate like cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, and application instructions.
Thus we need to keep the "How We Work" and "How We Reward You" sections (benefits). Also keep the mission statements etc.
We must not repeat the job title as a heading. The job title is "Senior Product Manager". Not to be used as heading.
We must not put Job ID/requisition numbers as headings; none present.
We need to output only HTML fragment, no /, no markdown fences.
Thus produce something like:
About the role
... paragraphs ...
Responsibilities
- Set direction and own the roadmap...
...
Requirements
- Typically 8 or more years of product management experience...
...
Qualifications
- Bachelor's degree or equivalent experience.
Maybe also include Preferred as part of Qualifications? Could separate but we have only those headings. Could treat "Preferred" as part of Qualifications (or Skills). But we have Skills heading allowed. Could put preferred under Skills. However the instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use Skills for preferred qualifications.
Thus:
Skills
- Experience turning recurring reports...
...
Benefits: list.
We need to ensure we don't include filler like "commensurate with experience". Not present.
We need to remove duplicated lines. Check for duplicates: The posting repeats some sentences? Eg "You will own part of the data foundation..." appears later. We'll keep but ensure not duplicate.
Let's extract content precisely.
I'll copy the posting and manually extract.
Posting text:
"Recognized as the No. 1 site trusted by real estate professionals, Realtor.com® has been at the forefront of online real estate for over 25 years, connecting buyers, sellers, and renters with trusted insights and expert guidance to find their perfect home. Through its robust suite of tools, Realtor.com® not only makes a significant impact on the real estate industry at large, but for consumers, navigating the biggest purchase they will make in their life, by providing a user experience that is easy to use, easy to understand, and most of all, easy to make decisions.Join us on our mission to empower more people to find their way home by breaking barriers to entry, making the right connections, and building confidence through expert guidance. 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.What you will do:Set direction and own the roadmapOwn 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 pipelineOwn 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 workEngage 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 deliverTurn 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 improveDefine 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 teamsKeep 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.Portfolio emphasisData products and marketplaceYour primary focus. You build the tools and marketplace that let teams publish, find and reuse trusted data products, each with a clear owner, documentation and service-level expectations and you ready selected products for use outside the company. Success means trusted, widely used products and less duplicated work.Native Data accessYour closest partner area. You work with the team that makes data easy to query in plain language and through the team's AI tools, so the products we ship are easy to use for people and for those tools. Success means one reliable, shared way to get answers from the data.What you will bring:Must-haveTypically 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 can align multiple teams around a common goal without formal authority.A high bar for product quality, trust, operational readiness and attention to detail.Bachelor's degree or equivalent experience.PreferredExperience turning recurring reports or one-off data requests into reusable products or self-serve tools.Experience with data products, data platforms, APIs, or B2B data.Experience taking proprietary data or insights to external customers.Experience with a marketplace, data catalog, developer platform, or self-serve internal platform.Working SQL proficiency; Snowflake experience is a plus.Familiarity with data governance, including metadata, lineage, catalogs, stewardship, access management, or certification.Experience in real estate, proptech, marketplaces, or consumer internet.How success will be measuredSuccess in this role will be defined by the outcomes of the product area, including:Customer value: internal teams get trusted, self-
for prose. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info. We need to parse the posting and extract relevant sections. Let's identify content: First paragraph: description of company, mission. Could be "About the role"? Actually it's about company. Could be "About the role" or maybe not. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can decide which sections have content.
We have:
- About the role: description of what the role does, mission, etc. Could include paragraphs about Data & AI Products team, owning tools and marketplace, etc. That seems like role description.
- Responsibilities: bullet list of what you will do: "Set direction and own the roadmap", "Run intake and manage the request pipeline", "Know the users and the work", "Ship and deliver", "Measure and improve", "Work across teams", "Portfolio emphasis", "Native Data access". Those are responsibilities.
- Requirements / Qualifications: "What you will bring: Must-have" list: 8+ years product management experience, track record, experience running intake/backlog, strong data fluency, strong at discovery, able to define product metrics, excellent prioritization, experience writing clear requirements, clear communicator, high bar for product quality, Bachelor's degree or equivalent.
- Preferred: list of preferred qualifications.
- Skills: maybe combine must-have and preferred? But we have separate sections for Requirements and Qualifications. Could treat Must-have as Requirements, Preferred as Qualifications? Or Qualifications could be education etc. We'll decide.
- Benefits: list of benefits under "How We Reward You": Inclusive and Competitive medical, Rx, dental, vision coverage; Family forming benefits; 13 Paid Holidays; Flexible Time Off; 8 hours paid Volunteer Time off; Immediate eligibility into Company 401(k) plan with 3.5% company match; Tuition Reimbursement program; 1:1 personalized Financial Planning Sessions; Student Debt Retirement Savings Match program; Free snacks and refreshments.
- Pay: Not mentioned. No salary info. So we should NOT include Pay section.
- Schedule: Not mentioned. No schedule info. So omit.
We also have "How We Work": in-person collaboration 3+ days office. Could be part of Benefits? Not exactly. Could be under "About the role"? Might be considered as part of company culture. Could be omitted or included as a paragraph under About the role? The instruction: include a section ONLY when posting has real, specific content for it. The "How We Work" is specific content about work arrangement. Could be placed under a section like "About the role" or maybe a separate section like "Work Arrangement"? Not in allowed headings. So we could incorporate into About the role as prose.
Also "Diversity is important..." EEO boilerplate should be removed.
Also "Do the best work of your life at Realtor.com®" etc is marketing fluff but still substantive? Might be considered boilerplate but it's about culture. Could be included in About the role.
We need to preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep all details from the posting, except boilerplate like cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, and application instructions.
Thus we need to keep the "How We Work" and "How We Reward You" sections (benefits). Also keep the mission statements etc.
We must not repeat the job title as a heading. The job title is "Senior Product Manager". Not to be used as heading.
We must not put Job ID/requisition numbers as headings; none present.
We need to output only HTML fragment, no /, no markdown fences.
Thus produce something like:
About the role
... paragraphs ...
Responsibilities
- Set direction and own the roadmap... ...
Requirements
- Typically 8 or more years of product management experience... ...
Qualifications
- Bachelor's degree or equivalent experience.