Software Appl Developer
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate, navigation, EEO, legal, etc. Must preserve all substantive info.
We need to parse the description.
Let's extract sections:
- About the Role: after "About the Role:" there is a paragraph: "The Salesforce Developer will be responsible for implementation, delivering and supporting application lifecycle projects utilizing commercial, free and custom-developed software by partnering with Sales, Marketing, Service, Technology and BI stakeholders. You will actively participate in the multi-year implementation and expansion of the SFDC platforms at http://move.com . Top Reasons to Apply: ..."
But "Top Reasons to Apply:" might be part of About the Role? It lists reasons: Ground floor build, High-Visibility Innovation with Agentforce, Direct Bridge Between Code and Business Strategy. Those are bullet points? They are sentences. Could be considered part of About the Role or maybe separate? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We have "What You'll Do:" which is responsibilities.
We have "What You'll Bring:" which includes qualifications, requirements, skills.
We have "How We Work:" and "How We Reward You:" which includes benefits.
We have no explicit Pay or Schedule info. There's mention of "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". Also "13 Paid Holidays", "Flexible Time Off", "8 hours of paid Volunteer Time off". Those are benefits. No explicit pay or schedule. So we should not create Pay or Schedule sections because no specific content.
We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Possibly also "How We Work" could be part of Benefits? But it's about work arrangement (in-person collaboration). Could be considered part of Benefits? Might be better as a separate section like "Work Environment" but not in allowed headings. Since only allowed headings are those listed, we should map content to those headings. "How We Work" could be considered part of Benefits? Not really. But we could include it under Benefits? Or we could omit because not matching allowed headings? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, but we should prefer those headings. It also says "include a section ONLY when the posting has real, specific content for it". So we can create sections for any of those headings if content exists. If content doesn't match exactly, we could still use those headings if appropriate. For "How We Work", maybe we could put under Benefits? Not ideal. Could we create a section "About the role" includes the initial description and top reasons. Then "Responsibilities" from "What You'll Do:". Then "Requirements" maybe from "What You'll Bring:" includes degree, years experience, certifications. Then "Skills" could be technical skills: Agentforce, Apex, LWC, etc. Then "Qualifications" maybe overlapping; but we need to avoid duplication. Could combine Requirements and Qualifications? But we need to follow instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But we have separate headings allowed; we could choose to include both if they have distinct content. Let's see.
"What You'll Bring:" includes:
- Bachelor’s or Master’s degree in mathematics, computer science or related field
- 3-6 years of hands on experience in SFDC development, lead role in supporting Sales/Marketing and Service modules
- Salesforce Platform Developer I ,Certified Platform Developer II, Agentforce Certifications preferred.
- Experience on building Agentforce Agent and bot experience required.
- Hands on design and development of custom solutions on the force.com platform including significant work in Agentforce, Apex Triggers, Apex Classes, LWC, Visualforce, lightning platform, SOQL queries, components and application integration patterns
- Experience in integrating SFDC with Cloud and On-premise applications such as Big Machines, Docusign, AWS and SOA etc
- Hands on experience on Javascript, Bootstrap, Jquery etc
- Must have development experience with http://Salesforce.com including lead management, opportunity management and Sales management
- Experience developing reports and dashboards in http://Salesforce.com
- Must be comfortable analyzing data, identifying trends and correcting data quality issues
- Strong and effective written, verbal and presentation skills with the ability to collaborate with team members and business stakeholders at all levels of the organization
- Must be comfortable with juggling multiple priorities with the ability to manage time effectively
- Excellent problem-solving, analytical and investigative skills
That covers qualifications, requirements, skills. Could split: Requirements (education, years experience, certifications) and Skills (technical skills, soft skills). Qualifications maybe similar to requirements. But we can decide to have Requirements and Skills sections, and maybe omit Qualifications to avoid thin sections.
Benefits: from "How We Reward You:" includes 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.
Also "How We Work:" mentions in-person collaboration 4+ days office. Could be considered part of Benefits? Not exactly benefits but work arrangement. Could be a separate section but not in allowed headings. Could we add a section "About the role" includes that? Probably not. Could we create a section "Benefits" and include work arrangement as part of benefits? Might be okay.
Pay: none.
Schedule: none.
Thus output sections: About the role, Responsibilities, Requirements, Skills, Benefits.
We need to use for each heading, then content:
for each heading, then content:
for prose,
- for lists.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting.
We need to avoid boilerplate: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes EEO statement at end: "Diversity is important to us, therefore, Realtor.com® is an Equal Opportunity Employer...". Must remove that.
Also remove "Here, you’ll partner..." etc? That is promotional but maybe substantive? It's about culture; could be considered part of About the role? Might be considered boilerplate? It's not navigation/legal; it's about culture. Might be okay to keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The culture paragraph is not those. Could keep as part of About the role? But we already have About the role content; we could add that as a paragraph.
But we need to avoid duplication: The posting includes "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." That's earlier. Also later: "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 also culture. Might be okay to keep as part of About the role or maybe a separate section? Not in allowed headings. Could incorporate into About the role.
We must not repeat job title as heading. The job title is Salesforce Developer (implied). Not used.
Now craft HTML.
Structure:
About the role
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. The Salesforce Developer will be responsible for implementation, delivering and supporting application lifecycle projects utilizing commercial, free and custom-developed software by partnering with Sales, Marketing, Service, Technology and BI stakeholders. You will actively participate in the multi-year implementation and expansion of the SFDC platforms at http://move.com. Top reasons to apply: ground floor build – you aren't just fixing someone else's old code; you are joining the Commercialization Team to build a new RDC products sales/customer care experience on Salesforce. If you love to build the process for new product sales/customer care and want to own the codebase from day one, this is it. High-visibility innovation with Agentforce – this role puts you at the cutting edge of Salesforce’s latest technology. You will lead the charge in building Agentforce Agents and bot experiences, moving beyond standard configuration into the future of AI-driven automation. Because this project is high-visibility, your work on these innovative solutions will be seen directly by cross-functional stakeholders and executive leadership. Direct bridge between code and business strategy – forget working in a silo. This position offers a unique "seat at the table" where you will partner directly with BSAs, Products, Sales, Marketing, and customer care stakeholders to translate business vision into technical reality.
But we need to keep bullet points? The "Top Reasons to Apply:" lines are separate sentences; we could keep as- . Better to use list.
Thus:
About the role
- Ground floor build: You aren't just fixing someone else's old code. You are joining the Commercialization Team to build a new RDC products sales/customer care experience on Salesforce. If you love to build the process for new product sales/customer care and want to own the codebase from day one, this is it.
- High-Visibility Innovation with Agentforce: This role puts you at the cutting edge of Salesforce’s latest technology. You will be lead the charge in building Agentforce Agents and bot experiences, moving beyond standard configuration into the future of AI-driven automation. Because this project is high-visibility, your work on these innovative solutions will be seen directly by cross-functional stakeholders and executive leadership.
- Direct Bridge Between Code and Business Strategy: Forget working in a silo. This position offers a unique "seat at the table" where you will partner directly with BSAs, Products, Sales, Marketing, and customer care stakeholders to translate business vision into technical reality
before the list. Thus:
About the role
Recognized as the No. 1 site trusted by real estate professionals, Realtor.com
- . Better to use list.
Thus: