Software Engineer Senior (Appian Group)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate. Preserve all substantive info. Let's parse the posting. First paragraph: "We are a hybrid, remote-office company dedicated to growing our talent anywhere! We have onsite locations in: Sioux Falls, SD, Scottsdale, AZ, Louisville, KY, Troy, MI, Franklin, TN, Easton, PA. At Pathward, we take tremendous pride in our purpose to create financial inclusion for all™. We are a financial empowerment company that works with innovators to increase financial availability, choice, and opportunity for all. We strive to remove barriers that traditional institutions put in the way of financial access, and promote economic mobility by providing responsible, secure, high quality financial products. We are a team of problem solvers and innovators who celebrate our differences and know that our unique perspectives make us stronger and well-positioned for success. We celebrate, and embrace, our team members through our *HUMBLE*HUNGRY*SMART approach, and we believe that we are strongest when we embrace the voices of our employees, customers, partners, and the communities we serve." This is generic company description; could be considered "About the role"? Actually "About the Role:" heading appears later. The earlier part is more about company. Might be considered "About the role"? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real, specific content for it. The "About the Role:" heading appears with content: "Applies knowledge of the technologies in Pathward’s technical stack to develop solutions. Responsible for working as part of a team and is required to perform all duties of software development including design, development, testing, and documentation." Thus we can have About the role section with that content. Then "What You Will Do:" list of duties. That's responsibilities. So Responsibilities section with bullet list. Then "What You Will Need:" list of qualifications/requirements. That includes education, experience, specific required skills, preferred knowledge, etc. We need to split into Requirements, Qualifications, Skills maybe. The instruction: prefer a few substantive sections over many thin ones. But we have to use headings as given if content exists. We can decide to combine some. We have: Bachelor's degree in technical field or equivalent education and work experience required. Typically, 5+ years of experience working in a professional technical environment. 4 years of professional software design and development experience required. Hands-on experience with the Appian low-code platform (application development, process modeling) is required. Experience integrating Appian with external systems and services (APIs, data sources) is required. General knowledge of Python, YAML, JSON, Azure DevOps, and Git source control is preferred. General knowledge of the software development lifecycle, preferably Agile/Lean or Kanban preferred. Experience with the following technologies is expected, but not all are required: General knowledge of .NET, C#, ASP.NET, MVC, Classic ASP, VB Script, Entity Framework, WPF, JavaScript, IIS, HTML, CSS, XML/XSLT, MSMQ, NServiceBus, Visual Studio, Team Foundation Server, Git, or other source control tools required. Experience with Visual Studio, Azure DevOps, Git, or other source control tools preferred. Cloud development experience with Azure or AWS a plus. Effectively work within a team environment Effective written and oral communication Ability to teach and mentor other software engineers Thus we have requirements (education, years experience, required Appian experience, integration experience). Qualifications maybe the preferred knowledge. Skills maybe the list of technologies. We also have Salary range: $86,000 – $145,000. That's Pay section. Benefits: "Pathward offers a comprehensive benefits package for eligible employees, including health insurance, 401(k) retirement benefits, life insurance, disability benefits, paid time off, and more." Thus Benefits section. Schedule: Not mentioned. No schedule info. So we should not include Schedule. Also there is "The responsibilities listed above are not all inclusive and may be changed at any time." That's boilerplate; we can drop. Also there is encouragement to apply etc. That's boilerplate; drop. EEO etc drop. Thus final HTML: sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We need to use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the specifics: e.g., list of onsite locations? That's substantive. Should we include that? It's part of company description; not under a specific heading. Could be placed in About the role? But About the role currently only has the two sentences. We could add a paragraph about company overview under About the role? The instruction: "About the role" heading is for section about the role. The company overview might be considered part of "About the role"? Not sure. The posting includes a paragraph before "About the Role:" that describes company. That is substantive; we should preserve it. Where to put? Could be a preceding

  before any headings, as intro. That's allowed. The instruction says use

  for section headings; we can have plain

  before first heading. So we can keep that company description as a

  before the About the role heading. Similarly, the line "We are a hybrid, remote-office company dedicated to growing our talent anywhere! We have onsite locations in: Sioux Falls, SD, Scottsdale, AZ, Louisville, KY, Troy, MI, Franklin, TN, Easton, PA." That's substantive. Thus we will output:

  We are a hybrid, remote-office company dedicated to growing our talent anywhere! We have onsite locations in: Sioux Falls, SD, Scottsdale, AZ, Louisville, KY, Troy, MI, Franklin, TN, Easton, PA. At Pathward, we take tremendous pride in our purpose to create financial inclusion for all™. We are a financial empowerment company that works with innovators to increase financial availability, choice, and opportunity for all. We strive to remove barriers that traditional institutions put in the way of financial access, and promote economic mobility by providing responsible, secure, high quality financial products. We are a team of problem solvers and innovators who celebrate our differences and know that our unique perspectives make us stronger and well-positioned for success. We celebrate, and embrace, our team members through our *HUMBLE*HUNGRY*SMART approach, and we believe that we are strongest when we embrace the voices of our employees, customers, partners, and the communities we serve.

  Then

  About the role

  with

  Applies knowledge of the technologies in Pathward’s technical stack to develop solutions. Responsible for working as part of a team and is required to perform all duties of software development including design, development, testing, and documentation.

  Then

  Responsibilities

  with
  • ... each duty from "What You Will Do:" list. List items: - Develops flexible, maintainable solutions using the guidelines, requirements and standard practices. - Solves development problems through the use of good design and practical experience. - Reviews, modifies, enhances, and maintains existing systems by fixing issues, remediating security vulnerabilities, and improving system performance. - Participates in planning and user story analysis by providing feedback and demonstrating an understanding of user requirements. - Assists in solving business problems by implementing technical solutions based on solid design principles and best practices. - Actively participates in and follows software development processes and procedures. - Documents software changes, best practices, and standards. - Keeps up to date with current and future changes in tools, technology, programming best practices, and industry standards through training and development opportunities. - Performs other duties as assigned. We should keep each as separate
  • . Then

    Requirements

    with
    • for required items: Bachelor's degree in technical field or equivalent education and work experience required. Typically, 5+ years of experience working in a professional technical environment. 4 years of professional software design and development experience required. Hands-on experience with the Appian low-code platform (application development, process modeling) is required. Experience integrating Appian with external systems and services (APIs, data sources) is required. Effectively work within a team environment. Effective written and oral communication. Ability to teach and mentor other software engineers. Also maybe "Experience with the following technologies is expected, but not all are required: General knowledge of .NET, C#, ASP.NET, MVC, Classic ASP, VB Script, Entity Framework, WPF, JavaScript, IIS, HTML, CSS, XML/XSLT, MSMQ, NServiceBus, Visual Studio, Team Foundation Server, Git, or other source control tools required." This is a required knowledge? It says "Experience with the following technologies is expected, but not all are required:" then list, then "required." Actually the sentence: "Experience with the following technologies is expected, but not all are required: General knowledge of .NET, C#, ASP.NET, MVC, Classic ASP, VB Script, Entity Framework, WPF, JavaScript, IIS, HTML, CSS, XML/XSLT, MSMQ, NServiceBus, Visual Studio, Team Foundation Server, Git, or other source control tools required." It's ambiguous but seems they require general knowledge of those? It says "Experience with the following technologies is expected, but not all are required:" then list, then "required." I'd treat that as a requirement: general knowledge of those technologies is required (though not all needed). We'll include as a requirement item: General knowledge of .NET, C#, ASP.NET, MVC, Classic ASP, VB Script, Entity Framework, WPF, JavaScript, IIS, HTML, CSS, XML/XSLT, MSMQ, NServiceBus, Visual Studio, Team Foundation Server, Git, or other source control tools. Also "Experience with Visual Studio, Azure DevOps, Git, or other source control tools preferred." That's preferred, not required. Thus Requirements section includes the required items. Then

      Qualifications

      for preferred qualifications: General knowledge of Python, YAML, JSON, Azure DevOps, and Git source control is preferred. General knowledge of the software development lifecycle, preferably Agile/Lean or Kanban preferred. Experience with Visual Studio, Azure DevOps, Git, or other source control tools preferred. Cloud development experience with Azure or AWS a plus. Also maybe "Ability to teach and mentor other software engineers" already in requirements; but we can keep. We'll list as
      • . Then

        Skills

        maybe not needed if we already covered technologies in qualifications. But we could separate: The list of technologies under "Experience with the following technologies is expected, but not all are required:" could be considered Skills. However we already put that in Requirements. To avoid duplication, maybe better to put that list under Skills, and keep Requirements focused on education/experience/Appian/integration/team/communication/mentor. Let's decide. We have many items; we need to preserve all substantive info. We can split as: Requirements: education, years experience, Appian hands-on, Appian integration, teamwork, communication, mentoring. Qualifications: preferred knowledge of Python, YAML, JSON, Azure DevOps, Git; SDLC Agile/Lean/Kanban; experience with Visual Studio, Azure DevOps, Git; cloud experience Azure/AWS. Skills: general knowledge of .NET, C#, ASP.NET, MVC, Classic ASP, VB Script, Entity Framework, WPF, JavaScript, IIS, HTML, CSS, XML/XSLT, MSMQ, NServiceBus, Visual Studio, Team Foundation Server, Git, or other source control tools. That seems reasonable and avoids duplication. Now Benefits: