Senior Software Engineer - Content & Industry Services
Realtor.com · Austin, TX · 3 wk ago
HybridInformation TechnologyFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO etc. Must preserve all substantive info.
We need to parse the description.
The description includes:
- Intro about Realtor.com (company description) - maybe not needed? It's not a section heading. Could be part of About the role? Actually "About The Role:" heading present. So we should put that content under
About the role
with paragraphs. - Then "What You’ll Do:" corresponds to Responsibilities. - Then "What You'll Bring:" corresponds to Requirements/Qualifications/Skills? We need to split appropriately. The posting lists many bullet-like sentences but not actual bullet list. We need to convert to- for any list of duties/requirements/benefits. The text includes sentences separated by periods. We can treat each sentence as a list item? The instruction: Use
- for any list of duties/requirements/benefits. So we need to identify lists. The "What You’ll Do:" section has multiple sentences each starting with a verb. Could treat as list.
Similarly "What You'll Bring:" includes many bullet-like sentences.
Also "How We Work:" and "How We Reward You:" sections correspond to Benefits? Actually "How We Reward You:" lists benefits. So we should create Benefits section with list.
Pay and Schedule: Not mentioned explicitly. No pay or schedule details. So we should not include those sections.
We also have "Who We Are:" maybe could be part of About the role? But we already have About the role section. Could include company description as part of About the role? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have those headings only if content exists. We have About the role, Responsibilities, Requirements (maybe combine Requirements and Qualifications?), Skills, Benefits. We need to decide how to split "What You'll Bring:" into Requirements, Qualifications, Skills. The posting includes: "Proven track record of delivering high-quality products and writing clean, maintainable code..." etc. Those are qualifications/requirements. Also "Full-stack expertise..." etc. Also "Programming Skills – Proficiency in multiple programming languages..." etc. Also "Cloud & Platform Skills – Experience with cloud-based development..." etc. Also "Exposure to build, test and deployment automation technologies." etc. Also "Familiarity with CI/CD pipelines..." etc. Also "Exposure to monitoring systems..." etc. Also "Proven experience of applying a deep understanding of computer science fundamentals..." etc. Also "Bachelor’s degree in Computer Science, Engineering, or a related field; Master’s degree is a plus." Thus we can categorize: Requirements (maybe years of experience, degree), Qualifications (maybe similar), Skills (technical skills). But we can also combine into Requirements and Skills sections. The instruction says prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (including qualifications and skills), Benefits. That would be 4 sections. But we need to follow the headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can omit Qualifications and Skills if we merge into Requirements? However the instruction: "Prefer a few substantive sections over many thin ones." So we can combine Qualifications and Skills into Requirements or maybe have Requirements and Skills separate if content distinct. Let's see: The posting has clear skill enumerations: programming languages, cloud & platform skills, CI/CD, monitoring, CS fundamentals. Those could be Skills. Requirements could be years of experience, degree, self-starter, etc. Qualifications maybe overlapping. To avoid thin sections, we could have Requirements (including experience, degree, personal attributes) and Skills (technical). That's two sections plus About the role, Responsibilities, Benefits. That's 5 sections, still reasonable. We must not create Pay or Schedule sections as no content. Now we need to extract content. About the role: The paragraph after "About The Role:" up to before "What You’ll Do:"? Let's capture: "About The Role:Data is the vital lifeblood upon which all of our tools and experiences are built. Content is an enabler and a multiplier that allows us to personalize our products, make better decisions and manage our risks. We have an exciting and unique opportunity for a motivated and energetic Senior Software Engineer to join the Realtor.com Content team. In this position, you will help make valuable data easily accessible for everyone. You will work across the full stack developing and operating mission critical systems that integrate with thousands of data sources and process millions of records daily. This role will involve investing in AI-driven solutions to improve content quality and developer efficiency. You will ship code that ensures the flow of content onto realtor.com and across our publisher network to reach tens of millions of consumers, learn about and leverage new technologies, work with an experienced team of engineers and be part of a team that has a lot of fun along the way!" We'll put that as
... maybe multiple sentences but we can keep as one paragraph. Responsibilities: "What You’ll Do:" list: - Collaborate closely with Product Managers, Designers, and fellow Engineers to deliver high-impact solutions that drive business value. - Lead by example, championing process improvements that enhance code quality, team efficiency, and the predictability of deliverables. - Mentor and coach engineers across all levels, fostering a culture of growth, ownership, and engineering excellence. - Design, build, and maintain robust, user-centric application features that deliver intuitive and delightful experiences. - Design, develop, and operationalize scalable backend services, data pipelines, and distributed systems using modern data architectures on AWS. - Apply AI and automation to improve data quality, monitoring, and operational efficiency. - Continuously optimize the developer experience by improving the toolchain, automating infrastructure provisioning, and streamlining CI/CD pipelines. - Stay current with emerging technologies; evaluate and recommend tools and frameworks that improve our architecture, performance, or developer productivity. - Work in a product development process that is primarily Agile/Scrum. We'll make each as
- .
Requirements: maybe include: "Self-starter who can independently manage projects, prioritize effectively, and set clear expectations with stakeholders." plus "5+ years of experience developing web applications, web services, and data pipelines." plus "Bachelor’s degree in Computer Science, Engineering, or a related field; Master’s degree is a plus." plus "Deep respect for data, with a meticulous approach to ensuring data accuracy, consistency, and integrity throughout the system." plus "Strong attention to detail, a keen eye for design, and a commitment to delivering exceptional user experiences." plus "Proven track record of delivering high-quality products and writing clean, maintainable code in a fast-paced, collaborative environment." plus maybe "Proven experience of applying a deep understanding of computer science fundamentals, including data structures, algorithms, and schema/database design." but that could be skill. We'll decide.
Skills: technical skills list:
- Proficiency in multiple programming languages and frameworks such as Python, Go, JavaScript, and ReactJS, with a willingness to quickly learn new technologies as needed.
- Experience with cloud-based development, deployment, and architecture, including tools and technologies such as CircleCI, Kafka, Kubernetes, GraphQL, MySQL, PostgreSQL, and AWS services (EC2, S3, RDS).
- Exposure to build, test and deployment automation technologies.
- Familiarity with CI/CD pipelines, automated testing, and deployment best practices.
- Exposure to monitoring systems, incident alerting, and service reliability practices to support SLAs.
We could also include "Full-stack expertise, with hands-on experience building and maintaining scalable frontend and backend systems." maybe skill.
Benefits: from "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
Also "How We Work:" maybe not benefit but could be part of culture; but we can ignore or include as part of Benefits? It's about in-person collaboration. Could be considered a benefit? Might be considered a work style. The instruction: include Benefits section only if posting actually states them. It does state benefits. So we include those.
We should not include EEO etc.
Now produce HTML fragment:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
- ... ...
- for any list of duties/requirements/benefits. So we need to identify lists. The "What You’ll Do:" section has multiple sentences each starting with a verb. Could treat as list.
Similarly "What You'll Bring:" includes many bullet-like sentences.
Also "How We Work:" and "How We Reward You:" sections correspond to Benefits? Actually "How We Reward You:" lists benefits. So we should create Benefits section with list.
Pay and Schedule: Not mentioned explicitly. No pay or schedule details. So we should not include those sections.
We also have "Who We Are:" maybe could be part of About the role? But we already have About the role section. Could include company description as part of About the role? The instruction: Use