Sr. Product Manager (Remote Opportunity)

We need to output HTML fragment with sections: About the role? Actually we have "Who We Are", "What We Do", "What You'll Do", "What You'll Bring", "Preferred Experience", "What We Offer". The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content to these headings where appropriate. We must not repeat job title as heading. We should not include boilerplate like EEO etc. We need to preserve all substantive info. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to decide which sections to include: we have content about company (Who We Are) maybe "About the role"? Actually "Who We Are" is company overview, could be placed under "About the role"? But instructions say use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map: - About the role: could contain "Who We Are" and "What We Do"? Might be better to have separate sections: About the role (company overview and what the team does). Responsibilities: "What You'll Do". Requirements/Qualifications: "What You'll Bring" plus maybe "Preferred Experience". Skills: maybe combine with qualifications. Benefits: "What We Offer" includes benefits. Pay: we have pay range. Schedule: not mentioned, so we should not include Schedule section. We must not create sections with filler like "not specified". So only include sections where we have real content. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. But we need to avoid duplication. Could combine Requirements and Qualifications into one? The instruction says use headings for those categories; we can have both if we have content. We have "What You'll Bring" which includes both requirements and qualifications. Could split: Requirements (education, years experience) and Qualifications (specific skills). But we can also just have one section "Requirements" containing all. Safer to follow instruction: include sections only when posting has real specific content. We have content for Requirements (education, experience). We have content for Qualifications (specific abilities). We have content for Skills (maybe technical skills). We have Benefits. We have Pay. Thus we will output:

About the role

Who We Are ... What We Do ...

But we need to preserve all substantive info. Let's extract: Who We Are paragraph: "Join a team that puts its People First! As member of First American's family of companies, Mortgage Solutions provides lenders with solutions to originate, close and service quality loans. Since 1889, First American (NYSE: FAF) has held an unwavering belief in its people. They are passionate about what they do, and we are equally passionate about fostering an environment where all feel welcome, supported, and empowered to be innovative and reach their full potential. Our inclusive, people-first culture has earned our company numerous accolades, including being named to the Fortune 100 Best Companies to Work For® list for eleven consecutive years. We have also earned awards as a best place to work for women, diversity and LGBTQ+ employees, and have been included on more than 50 regional best places to work lists. First American will always strive to be a great place to work, for all. For more information, please visit www.careers.firstam.com." What We Do: "The Senior Product Manager defines, promotes, and communicates the strategic roadmap for valuation and appraisal technology products. This role leads product discovery, requirements, prioritization, and cross-functional execution for complex enterprise workflows spanning appraisal data standards, review and quality control, rules and automation, platform integrations, and legacy-to-modern product migration. The Senior Product Manager works closely with customers, Product, Engineering, QA, Support, Operations, Sales, and other stakeholders to translate business needs and market opportunities into scalable product capabilities and successful releases." We can combine these into About the role. Responsibilities: "What You'll Do" bullet list (actually sentences). We need to put each duty as

inside

. The content is a long paragraph with many sentences separated by periods. We should split into list items each representing a duty. Let's extract each bullet-like sentence: - Lead product strategy, roadmap development, and prioritization for valuation and appraisal technology products, balancing customer needs, regulatory obligations, platform dependencies, and business outcomes. - Own product discovery from problem definition through delivery, including stakeholder research, workflow analysis, market assessment, requirements development, release planning, adoption, and continuous improvement. - Translate complex appraisal and valuation workflows - including data collection, review, quality control, risk, delivery, and exception handling - into scalable product capabilities and clear requirements. - Define and prioritize capabilities supporting appraisal data standards and compliance, including UAD 3.6, UCDP/EAD, MISMO/XML structures, validation requirements, and applicable lender, investor, and GSE guidance. - Partner with Engineering, Architecture, BSA, and QA teams on products that rely on APIs, schemas, integrations, rules engines, shared platform services, and structured data; provide business clarity without requiring developer-level implementation expertise. - Lead product work involving business rules, automated review, findings, decisioning, AI-assisted workflows, and other capabilities that improve quality, consistency, speed, and operational efficiency. - Drive legacy-to-modern product migration decisions, including capability rationalization, gap identification, sequencing, customer transition considerations, and definition of what should migrate, change, or retire. - Manage dependencies across shared products and platform components, working with peer Product Managers and Engineering leaders to understand impacts, sequence work, and make transparent prioritization tradeoffs. - Work directly with lenders, servicers, investors, appraisal professionals, enterprise clients, and internal business partners to understand pain points, validate proposed solutions, and incorporate feedback into roadmap decisions. - Conduct competitive and market analysis across appraisal technology, valuation platforms, review solutions, AMCs, property data providers, and mortgage/fintech products to identify opportunities for differentiation and innovation. - Use product, operational, quality, support, and customer data to evaluate product health, measure outcomes, identify recurring issues, and guide continuous improvement. - Partner with Sales, Client Success, Support, Operations, and Marketing as a product subject-matter expert for customer discussions, demos, pilots, implementation planning, positioning, and launch readiness. - Communicate product direction, decisions, risks, dependencies, and progress clearly to executive and cross-functional stakeholders, and serve as a credible product advocate throughout the product lifecycle. That's many items. Requirements: "What You'll Bring" first part: Bachelor's degree or equivalent combination of education and directly related experience. 5+ years of directly related product management or product development experience, preferably in valuation, appraisal, mortgage technology, real estate data, lending technology, or another regulated workflow experience. Experience owning complex enterprise products or workflows from discovery and requirements through delivery, launch, and ongoing optimization. Experience partnering with Engineering and cross-functional teams in highly matrixed environments and influencing outcomes without direct authority. Strong product judgment and the ability to define strategy, establish priorities, make tradeoffs, and connect roadmap decisions to customer and business outcomes. Ability to quickly understand complex valuation, appraisal, review, compliance, and operational workflows and translate them into product opportunities and requirements. Comfort discussing APIs, XML/MISMO, schemas, rules engines, integrations, cloud platforms, data flows, and architecture dependencies with technical teams. Ability to distinguish customer needs and underlying problems from requested solutions, synthesize feedback, and make disciplined product decisions. Strong capability in problem statements, product requirements, user stories, acceptance criteria, workflow definition, MVP scoping, and release prioritization. Demonstrated ability to align Product, Engineering, QA, Support, Operations, Sales, and leadership around shared outcomes in a highly matrixed environment. Clear, concise communicator who can explain complex concepts, decisions, risks, and tradeoffs to technical, operational, customer, and executive audiences. Uses qualitative and quantitative data to assess product performance, understand root causes, evaluate alternatives, and measure outcomes. Forward-thinking and adaptable; able to manage near-term delivery needs while maintaining a coherent long-term product direction. Understands customer value, competitive positioning, financial considerations, adoption, operational impact, and resource constraints when making product decisions. Proven ability to drive complex initiatives through ambiguity, manage dependencies and risks, maintain stakeholder alignment, and follow through on commitments. Builds trust with customers, manages expectations effectively, solicits meaningful feedback, and balances individual requests against scalable product strategy. That's a lot; we can list as
• each sentence. Qualifications: maybe we treat "Preferred Experience" as Qualifications? Actually "Preferred Experience" is separate heading. We could treat that as Qualifications. The content: Direct experience in appraisal, valuation, appraisal management, collateral risk, or residential mortgage technology. Working knowledge of UAD 3.6, UCDP/EAD, MISMO, appraisal XML, or comparable industry data standards and validation frameworks. Experience with rules engines, compliance/review platforms, automated decisioning, workflow automation, or AI-enabled product capabilities. Experience modernizing or migrating legacy applications, forms, or workflows into cloud-based platforms. Experience with API-driven products, enterprise integrations, structured data, schemas or shared platform services. We can put these as
  under Qualifications. Skills: maybe we could extract from Requirements some skill statements, but we already have many. Could create Skills section for technical skills: comfort discussing APIs, XML/MISMO, etc. But we might duplicate. Better to not create Skills if content overlaps; but we can still have Skills with items like "Strong product judgment", "Ability to quickly understand complex workflows", etc. However we already have those in Requirements. To avoid duplication, we could skip Skills section and just have Requirements and Qualifications. The instruction says prefer a few substantive sections over many thin ones. So we can combine Requirements and Qualifications into one section? But they ask for headings like Requirements, Qualifications, Skills. We can have both if we have distinct content. We have Requirements (education, experience, core abilities). Qualifications (preferred experience). Skills maybe not needed. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Now Benefits: "What We Offer" paragraph: "By choice, we don’t simply accept individuality – we embrace it, we support it, and we thrive on it! Our People First culture is inclusive for all employees - not just because it's the right thing to do, but because it's the key to our success. We are proud to foster an authentic and inclusive workplace For All. You are free and encouraged to bring your entire, unique self to work. First American is an equal opportunity employer in every sense of the term. Based on eligibility, First American offers a comprehensive benefits package including medical, dental, vision, 401k, PTO/paid sick leave and other great benefits like an employee stock purchase plan." We need to remove EEO boilerplate: "First American is an equal opportunity employer in every sense of the term." That's EEO boilerplate; should be removed. Also maybe remove "Based on eligibility, First American offers a comprehensive benefits package including medical, dental, vision, 401k, PTO/paid sick leave and other great benefits like an employee stock purchase plan." Keep that. Also remove the earlier fluff about People First? That's substantive; keep. Thus Benefits section:

  Based on eligibility, First American offers a comprehensive benefits package including medical, dental, vision, 401k, PTO/paid sick leave and other great benefits like an employee stock purchase plan.

  plus maybe the preceding sentences about People First culture? Those are also substantive about culture; we can keep them as part of About the role? Actually they are about company culture, could be part of About the role. But we already have About the role with Who We Are and What We Do. Could add culture there. However we might keep Benefits separate focusing on benefits only. The instruction: include a section ONLY when posting has real, specific content for it. Benefits section we have specific benefits