Software Engineer, Mobile
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. No Job ID etc. Remove boilerplate. We need to parse the description. Content: - Intro paragraph about Realtor.com (maybe not needed as heading? It's description but not under a heading. Could be placed as
before sections? The instruction: Use
for section headings (e.g. About the role, Responsibilities...). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
Thus we need to keep substantive info: About the Role paragraph, What You'll Do (responsibilities), What You'll Bring (requirements/qualifications/skills), How We Work (maybe schedule? but not explicit), How We Reward You (benefits). Also maybe "Do the best work of your life at Realtor.com®" etc is fluff but could be kept as prose? It's not boilerplate; it's motivational but maybe keep as part of description? The instruction: remove duplicated lines, but not remove motivational content unless it's boilerplate. It's not boilerplate but could be considered fluff. However we need to preserve ALL substantive information. That includes that paragraph? It's somewhat generic but still part of posting. I'd keep it as a
under maybe no heading? But we could put it under a heading like "About the Role" already covers that. Actually "About the Role:" heading is present in the posting. So we should create
About the role
and include the paragraph(s) under it.
Then "What You'll Do:" corresponds to Responsibilities. So Responsibilities
with list.
Then "What You'll Bring:" corresponds to Requirements/Qualifications/Skills. Could split into Requirements (education, experience) and Skills (technologies). But we can combine into one section maybe "Requirements". However instruction: Prefer a few substantive sections over many thin ones. So we could have one section for Requirements/Qualifications/Skills combined. But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include. We have content for About the role, Responsibilities, Requirements (education, experience), Qualifications (maybe same), Skills (specific tech), Benefits (How We Reward You). Pay and Schedule not present (no explicit pay or schedule). So we omit Pay and Schedule sections.
We could also include "How We Work" as maybe Schedule? But it's about in-person collaboration days, not schedule. Could be considered Schedule? It says "For most roles, our employees work four or more days in our offices". That's schedule info. Could be placed under Schedule heading. But the instruction: only include a section when posting has real, specific content for it. This is specific: four or more days in office. So we could create a Schedule section with that info. However we also have How We Work paragraph about in-person collaboration. That could be considered Schedule or maybe a separate section like "Work Environment". But we only have allowed headings list; we could put it under Schedule. That seems appropriate.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule. Possibly Qualifications separate? But we can combine Requirements and Qualifications into one section? The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one Requirements
(or Qualifications). But we need to decide which heading to use. Since we have both headings allowed, we could use Requirements for education/experience, and Qualifications for maybe "Bachelor’s degree..." etc. But they overlap. Better to have one section called Requirements (or Qualifications) that includes education, experience, technical skills. Then Skills could be separate for specific technologies? But that would be thin. Let's combine education, experience, and technical skills into Requirements. Then we could have Skills maybe empty; better not to include Skills if no distinct content beyond what's already in Requirements. So we omit Skills.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule.
Now extract content.
About the role: The paragraph after "About the Role:" includes two sentences: "Are you passionate about building software solutions to solve real customer problems? Do you like fast-paced work environments? Are you excited about modern programming languages, design patterns, and scalable architectures? You’ll be right at home here!" Then following paragraph: "You will be joining the Client Mobile tech team. At Realtor, our technology team participates in the research and development of scalable applications, identifying new technologies and trends to enhance our products and business. We build innovative solutions to help customers in their buying, renting, and selling journeys by connecting them with real estate agents and partners. Join us to push the boundaries of what’s possible and learn from world-class talent that promotes a culture of experimentation and learning." Then next paragraph: "A Software Engineer at Realtor.com is an impactful contributor to our engineering team. You solve difficult problems, applying technologies with engineering best practices. You work with your team to design and build software that solves consumer and customer problems. You write stable code that a software engineer unfamiliar with the system can understand. You write stable code that a software engineer unfamiliar with the system can understand. You make appropriate trade-offs and re-use where possible. You work on project ideas with Product Management and engage with customers, stakeholders, and peers. You help the team by actively participating in the code review process, design discussions, and team planning."
Note duplicate sentence about writing stable code appears twice; we should preserve but not duplicate? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we need to remove duplicated lines. The duplicate line is exactly same sentence appears twice. We should keep only one instance.
Thus About the role content: combine paragraphs, removing duplicate line.
Now Responsibilities: Under "What You'll Do:" bullet list (though not bullet in text). It's a series of sentences each starting with a verb. We should make - for each duty.
List:
- Develop high quality, scalable, and reliable solutions
- Work collaboratively in a squad composed of Product Managers, Designers, Analysts and Engineers.
- Help mentor and pair with peers on your team
- Investigate and prototype technologies that can be leveraged to introduce new innovations
- Be self-directed, take initiative and drive towards solutions with little guidance
- Participate in team meetings, providing opinions and insight that helps clarify requirements and technical challenges.
Now Requirements: Under "What You'll Bring:" list.
We need to extract each bullet:
- Bachelor’s degree in Computer Science or equivalent experience
- 2-3 years experience in software development
- Experience in mobile application development using React Native; familiarity with Expo is a plus
- Familiarity with GraphQL and Python
- Experience working with Postgres; AWS knowledge is preferred
- Strong understanding of system design and trade offs between design approaches
- Experience delivering high value features to customers quickly and iterating based on feedback
- Strong software engineering best practices, including testing, code reviews, and CI/CD pipelines
- Hands on experience in releasing, maintaining, and supporting mobile applications in production
We could keep as list.
Now Benefits: Under "How We Reward You:" 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
Now Schedule: Under "How We Work:" paragraph: "We balance creativity and innovation on a foundation of in-person collaboration. For most roles, 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."
We could make that as a
under Schedule heading.
Now also there is introductory paragraph before 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."
This is substantive but not under a heading. Should we keep it? It's description of company. Could be placed as a
before any headings. The instruction: Use
for prose. So we can include that as opening
. It's not boilerplate. So include.
Also after benefits there is "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." This is also prose, could be included as a
after benefits maybe. It's not under a heading but it's substantive. We'll include as a
after benefits maybe before Schedule? Actually Schedule heading after that? The original order: How We Work, How We Reward You, then "Do the best work of your life..." then Diversity statement. The Diversity statement is boilerplate EEO, should be removed. So we keep the "Do the best work..." paragraph.
Thus final HTML fragment:
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.
About the role
[combined paragraphs without duplicate line]
Responsibilities
- ...
...
Requirements
- ...
...
Benefits
- ...
...
Schedule
We balance creativity and innovation on a foundation of in-person collaboration. For most roles
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we need to keep substantive info: About the Role paragraph, What You'll Do (responsibilities), What You'll Bring (requirements/qualifications/skills), How We Work (maybe schedule? but not explicit), How We Reward You (benefits). Also maybe "Do the best work of your life at Realtor.com®" etc is fluff but could be kept as prose? It's not boilerplate; it's motivational but maybe keep as part of description? The instruction: remove duplicated lines, but not remove motivational content unless it's boilerplate. It's not boilerplate but could be considered fluff. However we need to preserve ALL substantive information. That includes that paragraph? It's somewhat generic but still part of posting. I'd keep it as a
under maybe no heading? But we could put it under a heading like "About the Role" already covers that. Actually "About the Role:" heading is present in the posting. So we should create
About the role
and include the paragraph(s) under it. Then "What You'll Do:" corresponds to Responsibilities. SoResponsibilities
with list. Then "What You'll Bring:" corresponds to Requirements/Qualifications/Skills. Could split into Requirements (education, experience) and Skills (technologies). But we can combine into one section maybe "Requirements". However instruction: Prefer a few substantive sections over many thin ones. So we could have one section for Requirements/Qualifications/Skills combined. But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include. We have content for About the role, Responsibilities, Requirements (education, experience), Qualifications (maybe same), Skills (specific tech), Benefits (How We Reward You). Pay and Schedule not present (no explicit pay or schedule). So we omit Pay and Schedule sections. We could also include "How We Work" as maybe Schedule? But it's about in-person collaboration days, not schedule. Could be considered Schedule? It says "For most roles, our employees work four or more days in our offices". That's schedule info. Could be placed under Schedule heading. But the instruction: only include a section when posting has real, specific content for it. This is specific: four or more days in office. So we could create a Schedule section with that info. However we also have How We Work paragraph about in-person collaboration. That could be considered Schedule or maybe a separate section like "Work Environment". But we only have allowed headings list; we could put it under Schedule. That seems appropriate. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule. Possibly Qualifications separate? But we can combine Requirements and Qualifications into one section? The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into oneRequirements
(or Qualifications). But we need to decide which heading to use. Since we have both headings allowed, we could use Requirements for education/experience, and Qualifications for maybe "Bachelor’s degree..." etc. But they overlap. Better to have one section called Requirements (or Qualifications) that includes education, experience, technical skills. Then Skills could be separate for specific technologies? But that would be thin. Let's combine education, experience, and technical skills into Requirements. Then we could have Skills maybe empty; better not to include Skills if no distinct content beyond what's already in Requirements. So we omit Skills. Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule. Now extract content. About the role: The paragraph after "About the Role:" includes two sentences: "Are you passionate about building software solutions to solve real customer problems? Do you like fast-paced work environments? Are you excited about modern programming languages, design patterns, and scalable architectures? You’ll be right at home here!" Then following paragraph: "You will be joining the Client Mobile tech team. At Realtor, our technology team participates in the research and development of scalable applications, identifying new technologies and trends to enhance our products and business. We build innovative solutions to help customers in their buying, renting, and selling journeys by connecting them with real estate agents and partners. Join us to push the boundaries of what’s possible and learn from world-class talent that promotes a culture of experimentation and learning." Then next paragraph: "A Software Engineer at Realtor.com is an impactful contributor to our engineering team. You solve difficult problems, applying technologies with engineering best practices. You work with your team to design and build software that solves consumer and customer problems. You write stable code that a software engineer unfamiliar with the system can understand. You write stable code that a software engineer unfamiliar with the system can understand. You make appropriate trade-offs and re-use where possible. You work on project ideas with Product Management and engage with customers, stakeholders, and peers. You help the team by actively participating in the code review process, design discussions, and team planning." Note duplicate sentence about writing stable code appears twice; we should preserve but not duplicate? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we need to remove duplicated lines. The duplicate line is exactly same sentence appears twice. We should keep only one instance. Thus About the role content: combine paragraphs, removing duplicate line. Now Responsibilities: Under "What You'll Do:" bullet list (though not bullet in text). It's a series of sentences each starting with a verb. We should make- for each duty.
List:
- Develop high quality, scalable, and reliable solutions
- Work collaboratively in a squad composed of Product Managers, Designers, Analysts and Engineers.
- Help mentor and pair with peers on your team
- Investigate and prototype technologies that can be leveraged to introduce new innovations
- Be self-directed, take initiative and drive towards solutions with little guidance
- Participate in team meetings, providing opinions and insight that helps clarify requirements and technical challenges.
Now Requirements: Under "What You'll Bring:" list.
We need to extract each bullet:
- Bachelor’s degree in Computer Science or equivalent experience
- 2-3 years experience in software development
- Experience in mobile application development using React Native; familiarity with Expo is a plus
- Familiarity with GraphQL and Python
- Experience working with Postgres; AWS knowledge is preferred
- Strong understanding of system design and trade offs between design approaches
- Experience delivering high value features to customers quickly and iterating based on feedback
- Strong software engineering best practices, including testing, code reviews, and CI/CD pipelines
- Hands on experience in releasing, maintaining, and supporting mobile applications in production
We could keep as list.
Now Benefits: Under "How We Reward You:" 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
Now Schedule: Under "How We Work:" paragraph: "We balance creativity and innovation on a foundation of in-person collaboration. For most roles, 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."
We could make that as a
under Schedule heading. Now also there is introductory paragraph before 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." This is substantive but not under a heading. Should we keep it? It's description of company. Could be placed as a
before any headings. The instruction: Use
for prose. So we can include that as opening
. It's not boilerplate. So include. Also after benefits there is "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." This is also prose, could be included as a
after benefits maybe. It's not under a heading but it's substantive. We'll include as a
after benefits maybe before Schedule? Actually Schedule heading after that? The original order: How We Work, How We Reward You, then "Do the best work of your life..." then Diversity statement. The Diversity statement is boilerplate EEO, should be removed. So we keep the "Do the best work..." paragraph. Thus final HTML fragment:
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.
About the role
[combined paragraphs without duplicate line]
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...
Schedule
We balance creativity and innovation on a foundation of in-person collaboration. For most roles