Data Engineer II

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We have Position Summary (could be About the role). Qualifications list. Core Competencies (maybe Skills). Essential Duties (Responsibilities). Physical Requirements and Work Environment maybe not needed unless they map to Benefits/Pay/Schedule? They are not Benefits/Pay/Schedule. So we may omit Benefits, Pay, Schedule sections because no info. Also we have no explicit "Skills" but Core Competencies could be Skills. Also we have Qualifications section. Also we have "Essential Duties" as Responsibilities. Also "Position Summary" as About the role. We must not repeat job title as heading. No Job ID. Remove boilerplate like Physical Requirements? It's substantive but not a required heading; we could include as a

under maybe a generic section? But we only have allowed headings list; we could still include paragraphs without heading? 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 that pattern. Probably we should only use those headings when content exists. For Physical Requirements and Work Environment, we could put them under a generic

without heading? Might be okay but better to include them as part of Responsibilities? Not really. Could create a section "Working Conditions" but not in list. Safer to include them as paragraphs after the sections, without heading? The instruction says use those headings for section headings; doesn't say you can't have other headings, but better to stick to given ones. We could incorporate Physical Requirements and Work Environment into a "Responsibilities" or "About the role"? Not ideal. Maybe we treat Physical Requirements and Work Environment as part of "About the role" or as a separate

without heading. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose." So we can have prose paragraphs not under a heading? Probably yes, but we should structure with headings for each major section. We could have:

  About the role

  Position Summary: ...

  Responsibilities

  • ... essential duties list

  Qualifications

  • ... qualifications list

  Skills

  • ... core competencies list
  We should not include Benefits, Pay, Schedule. We must preserve all substantive information; not invent or summarize away detail. So we need to include all details from Position Summary, Qualifications, Essential Duties, Core Competencies. Also maybe Physical Requirements and Work Environment should be included as prose paragraphs after Skills? Could add a heading like "Working Conditions" but not allowed. Could add as

  under maybe a generic

  Other Details

  but not in list. Might be considered adding a heading not in list, which may be okay but risk. Better to include them as paragraphs after Skills without a heading, but that may be okay. Let's extract content. Position Summary: "The Data Engineer II will be responsible for designing, building, and maintaining the bank's data infrastructure and systems. This role involves working with cross-functional teams to ensure efficient data integration, transformation, and storage. The Data Engineer II will collaborate closely with data scientists, analysts, and stakeholders to develop robust data solutions that support the bank's data-driven initiatives." Qualifications: list bullet points: - Bachelor's degree in Computer Science, Information Systems, or a related field. A master's degree is a plus. - Proven experience as a Data Engineer or similar role, preferably in the banking or financial industry. - Strong knowledge of data engineering concepts, techniques, and best practices. - Proficiency in SQL and experience with relational databases (e.g., Oracle, SQL Server, MySQL). - Experience with programming languages such as Python, Java, or Scala. - Solid understanding of ETL processes, data integration, and data transformation. - Experience in designing and implementing data warehouses, data lakes, or similar data storage solutions. - Familiarity with cloud platforms like AWS, Azure, or Google Cloud, including relevant data services (e.g., S3, Redshift, BigQuery). - Knowledge of data governance, data quality, and data security practices. - Experience with big data technologies such as Hadoop, Spark, or similar frameworks. - Proficiency in data modeling and database design principles. - Strong analytical and problem-solving skills. - Excellent communication and collaboration abilities. - Ability to manage multiple tasks and work in a fast-paced environment. Core Competencies: list bullet points under categories: Career Development, Communicates Effectively, Focuses on the Client, Judgment, Teamwork. Each has multiple sentences. We need to preserve all substantive information; we can turn each bullet into
• with the full text. Essential Duties: list bullet points: - Design, build, and maintain the bank's data infrastructure, including data pipelines, databases, and data warehouses. - Develop and optimize ETL processes to efficiently extract, transform, and load data from various sources into the bank's data storage systems. - Collaborate with data scientists, analysts, and business stakeholders to understand data requirements and develop scalable data solutions that support analytics and reporting needs. - Implement data governance policies and ensure data quality, consistency, and security throughout the data lifecycle. - Perform data modeling and database design activities to support data integration, storage, and retrieval. - Monitor and optimize data engineering systems and processes for performance, scalability, and reliability. - Collaborate with IT teams to ensure seamless integration of data engineering solutions with existing infrastructure and applications. - Stay updated with industry trends, emerging technologies, and best practices in data engineering. - Mentor and provide guidance to junior data engineers, promoting knowledge sharing and professional development within the team. - Document data engineering processes, workflows, configurations, and system architectures. Physical Requirements: paragraph: "The physical demands described here are representative of those that must be met by an employee to successfully perform the essential functions of this job. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. While performing the duties of this job, the employee is regularly required to sit, use hands to finger, handle or feel, reach with hands and arms, and talk or hear. The employee is frequently required to stand and walk. The employee may occasionally lift and/or move up to 10 pounds. Ability to reach destinations within the Orrstown footprint at all times is required. Ability to work and report to the employer’s physical work location(s)." Work Environment: paragraph: "Work is performed in an office setting with little to moderate exposure to noise, heat, dust or other adverse factors. Working extended hours may be required as needed. The noise level in the work environment is usually quiet." We should include these as prose paragraphs maybe under a heading like "Working Conditions" but not in list. Could add as

  after Skills without heading. That preserves info. Now produce HTML fragment. We need to ensure no extra text, just HTML. Let's craft:

  About the role

  The Data Engineer II will be responsible for designing, building, and maintaining the bank's data infrastructure and systems. This role involves working with cross-functional teams to ensure efficient data integration, transformation, and storage. The Data Engineer II will collaborate closely with data scientists, analysts, and stakeholders to develop robust data solutions that support the bank's data-driven initiatives.

  Responsibilities

  • Design, build, and maintain the bank's data infrastructure, including data pipelines, databases, and data warehouses.
  • Develop and optimize ETL processes to efficiently extract, transform, and load data from various sources into the bank's data storage systems.
  • Collaborate with data scientists, analysts, and business stakeholders to understand data requirements and develop scalable data solutions that support analytics and reporting needs.
  • Implement data governance policies and ensure data quality, consistency, and security throughout the data lifecycle.
  • Perform data modeling and database design activities to support data integration, storage, and retrieval.
  • Monitor and optimize data engineering systems and processes for performance, scalability, and reliability.
  • Collaborate with IT teams to ensure seamless integration of data engineering solutions with existing infrastructure and applications.
  • Stay updated with industry trends, emerging technologies, and best practices in data engineering.
  • Mentor and provide guidance to junior data engineers, promoting knowledge sharing and professional development within the team.
  • Document data engineering processes, workflows, configurations, and system architectures.

  Qualifications

  • Bachelor's degree in Computer Science, Information Systems, or a related field. A master's degree is a plus.
  • Proven experience as a Data Engineer or similar role, preferably in the banking or financial industry.
  • Strong knowledge of data engineering concepts, techniques, and best practices.
  • Proficiency in SQL and experience with relational databases (e.g., Oracle, SQL Server, MySQL).
  • Experience with programming languages such as Python, Java, or Scala.
  • Solid understanding of ETL processes, data integration, and data transformation.
  • Experience in designing and implementing data warehouses, data lakes, or similar data storage solutions.
  • Familiarity with cloud platforms like AWS, Azure, or Google Cloud, including relevant data services (e.g., S3, Redshift, BigQuery).
  • Knowledge of data governance, data quality, and data security practices.
  • Experience with big data technologies such as Hadoop, Spark, or similar frameworks.
  • Proficiency in data modeling and database design principles.
  • Strong analytical and problem-solving skills.
  • Excellent communication and collaboration abilities.
  • Ability to manage multiple tasks and work in a fast-paced environment.

  Skills

  • Career Development: Proactively prepares and actively participates in ongoing, candid, constructive monthly Coaching sessions with supervisor. Seeks advancement into challenging and developmental roles and assignments. Sets and meets clear, measurable goals.
  • Communicates Effectively: Demonstrates the ability to effectively communicate with all employees and clients, regardless of level. Communicates clearly, concisely, with candor and confidence. Writes, speaks and listens to disseminate and receive information effectively and accurately. Seeks to understand the viewpoints of others. Keeps others informed in a timely manner.
  • Focuses on the Client: Anticipates and identifies internal and external client needs. Takes action to meet and, where possible, exceed client expectations. Plans and organizes work effectively to facilitate responsiveness to client and meet deadlines.
  • Judgment: Demonstrates sound reasoning and well-balanced thinking. Balances the need for action with the need for analysis. Incorporates strategic thinking skills into practice by examining facts. Shows an ability to problem solve complex issues. Probes beyond symptoms to determine the underlying cause. Learns from and accepts responsibility from mistakes.
  • Teamwork: Demonstrates the ability to enhance the department and Orrstown Banks development through participation. Holds self and others accountable for exceeding departmental and corporate goals. Develops strong working relationships throughout the organization. Appropriately voices opinions, even if they are contrary to the consensus of the team. Initiates and develops positive working relationships with others in a way that builds bridges across boundaries and breaks down silos. Relates to others in an open and accepting manner that creates trust, respect and a collaborative environment.

  The physical demands described here are representative of those