Sr. Enterprise Systems Technical Business Analyst
Realtor.com · Austin, TX · 1 mo ago
HybridBusiness DevelopmentFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the job posting.
First, there is introductory paragraph about Realtor.com. That's likely "About the role" or maybe "About the company". The instruction: use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the job posting.
First, there is introductory paragraph about Realtor.com. That's likely "About the role" or maybe "About the company". The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide appropriate headings based on content.
We have:
- Intro: "Recognized as the No. 1 site trusted by real estate professionals..." This is about the company and mission. Could be "About the role" or "About the company". Since they said "About the role" is an example, we can use that for a summary of the role and company.
- Then: "We are seeking a Sr. Enterprise Systems Technical Business Analyst to support key initiatives across our enterprise applications, with a primary focus on Salesforce and customer-facing business systems. This role partners closely with Sales, Customer Success, Revenue Operations and Engineering to deliver scalable technology solutions that improve operational efficiency and enhance the customer experience."
- Then: "Join us as our newest Sr. Enterprise Systems Technical Business Analyst and continue to Love Your Career at Realtor.com®. As part of the Realtor.com® BSA team, you will join a diverse group of analytically minded individuals committed to the success of our partners across the company—supporting key business groups including Sales, Success, Customer Care, and Finance,.We are a team that sees problems from end to end, skillfully translating business challenges into elegant technical solutions. We evaluate opportunities using data and observation, guide technical teams with detailed requirements, and support QA and users through delivery. If your mission aligns with ours—to help business partners achieve their goals while providing the highest quality products and services to our customers—we'd love to talk to you."
- Then: "The ideal candidate is comfortable gathering detailed business requirements, supporting roadmap discussions, and partnering with technical teams to deliver system enhancements. You will need solid Salesforce expertise, strong written and verbal communication abilities, and experience collaborating with both technical and non-technical business partners."
- Then "What You'll Do:" with bullet list items (Product Strategy Support, Business Analysis, End-to-End Delivery Support, Salesforce Support, AI & Emerging Technologies, Project & Stakeholder Coordination). Those are responsibilities.
- Then "How We Work:" paragraph about in-person collaboration.
- Then "What You Bring:" list of qualifications: Bachelor's degree, 5+ years experience, etc.
- Then "Preferred:" list of certifications.
- Then "How We Reward You:" benefits list.
- Then "Do the best work of your life at Realtor.com®" paragraph about culture.
- Then EEO boilerplate (should be removed).
We need to remove cookie/navigation/legal/EEO etc. So we drop the final EEO paragraph.
We need to include sections only when there is real specific content.
Potential sections:
- About the role (intro + mission). Could combine intro paragraphs.
- Responsibilities (What You'll Do)
- Requirements / Qualifications (What You Bring) maybe separate Requirements and Qualifications? The instruction list includes both Requirements and Qualifications as possible headings. We could put "Requirements" for mandatory qualifications, and "Qualifications" for preferred? Or combine. But we need to avoid thin sections. Perhaps we can have "Requirements" for the mandatory qualifications (Bachelor's degree, 5+ years experience, etc.) and "Preferred Qualifications" maybe not needed. But we have a "Preferred:" list. Could treat as "Qualifications" (including both required and preferred). However we need to follow instruction: Use headings only when posting has real specific content. We have content for both required and preferred. Could make two sections: "Requirements" and "Preferred Qualifications". But they said headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So "Qualifications" is a heading. Could put all qualifications under "Qualifications". But then we lose distinction between required and preferred. However we can still include both under same heading.
Alternatively we could have "Requirements" for mandatory, and "Skills" for skills/expertise. But we have skills mentioned in responsibilities and qualifications.
Better to follow typical pattern: About the role, Responsibilities, Requirements, Qualifications, Benefits. Since we have no explicit Pay or Schedule, we omit those.
We also have "How We Work:" about in-person collaboration. Could be part of About the role or maybe a separate section like "Work Environment". Not in allowed headings list. Could omit or incorporate into About the role.
We need to preserve all substantive information; not invent or summarize away detail. So we need to keep the details.
Thus we need to produce HTML with sections:
About the role
About the role
... (intro paragraphs)
Responsibilities
- ... each bullet
Requirements
... maybe combine mandatory qualifications into paragraph(s) or list? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So if we have a list of requirements, we should use
- . The "What You Bring:" includes bullet-like sentences (though not formatted as bullet list originally). We can convert to list.
Similarly "Preferred:" list can be another list under maybe "Preferred Qualifications" but not in allowed headings. Could put under "Qualifications" as list as well, but we need to differentiate? Could combine both required and preferred into one list but that loses distinction. However we could have two sections: "Requirements" (mandatory) and "Qualifications" (preferred). That fits allowed headings.
Thus:
Requirements
- Bachelor's degree or equivalent experience
- 5+ years of experience as a Technical Business Analyst, Enterprise Systems Analyst, Business Systems Analyst, or Program Coordinator with experience implementing and enhancing Salesforce solutions, with experience in Sales Cloud and Service Cloud.
- Experience supporting cross-functional projects from discovery through implementation, including business process analysis, requirements gathering, and solution design.
- Strong skills writing business requirements, functional specifications, user stories, process documentation, and stakeholder presentations.
- Experience with, or strong interest in, implementing AI-enabled business solutions (e.g., Salesforce Agentforce, Claude, Gemini, OpenAI, or Microsoft Copilot).
- Familiarity with Salesforce Data Cloud, Flow, APIs, and enterprise integrations alongside knowledge of CRM, Customer Support, Revenue Operations, CPQ, and SaaS business processes.
- Strong communication, facilitation, and stakeholder management skills; a "We, Not Me" collaborative attitude.
Qualifications
- Preferred: Salesforce certifications (Administrator, Business Analyst, Advanced Administrator, AI Associate, or Agentforce Specialist) and Agile/Scrum certifications.
- for each benefit. Benefits list: - Inclusive and Competitive medical, Rx, dental, and vision coverage - Family forming benefits - 13 Paid Holidays - Flexible Time Off - 8 hours of paid Volunteer Time off - Immediate eligibility into Company 401(k) plan with 3.5% company match - Tuition Reimbursement program for degreed and non-degreed programs - 1:1 personalized Financial Planning Sessions - Student Debt Retirement Savings Match program - Free snacks and refreshments in each office location We should keep each as separate
- .
Now "How We Work:" paragraph about in-person collaboration. Could be part of About the role or maybe a separate section like "Work Environment". Not in allowed headings but we could incorporate into About the role.
Also there is a paragraph after benefits: "Do the best work of your life at Realtor.com®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."
That's more about culture; could be part of About the role or maybe a separate section like "Culture". Not in allowed headings; we could incorporate into About the role.
Thus About the role will include the introductory paragraphs, the "How We Work:" paragraph, and the culture paragraph.
We need to ensure we don't repeat the job title as a heading. We are not.
We must not include Job ID/requisition numbers.
We must remove boilerplate: EEO paragraph at end removed.
Now produce HTML fragment.
We need to ensure proper nesting: each section heading
followed by either
or
- ...
- . The "What You Bring:" includes bullet-like sentences (though not formatted as bullet list originally). We can convert to list.
Similarly "Preferred:" list can be another list under maybe "Preferred Qualifications" but not in allowed headings. Could put under "Qualifications" as list as well, but we need to differentiate? Could combine both required and preferred into one list but that loses distinction. However we could have two sections: "Requirements" (mandatory) and "Qualifications" (preferred). That fits allowed headings.
Thus: