Senior Data Engineer - Apartments.com - Irvine, CA

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. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate. Must preserve all substantive info. We need to parse the job description. First part: description about company, mission, etc. That could be "About the role"? Actually "About the role" heading should contain description of role. The initial paragraphs about company and mission maybe not directly about role but could be considered "About the role". However we need to decide. The posting includes: "Apartments.com is growing quickly and we’re looking for a Senior Data Engineer to help accelerate our growth. This role will be responsible for helping build out sitewide tracking architecture on Apartments.com and then feeding that data into user-friendly KPI dashboards which track site performance and product usage and provide day-to day insights into consumer behavior. This individual will help build and deliver the data engineering architecture for Apartments.com and work across all departments to provide analysis and insights for future growth. You will be part of various aspects of our data management, ranging from designing and maintaining automated data infrastructure and delivering Data engineering and Analytics solutions to facilitating data access and analysis for key company teams. CoStar is investing heavily in artificial intelligence to accelerate software delivery, improve platform observability, automate research and business workflows, enhance product experiences through intelligent agents and skills, and improve data quality across enterprise systems. Successful candidates will demonstrate a willingness to learn, adopt, and apply AI technologies responsibly to solve complex business and engineering challenges." That is description of role. So we can put that under

About the role

with paragraphs. Then "Responsibilities" heading with list of responsibilities bullet points. Then "Requirements" maybe "Basic Qualifications". Could be "Requirements". Then "Preferred Qualifications" maybe "Skills"? Actually they have "Preferred Qualifications". Could be "Skills". But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Basic Qualifications and Preferred Qualifications. Could map Basic Qualifications to "Requirements". Preferred Qualifications to "Skills" or "Qualifications". But we also have "Qualifications" heading separate from Skills. Might need to decide. We have "What's In It For You?" which includes benefits and compensation. So we can have Benefits section with list of benefits. Pay section with salary range. Schedule section with Monday-Thursday in office, work from home Fridays. We need to ensure we don't include filler like "commensurate with experience". Not present. We must not include boilerplate like EEO, visa sponsorship note? The note about visa sponsorship is maybe not boilerplate but it's a condition. Should we keep? It's substantive info about eligibility. Could be included maybe in Requirements? But we can drop as it's not a heading; but we could include in a short paragraph under Requirements? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Visa sponsorship is not minor metadata? It's a condition. Might be okay to keep as a short p under Requirements or maybe under About the role. But we can drop if we consider it minor. However it's substantive: they cannot sponsor visa. Might be important. I'd include as a short paragraph under Requirements. Also note: "We welcome all qualified candidates who are currently eligible to work full-time in the United States to apply." That's also eligibility. We'll include that in Requirements. Now we need to output only HTML fragment, no markdown fences. Let's craft. Structure:

About the role

... paragraphs ...

Responsibilities

• ... each responsibility ...

Requirements

• ... basic qualifications ...

We welcome all qualified candidates who are currently eligible to work full-time in the United States to apply. However, please note that CoStar Group is not able to provide visa sponsorship for this position.

Skills

• ... preferred qualifications ...

Benefits

• ... benefits list ...

Pay

Base Compensation: $128,000-$190,000 Annually

Schedule

Monday to Thursday in the office and work from home on Fridays.

Check if any other sections like Qualifications needed? We have Skills covering preferred qualifications. Could also have Qualifications heading for something else but we don't have separate. Might be okay to omit Qualifications if no specific content. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can omit Qualifications if we don't have content. But we have Skills for preferred qualifications. Could also rename Preferred Qualifications to Skills. That's fine. Now we need to extract responsibilities list exactly as given. Responsibilities bullet points from text: - Design and Oversee implementation of dimensional modeling, database design, and cloud data platform structures (e.g., Databricks, Snowflake, BigQuery) - Develop data platform framework to build secure data warehouses and data lakehouses applying principles of Medallion Architecture - Design, develop, and maintain scalable data pipelines and ETL processes using Databricks, Snowflake, and other AWS services - Implement and optimize Spark jobs, data transformations, and data processing workflows in Databricks - Building and deploying AI/ML models: Integrate Machine Learning into data pipelines, leverage Databricks ML and AWS ML to develop predictive models and drive business insights - Define and Apply AI-assisted software development practices to improve engineering productivity and code quality - Understand various data domains and be able to translate them through data transformations to suit various business needs - Oversee automated data infrastructure: Collaborate with software engineering and product teams to streamline data tracking in our products - Ability to integrate data from disparate sources via cross domain data stitch into existing data model - Implement data governance, lineage tracking, testing, and monitoring frameworks to guarantee data integrity - Hands-on data optimization and query performance - Liaise with key company teams (DBA, DevOps, SecOps…) for data accessibility and analysis - Mentor and manage engineers and analysts in the normal execution of their responsibilities. - Successfully implement software development projects to specification and within scheduled timelines and budget parameters - Leverage AWS DevOps and CI/CD best practices to automate the deployment, through terraform, and management of data pipelines and infrastructure. We need to keep them as list items. Now Basic Qualifications list: - Bachelor's degree required from an accredited, not-for-profit, in-person college/university - A track record of commitment to prior employers - 6+ years of hands-on experience in software development, delivering high-quality solutions - Strength in Data Engineering, with strong proficiency in Python, PySpark, and SQL - Solid foundation in Object-Oriented Programming principles and best practices - Demonstrated success in building and launching data-driven products operating at terabyte scale - Proven record of designing and implementing Enterprise Level secure, and accurate Data platform - Ability to translate technical requirements into robust architecture, data models, and ETL strategies - Practical experience with cloud-based databases, including both relational and non-relational systems - Knowledge of business intelligence software (i.e. Power BI or similar tools) - Understanding of AI technologies and hands-on experience leveraging AI tooling in development (Claude Code, GitHub Copilot, Cursor, Gemini, Grok) - Ability to retrieve, synthesize, and present critical data in structures that is immediately useful to answering specific ad-hoc questions - Hands-on data experience on optimization, data quality checks, data accuracy and query performance improvement Now Preferred Qualifications list: - Hands-on experience or familiarity with big data platforms such as Databricks or Snowflake - Proficiency with cloud platforms, including AWS or Azure - Experience working with NoSQL databases (e.g., DynamoDB) and object storage systems (e.g., Amazon S3, GCS, etc.) - Practical knowledge of event streaming technologies, especially Kafka - Experience leveraging AWS compute and container services for scalable solutions - Familiarity with large language models (LLMs), prompt engineering, or agent-based architectures - Great analytical and problem-solving skills, with the ability to tackle complex technical challenges - Strong Ability to understand technical challenges and complex designs, and communicate into simple business ideas, or solutions with senior management/stakeholders Note there is a typo "Strong Ability". We'll keep as is. Now Benefits list from "Our Benefits Package Includes (but Is Not Limited To)": - Comprehensive healthcare coverage: Medical / Vision / Dental / Prescription Drug - Life, legal, and supplementary insurance - Virtual and in person mental health counseling services for individuals and family - Commuter and parking benefits - 401(K) retirement plan with matching contributions - Employee stock purchase plan - Paid time off - Tuition reimbursement - On-site fitness center and/or reimbursed fitness center membership costs (location dependent), with yoga studio, Pelotons, personal training, group exercise classes - Access to CoStar Group’s Diversity, Equity, & Inclusion Employee Resource Groups - Complimentary gourmet coffee, tea, hot chocolate, fresh fruit, and other healthy snacks Now Pay: Base Compensation: $128,000-$190,000 Annually Schedule: Monday to Thursday in the office and work from home on Fridays. Now About the role paragraph(s). We'll combine into maybe two paragraphs. Paragraph 1: Apartments.com is growing quickly and we’re looking for a Senior Data Engineer to help accelerate our growth. This role will be responsible for helping build out sitewide tracking architecture on Apartments.com and then feeding that data into user-friendly KPI dashboards which track site performance and product usage and provide day-to day insights into consumer behavior. This individual will help build and deliver the data engineering architecture for Apartments.com and work across all departments to provide analysis and insights for future growth. Paragraph 2: You will be part of various aspects of our data management, ranging from designing and maintaining automated data infrastructure and delivering Data engineering and Analytics solutions to facilitating data access and analysis for key company teams. CoStar is investing heavily in artificial intelligence to accelerate software delivery, improve platform observability, automate research and business workflows, enhance product experiences through intelligent agents and skills, and improve data quality across enterprise systems. Successful candidates will demonstrate a willingness to learn, adopt, and apply AI technologies responsibly to solve complex business and engineering challenges. Now we need to ensure we don't include any boilerplate like "Learn more about Apartments.com." That's navigation. Remove. Also remove "Apartments.com is the nation’s #1 rental marketplace..." etc. That's company description not role; but could be considered part of About the role? Might be considered generic company info. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. However we can decide to include company description under About the role? It's not about the role but about the company. The heading "About the role" expects role description. The company description may be considered not directly about role but still substantive. However we could include it as part of About the role? Might be okay but could be considered filler. The instruction says "Prefer a few substantive sections over many thin ones." So we could include a short paragraph about company under About the role before role specifics. That would preserve info. But we already have a paragraph about role. Adding company description may be okay. Let's include a brief paragraph: "CoStar Group (NASDAQ: CSGP) is a leading global provider of commercial and residential real estate information, analytics, and online marketplaces. Included in the S&P 500 Index, CoStar Group is on a mission to digitize the world’s real estate, empowering all people to discover properties, insights and