Data Engineer - AWS, Snowflake
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. Need to parse the job posting.
First, there is a preamble about Regions, etc. That is boilerplate (cookie/navigation/legal/EEO etc). We need to remove that. The job description starts after "Job Description". So we need to extract sections.
Let's parse:
Job Description At Regions, the Data Engineer focuses on the evaluation, design, and execution of data structures, processes, and logic to deliver business value through operational and analytical data assets. The Data Engineer uses advanced data design and technical skills to work with business subject matter experts to create enterprise data assets utilizing state of the art data techniques and tools.
That's prose about the role. Could be "About the role". So we can put that in About the role
then
...
. Next: Primary Responsibilities (list). Then a list of responsibilities bullet points. We'll putResponsibilities
then- each bullet.
After responsibilities, there is a sentence: "This position is exempt from timekeeping requirements under the Fair Labor Standards Act and is not eligible for overtime pay." That's maybe not a section; could be part of Requirements? It's about FLSA exemption. Might be considered part of Requirements? Not exactly. Could be omitted? It's substantive but not a heading. Could be placed in a
under Requirements? Might be better to include as a separate paragraph under Requirements? But guidelines: Use headings only for sections with real content. Could include a short paragraph under Requirements? But it's not a requirement. Could be placed under "About the role"? Might be okay to include as a
after responsibilities before Requirements. Next: Requirements (list). Then Preferences (list). Then Skills And Competencies (list). Then "This position is intended to be onsite, now or in the near future. Associates will have regular work hours, including full days in the office three or more days a week. The manager will set the work schedule for this position, including in-office expectations. Regions will not provide relocation assistance for this position, and relocation would be at your expense. The locations available for this role are Birmingham, AL, Atlanta, GA or Charlotte, NC. Regions will not sponsor applicants for work visas for this position at this time. Applicants for this position must currently be authorized to work in the United States on a full-time basis." This includes schedule info (onsite, work hours). Could be Schedule section. Also location info maybe not needed. But we can include Schedule section with that content. Then: Position Type Full time (maybe not needed). Compensation Details (Pay). Then Benefits Information (Benefits). Then Location Details (Charlotte Uptown Location...). Then EEO boilerplate etc to remove. We need to include Pay section only if posting states them. It does: Minimum Job Range Target: $115,002.20 USD Median $146,401.50 USD Incentive Pay Plans Opportunity to participate in the Long Term Incentive Plan. So we can include Pay section. Benefits section: they list benefits. So include Benefits. Schedule: we have info about onsite, work hours, etc. So include Schedule. Qualifications? The posting has Requirements (education/experience), Preferences, Skills And Competencies. Could map Requirements to Requirements heading, Preferences maybe part of Requirements? But we have Qualifications heading as an option. Could treat Requirements as Qualifications? The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which to use. We have Requirements (education/experience). We have Preferences (maybe could be part of Requirements or Qualifications). We have Skills And Competencies (Skills). Could also have Qualifications (maybe combine Requirements and Preferences?). But we should not create thin sections. Better to have Requirements (education/experience), Skills (Skills And Competencies), and maybe combine Preferences into Requirements or Skills? But we need to preserve all substantive information. So we need to include Preferences somewhere. Could add a
Qualifications
for Preferences? Or we could include Preferences under Requirements as a list? But that would mix education/experience with preferences. Might be okay but could be less clear. However instruction: Prefer a few substantive sections over many thin ones. So we could have Requirements (education/experience + preferences) and Skills (skills). That would be two sections plus About, Responsibilities, Benefits, Pay, Schedule. That's many but okay. But we have headings list includes Qualifications; we could use Qualifications for Preferences and Skills for Skills And Competencies. Requirements for education/experience. That would be three sections: Requirements, Qualifications, Skills. That seems reasonable. Let's extract content. About the role: The first paragraph after Job Description. Responsibilities: list of bullet points under Primary Responsibilities. Requirements: education/experience requirements (Ph.D..., Master's..., Bachelor's..., Three (3) years of working programming experience..., Three (3) years of working experience in Big Data Technology...). That's a list. Qualifications: Preferences list (Background in Big Data Engineering..., Experience developing solutions for the financial services industry..., Experience in Agile Software Development..., Experience or exposure to cloud technologies and migrations..., Prior banking or financial services experience). That's a list. Skills: Skills And Competencies list (Ability to interpret..., Experience building..., Experience designing..., Experience with DevOps..., Experience with No-SQL..., Experience with large-scale data Lakehouses..., Proven record..., Significant experience..., Strong background..., Strong technical background..., Strong communication skills...). That's a list. Benefits: list of benefits (Paid Vacation/Sick Time, 401K with Company Match, Medical, Dental and Vision Benefits, Disability Benefits, Health Savings Account, Flexible Spending Account, Life Insurance, Parental Leave, Employee Assistance Program, Associate Volunteer Program). Also note about benefits may change. Pay: Minimum Job Range Target: $115,002.20 USD Median $146,401.50 USD Incentive Pay Plans Opportunity to participate in the Long Term Incentive Plan. Schedule: This position is intended to be onsite, now or in the near future. Associates will have regular work hours, including full days in the office three or more days a week. The manager will set the work schedule for this position, including in-office expectations. Regions will not provide relocation assistance for this position, and relocation would be at your expense. The locations available for this role are Birmingham, AL, Atlanta, GA or Charlotte, NC. Regions will not sponsor applicants for work visas for this position at this time. Applicants for this position must currently be authorized to work in the United States on a full-time basis. We might also include Position Type Full time but not needed. We need to output only HTML fragment. Usefor each section heading. Use
- for lists. Use
for prose. We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate: EEO, legal, etc. Let's craft. First, About the role paragraph: "At Regions, the Data Engineer focuses on the evaluation, design, and execution of data structures, processes, and logic to deliver business value through operational and analytical data assets. The Data Engineer uses advanced data design and technical skills to work with business subject matter experts to create enterprise data assets utilizing state of the art data techniques and tools." Second, Responsibilities list: need to capture each bullet. From text: "Partners with Regions Technology partners to Design, Build, and Maintain the data-based structures and systems in support of Data and Analytics and Data Product use cases" "Builds data pipelines to collect and arrange data and manage data storage in Regions’ big data environment" "Builds robust, testable programs for moving, transforming, and loading data using big data tools such as Spark" "Coordinates design and development with Data Products Partners, Data Scientists, Data Management, Data Modelers, and other Technical partners to construct strategic and tactical data stores" "Ensures data is prepared, arranged and ready for each defined business use case" "Designs and deploys frameworks and micro services to serve data assets to data consumers" "Collaborates and aligns with technical and non-technical stakeholders to translate customer needs into Data Design requirements, and work to deliver world-class visualizations, data stories while ensuring data quality and integrity" "Provides consultation to all areas of the organization that plan to use data to make decisions" "Supports any team members in the development of such information delivery and aid in the automation of data products" "Acts as trusted adviser and partner to business leads- assisting in the identification of business needs & data opportunities, understanding key drivers of performance, interpreting business case data drivers, turning data into business value, and participating in the guidance of the overall data and analytics strategy" "Ensures compliance with risk management programs, rules and regulations, and cybersecurity practices; identifies opportunities for and supports process improvements; applies disciplined change management practices" We'll put each as
- .
Third, Requirements list:
"Ph.D. and two (2) years of experience in a quantitative/analytical/STEM field"
"Or Master’s degree and four (4) years of experience in a quantitative/analytical/STEM field or technical related field"
"Or Bachelor's degree and six (6) years of experience in a quantitative/analytical/STEM field or technical related field"
"Three (3) years of working programming experience in Python/PySpark, Scala, SQL"
"Three (3) years of working experience in Big Data Technology in Hadoop, Hive, Impala, Spark, or Kafka"
We'll put as list.
Fourth, Qualifications (Preferences) list:
"Background in Big Data Engineering and Advanced Data Analytics"
"Experience developing solutions for the financial services industry"
"Experience in Agile Software Development"
"Experience or exposure to cloud technologies and migrations"
"Prior banking or financial services experience"
Fifth, Skills list:
"Ability to interpret and ensure compliance with applicable rules, regulations, and industry guidance"
"Experience building data solutions at scale"
"Experience designing and building relational data structures in multiple environments"
"Experience with DevOps principals, CI/CD, and Software Development Lifecycle"
"Experience with No-SQL databases"
"Experience with large-scale data Lakehouses at Enterprise scale"
"Proven record of accomplishment of delivering operational Data solutions including Report and Model Ready Data Assets"
"Significant experience working with senior executives in the use of data, reporting and visualizations to support strategic and operational decision making"
"Strong background in synthesizing data and analytics in a large (Fortune 500), complex, and highly regulated environment"
"Strong technical background including database and business intelligence skills"
"Strong communication skills through written and oral presentations"
Sixth, Benefits list:
"Paid Vacation/Sick Time"
"401K with Company Match"
"Medical, Dental and Vision Benefits"
"Disability Benefits"
"Health Savings Account"
"Flexible Spending Account"
"Life Insurance"
"Parental Leave"
"Employee Assistance Program"
"Associate Volunteer Program"
We could also include note about benefits may change but that's boilerplate? It's a note but could be included as a
after list. Might be okay. Seventh, Pay section: we need to include the pay details. Could be a
with the text. Eighth, Schedule section: include the paragraph(s) about onsite, work hours, location, visa, work authorization. We should not include location details as separate heading; we can embed in Schedule paragraph. Now ensure we don't include any filler like "commensurate with experience". Not present. Now produce HTML. We'll start with
About the role
...
ThenResponsibilities
- ...
Requirements
- ...
Qualifications
- for lists. Use