Senior Data Engineer

SelectQuote Insurance Services · United States · 3 wk ago

RemoteRemoteInformation Technology$115k/yrFull-time

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule (only if present). The posting includes: Company Overview (maybe not needed as heading? It's not listed as a section heading; we can include as

maybe under About the role? But we must not repeat job title. The posting includes "About The Role" heading. We'll use

About the role

then paragraph(s). Then "Essential Duties And Responsibilities" -> Responsibilities section. Then "Skills/Abilities" -> Skills section. Then "Education And Experience" -> Qualifications (or Requirements). Could separate Requirements and Qualifications but we can combine? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content. We have: - About the role: content after "About The Role" paragraph: "Responsible for developing Data Engineering solutions...". We'll put that. - Responsibilities: from "Essential Duties And Responsibilities" list: bullet points (though they are sentences separated by periods). We'll convert each sentence to

. - Requirements: maybe "Education And Experience" could be Qualifications. But we also have "Skills/Abilities" as Skills. Could also have Requirements (like experience). We'll treat Education And Experience as Qualifications. Requirements maybe not separate; we could omit if no distinct content. But we could put Requirements as same as Qualifications? Better to follow instruction: include a section ONLY when posting has real, specific content for it. We have content for Education And Experience, so we can make a Qualifications section. For Requirements, maybe we don't have a separate list; we could skip. - Skills: from Skills/Abilities list. - Benefits: from "Our Benefits" and list. - Pay: from "Base Salary Minimum $115,000 Base Salary Maximum $130,000". Also mention incentive plans. We'll include Pay section. - Schedule: not mentioned; omit. Also need to include maybe "Supervisory Responsibilities" as part of Responsibilities? Could be a note. We'll include as a paragraph maybe under Responsibilities. We must not include boilerplate like EEO, disclaimer, visa, etc. Remove those. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the sections we include. Let's extract content. Company Overview: maybe we can include as a paragraph before About the role? Not required but could be included as part of About the role? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow. Could include Company Overview as a
before the first heading. That's okay. Let's parse: Company Overview paragraph: "More than 35 years ago, SelectQuote was founded on one core promise: to help our customers protect the people they value most. We pioneered the way consumers shopped for term life insurance, and now, we also help people find home insurance, auto insurance, senior health insurance and more. Our quick and easy process saves consumers both time and money, and today, more than 2 million families trust us to help them with their insurance needs. But what truly sets us apart is our people, and the opportunities to grow your career with SelectQuote are unmatched." We'll keep that as a
. Then About The Role heading: content: "Responsible for developing Data Engineering solutions with a strong understanding of data engineering concepts and the ability to apply those concepts broadly across multiple technologies. The Data Engineer III improves processes and methodologies across multiple projects and solutions. The Data Engineer III plays a leadership role within Enterprise Analytics leading improvement teams to enhance the department's performance and serves as a mentor to junior Data Engineers and colleagues." We'll put that as
under

About the role

. Then "Supervisory Responsibilities This position has no direct supervisory responsibilities." Could be a note under Responsibilities or separate. We'll include as a

under Responsibilities maybe. Then "Essential Duties And Responsibilities" list: sentences: - Maintain existing data engineering solutions while looking for opportunities to improve them. - Communicate both business requirements and technical terms with a high degree of understanding. - Determine business requirements and create solutions while maintaining a high level of accuracy and data integrity. - Collaborate with other team members to consolidate the data landscape to reduce the development time and increase consistency among data engineering solutions. - Lead and design complex projects and ensure their complete and accurate execution with an emphasis on delivering business value. - Train and coach junior engineers in data engineering best practices. We'll make

for each. Then "Skills/Abilities" list: items: - Strong analytical skills - Comfortable working with source control (Bitbucket git GitHub) - Knowledge of different file formats including but not limited to JSON CSV Parquet and fixed-width - Objectivity and openness to others' views providing solutions and creative input - Ability to adjust when there is a shift in priorities - Excellent communicator with individuals and groups at all levels within the organization - Detail-oriented organized and able to manage user expectations - Good organizational time management and listening skills - Self-motivated learner - Excited to work with new and different technologies - Understanding of data engineering and ETL/ELT concepts with an ability to apply those concepts to multiple technologies We'll make
- . Then "Education And Experience": - Bachelor’s degree in Engineering, Computer Science, or related field required. - 6+ years of experience working within Data systems or equivalent training - 4+ Years of strong experience troubleshooting stored procedures and other T-SQL code - 4+ years of Experience with Airflow or equivalent training - 4+ years of experience in Python coding using advanced modules Pandas Numpy and other libraries - Experience working with C# or other statically typed languages is a plus - Experience working with external REST APIs - Microsoft SQL Server 2019 or later - Microsoft SQL Server performance tuning - Experience with AWS systems and concepts for data engineering Simple Storage Solutions (S3) Lambda boto3 SQS/SNS - Experience with in-memory databases such as Redis and Elasticache We'll put as
  - under Qualifications. Then "Physical Requirements" maybe we could include as a note but not required heading. Could be omitted as not in list of headings. Might be considered boilerplate? It's substantive but not in allowed headings; we could include as a
    under Qualifications maybe? But instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should prefer those. Could include Physical Requirements as a
    under Qualifications or as a separate section not in list? Safer to omit? But we must preserve ALL substantive information. Physical Requirements is substantive. We could include as a
    under Qualifications or maybe as a separate
    Physical Requirements
    but that's not in the list; but instruction says use
    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but to follow the pattern we might include it as a
    under Qualifications or as a separate
    Physical Requirements
    but risk deviating. I'd include as a
    under Qualifications after the list, maybe preceded by a note. Then "SelectQuote Core Values" list: could be included as a
    or

Senior Data Engineer

About the role

About the role

Physical Requirements

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but to follow the pattern we might include it as a under Qualifications or as a separate

Physical Requirements

About the role

Responsibilities

Qualifications

Skills

Benefits

Pay

Core Values

Similar jobs