Quality Automation Engineer III

We need to output HTML fragment with sections: About the role? The description includes "Job Description" intro, then "Who You Are", "What You’ll Do", "What You’ll Need", "Additional Preferred Skills", "Our Benefits". Also there is some intro about Frost legacy etc. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly. We should not repeat job title as heading. No Pay/Schedule unless present. No Pay or Schedule info present, so omit those sections. We need to include sections only when there is real specific content. So we can have sections: About the role (maybe combine intro and Who You Are?), Responsibilities (What You’ll Do), Requirements (What You’ll Need), Skills (Additional Preferred Skills), Benefits (Our Benefits). Possibly Qualifications could be merged with Requirements. But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include those that have content. We have content for About the role: introductory paragraphs about Frost, mission, legacy, etc. Also "Who You Are" could be part of About the role. We'll put that under About the role. Responsibilities: "What You’ll Do" list. Requirements: "What You’ll Need" list (mandatory). Qualifications: maybe we could treat "What You’ll Need" as Requirements, and Qualifications could be empty; better not to include Qualifications if no distinct content. But we could split: Requirements = mandatory, Qualifications = preferred? However we have Additional Preferred Skills separate. Could map Qualifications to "Additional Preferred Skills"? But we already have Skills heading. The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Skills for technical skills, Qualifications for education/experience? But we have both. Let's decide: - About the role: intro + Who You Are. - Responsibilities: What You’ll Do. - Requirements: What You’ll Need (mandatory). - Qualifications: maybe we could include "Bachelor’s degree..." etc but that's already in Requirements. Could treat Qualifications as same as Requirements but we shouldn't duplicate. Better to omit Qualifications if no distinct content beyond Requirements. But we might include Qualifications for education/experience and Requirements for technical skills? However the instructions say "Prefer a few substantive sections over many thin ones." So we should combine similar content. Thus we can have: About the role, Responsibilities, Requirements (includes education, experience, technical skills), Skills (Additional Preferred Skills), Benefits. We must not include Pay or Schedule. Now we need to format lists with

• . For prose use

  . We must preserve all substantive information, not invent or summarize away detail. So we need to keep all bullet points exactly as given. Let's extract content. Intro paragraphs: "It’s about putting our best to the test. Are you described as someone with an inquisitive mind and an innovative personality? Are you never satisfied with good enough? Does solving complex problems and ensuring top-quality applications excite you? If so, being a Quality Automation Engineer III with Frost could be for you. At Frost, it’s about more than a job. It’s about having a flourishing career where you can thrive, both in and out of work. At Frost, we’re committed to fostering an environment that reflects our values and encourages team members to be the best they can be. In joining our adaptable, integrity-driven team, you’ll become part of Frost’s over 150-year legacy of providing unparalleled banking services." Then "Who You Are" paragraph: "As a Quality Automation Engineer III, you are our quality control, ensuring every application is stable and built with integrity, caring and excellence. You’ll play an important role in the design, creation, and testing of applications to ensure the quality and stability in every system. You’ll use your strong problem-solving skills to ensure that the applications are performing optimally and meet our high standards. You are not afraid to ask the question why and thrive in a collaborative environment." We can combine these into About the role section. Now Responsibilities: "What You’ll Do" list: - Oversee, design, review, build, and deploy test automation solutions and framework for the most complex, interrelated systems to ensure the quality and stability of software applications - Lead the troubleshooting and triage of the most complex escalated system issues with project teams to identify the root causes, resolve issues, and implement process improvements - Guide and mentor other Test Automation Engineers to ensure that their test automation solutions and scripts align with Frost’s automation framework and industry standards - Collaborate with product management, project management, development teams, and business stakeholders to develop project, product, and testing objectives - Write and execute functional test cases as needed - Always take action using Integrity, Caring, and Excellence to achieve all-win outcomes Now Requirements: "What You’ll Need" list: - Bachelor’s degree in a technical field or equivalent experience - 4+ years of test automation experience - Technical development experience with multiple programming or scripting languages while using Selenium as framework - Expertise with JAVA and SQL queries - Strong understanding of Object-Oriented programming concepts - Expertise in independently identifying technical issues including misconfigurations and defects in code - Demonstrated experience in developing functional, load, and batch test automation solutions - Expert knowledge of the role of Test Automation and Software Quality Assurance in the development process - Experience with test automation frameworks and design patterns - Experience with a distributed version-control management system like GIT Now Additional Preferred Skills list: - Experience with Selenium WebDriver - Experience using automated testing tools like Junit, TestNG, Cucumber, Appium, JMeter, SoapUI - Knowledge of DevOps including Jenkins, Maven etc. - Knowledge of Non-Functional Testing (Performance, Security and Accessibility Testing) Now Benefits list: - Medical, dental, vision, long-term disability, and life insurance - 401(k) matching - Generous holiday and paid time off schedule - Tuition reimbursement - Extensive health and wellness programs, including our Employee Assistance Program - Referral bonus program + more! Also there is some additional company description after benefits: "Since 1868, Frost has dedicated their expertise to provide exceptional banking, investment, and insurance services to businesses and individuals throughout Texas. Frost is one of the 50 largest U.S. banks by asset size and is a leader in banking customer satisfaction. At Frost, it’s about being part of something bigger. If this sounds like you, we encourage you to apply and see what’s possible at Frost." This is more about company, could be part of About the role or maybe a separate section? But we have no heading for company overview. Could include in About the role as additional prose. We must not include application instructions, boilerplate, etc. The last sentence encourages to apply - that's application instruction, should be removed. Also "If this sounds like you, we encourage you to apply and see what’s possible at Frost." That's application instruction, remove. Also the preceding sentences about Frost history could be kept as part of About the role. Thus we keep: "Since 1868, Frost has dedicated their expertise to provide exceptional banking, investment, and insurance services to businesses and individuals throughout Texas. Frost is one of the 50 largest U.S. banks by asset size and is a leader in banking customer satisfaction. At Frost, it’s about being part of something bigger." (remove the encouragement to apply). That's substantive. Now we need to output HTML fragment only. Structure:

  About the role

  ...combined intro and Who You Are and company overview...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Skills

  • ...
  ...

  Benefits

  • ...
  ...
  Make sure to preserve punctuation exactly. Let's craft the About the role paragraph(s). Could be multiple

  elements. We'll combine into maybe two paragraphs: first the motivational intro, second the Who You Are, third the company overview. But we can also put all in one

  but that may be long. It's okay to have multiple

  under same heading? The instruction: Use

  for prose. It doesn't forbid multiple

  . We'll output multiple

  under the heading. Thus:

  About the role

  It’s about putting our best to the test. Are you described as someone with an inquisitive mind and an innovative personality? Are you never satisfied with good enough? Does solving complex problems and ensuring top-quality applications excite you? If so, being a Quality Automation Engineer III with Frost could be for you. At Frost, it’s about more than a job. It’s about having a flourishing career where you can thrive, both in and out of work. At Frost, we’re committed to fostering an environment that reflects our values and encourages team members to be the best they can be. In joining our adaptable, integrity-driven team, you’ll become part of Frost’s over 150-year legacy of providing unparalleled banking services.

  As a Quality Automation Engineer III, you are our quality control, ensuring every application is stable and built with integrity, caring and excellence. You’ll play an important role in the design, creation, and testing of applications to ensure the quality and stability in every system. You’ll use your strong problem-solving skills to ensure that the applications are performing optimally and meet our high standards. You are not afraid to ask the question why and thrive in a collaborative environment.

  Since 1868, Frost has dedicated their expertise to provide exceptional banking, investment, and insurance services to businesses and individuals throughout Texas. Frost is one of the 50 largest U.S. banks by asset size and is a leader in banking customer satisfaction. At Frost, it’s about being part of something bigger.

  Now Responsibilities

  Responsibilities

  ...
  Requirements

  Requirements

  ...
  Skills

  Skills

  ...
  Benefits

  Benefits

  ...
  Check that we didn't miss any content: The "What You’ll Do" includes "Always take action using Integrity, Caring, and Excellence to achieve all-win outcomes". Keep. Check that we didn't inadvertently include boilerplate: The original had "Our Benefits At Frost, we care about your health, your family, and your future and strive to have our benefits reflect that. This includes:" We turned that into list items; we omitted the introductory sentence. That's okay because we preserved the list items. The intro sentence is not essential? It's prose describing benefits; we could include it as a

  before the list. The instruction: preserve ALL substantive information; do not invent or summarize away detail. The sentence "Our Benefits At Frost, we care about your health, your family, and your future and strive to have our benefits reflect that. This includes:" is substantive. Should we keep it? We could include a

  before the list. That would be better. Similarly for Requirements: there is an intro "What You’ll Need". Could keep as a

  before list. For Responsibilities: "What You’ll Do". Could keep as a

  . For Skills: "Additional Preferred Skills". Could keep as a

  . For About the role we already have prose. Thus we should include those introductory sentences as

  before the

  . Let's do that. Thus:

  Responsibilities

  What You’ll Do

  ...
  Similarly for Requirements:

  What