Appian Quality Assurance Tester

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate like EEO, accessibility, etc. Also remove application instructions, duplicated lines. Must not create sections with filler like "commensurate with experience". So we need to extract content. Let's parse the posting: - Intro: "Atlas Technologies is seeking a skilled and detail-oriented Quality Assurance Tester with experience supporting Appian applications within Appian Government Cloud (AGC) or Appian Defense Cloud (ADC) environments. The selected candidate will support mission-critical Coast Guard applications by performing comprehensive testing, ensuring functional accuracy, and validating compliance with federal security and operational standards. Fully remote position available to residents in AL, CA, CT, FL, GA, KS, KY, LA, ME, MD, MA, NC, OR, RI, SC, TX, VA, DC, WV, NJ. Travel up to 10%" That's about the role. So we can have

About the role

with a paragraph containing that info. - Then "Primary Duties And Responsibilities" heading. Then list of duties. We'll put

Responsibilities

with

• each duty. List items: - Develop detailed test plans, test cases, and test scripts based on Appian requirements, user stories, functional specifications, and security constraints. - Conduct functional, regression, system integration, accessibility, and end-to-end testing for Appian applications deployed in AGC or ADC environments. - Validate Appian objects including interfaces, records, expression rules, process models, data types, document generation, and record security. - Test Appian integrations, APIs, secure authentication flows (SAML, CAC, PKI), and connections to USCG enterprise systems. - Verify compliance with USCG cybersecurity policies, NIST standards, FedRAMP requirements, and DoD IL4/IL5 security guidelines. - Evaluate logging, auditing, escalation paths, and exception-handling workflows for completeness and accuracy. - Identify defects, document issues clearly, and track resolutions through established change management processes. - Participate in User Acceptance Testing (UAT) and work directly with Coast Guard stakeholders to validate requirements and mission workflows. - Participate in Final Acceptance Testing (FAT) and work directly with Coast Guard stakeholders to validate requirements and mission workflows. - Support Agile development activities including daily standups, sprint planning, backlog refinement, and retrospectives. - Monitor regression impacts and recommend improvements to testing coverage within controlled cloud environments. - Ensure all testing results and documentation meet USCG quality assurance, security, and configuration management standards. - Then "Required Qualifications" heading. Then list of required qualifications. List: - U.S. Citizenship - A minimum of a Department of Defense (DoD) Secret level Security Clearance or the ability to obtain and maintain one. - Minimum 5 years of experience in software testing or quality assurance. - Hands-on experience testing Appian applications, including workflows, integrations, and interface components. - Experience supporting applications in secure federal cloud environments (AGC, ADC, FedRAMP, DoD-authorized cloud environments). - Familiarity with Agile/Scrum development methodologies and tools such as Jira, ServiceNow, or Azure DevOps. - Strong analytical, troubleshooting, communication, and documentation skills. - Ability to work in structured, compliance-driven environments with strict security and testing protocols. - Bachelor’s degree in Computer Science, Information Systems, Engineering, or related discipline. - Then "Preferred Qualifications" heading. Then list. List: - Appian Certified Analyst, Designer, or Developer (Associate/Senior). - Experience supporting federal or DoD systems, particularly mission-critical or operational systems. - Knowledge of USCG operational requirements, system environments, or enterprise architecture. - Familiarity with NIST 800-53, FedRAMP, DoD cybersecurity policies, or STIG requirements. - Experience with API testing tools (Postman, SoapUI) or test automation frameworks. - Active Public Trust, Secret, or higher clearance preferred. - Then after that there is a quote section: "Want to hear more? Read on to see what our Team Members say about their experience: ..." That's testimonial, maybe we can include under a section like "About the team" but not in allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put testimonials maybe under About the role? But it's not about role. Could we create a section "About the team"? Not allowed. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid adding other headings not in list? It says: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, but likely they expect only those headings. Safer to stick to those headings. We can incorporate testimonials into About the role paragraph maybe as extra sentence. But that might be stretching. However we must preserve ALL substantive information; we cannot invent or summarize away detail. So we need to keep the testimonials somewhere. If we cannot add a new heading, we could put them in a

  under About the role or maybe under Responsibilities? That would be misrepresenting. Better to add a section like "Team Member Feedback" but that's not in the list. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." implies those are examples, not an exhaustive list. So we can add other headings as needed, as long as we follow the pattern. Probably acceptable. Thus we can add a section

  Team Member Feedback

  with the quotes. Then after that there is EEO boilerplate etc which we must remove. Then there is "Accessibility & Accommodations" etc - remove. Then "Atlas Tech offers a competitive salary, generous benefits package, and an opportunity to make a positive impact in your own community." That's benefits info. So we need a Benefits section with that sentence. Also maybe Pay and Schedule sections: not provided. So we should not create Pay or Schedule sections because no specific content. The posting does not mention pay or schedule specifics. So we omit those. We also have "Skills" section: maybe we can extract skills from required/preferred qualifications? But we already have Requirements and Qualifications sections. The instruction includes Skills as a possible heading. We could put skills like "Strong analytical, troubleshooting, communication, and documentation skills." but that's already in Required Qualifications. Might be redundant. Better to follow the headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. We have Required Qualifications and Preferred Qualifications; we could combine them under Qualifications. Or we could have Requirements (maybe mandatory) and Qualifications (preferred). The list includes both Requirements and Qualifications as separate headings. So we can do: - Requirements: the required qualifications (must-haves) - Qualifications: the preferred qualifications (nice-to-haves) Skills: maybe we can extract skills like "Strong analytical, troubleshooting, communication, and documentation skills." but that's already in Requirements. Could also include "Familiarity with Agile/Scrum development methodologies and tools such as Jira, ServiceNow, or Azure DevOps." That's also a skill. But we might just not include Skills section if content overlaps. However we need to preserve all substantive info; if we omit Skills heading, we still have the content under Requirements/Qualifications. That's fine. Thus final HTML:

  About the role

  Atlas Technologies is seeking a skilled and detail-oriented Quality Assurance Tester with experience supporting Appian applications within Appian Government Cloud (AGC) or Appian Defense Cloud (ADC) environments. The selected candidate will support mission-critical Coast Guard applications by performing comprehensive testing, ensuring functional accuracy, and validating compliance with federal security and operational standards. Fully remote position available to residents in AL, CA, CT, FL, GA, KS, KY, LA, ME, MD, MA, NC, OR, RI, SC, TX, VA, DC, WV, NJ. Travel up to 10%.

  Responsibilities

  • Develop detailed test plans, test cases, and test scripts based on Appian requirements, user stories, functional specifications, and security constraints.
  • Conduct functional, regression, system integration, accessibility, and end-to-end testing for Appian applications deployed in AGC or ADC environments.
  • Validate Appian objects including interfaces, records, expression rules, process models, data types, document generation, and record security.
  • Test Appian integrations, APIs, secure authentication flows (SAML, CAC, PKI), and connections to USCG enterprise systems.
  • Verify compliance with USCG cybersecurity policies, NIST standards, FedRAMP requirements, and DoD IL4/IL5 security guidelines.
  • Evaluate logging, auditing, escalation paths, and exception-handling workflows for completeness and accuracy.
  • Identify defects, document issues clearly, and track resolutions through established change management processes.
  • Participate in User Acceptance Testing (UAT) and work directly with Coast Guard stakeholders to validate requirements and mission workflows.
  • Participate in Final Acceptance Testing (FAT) and work directly with Coast Guard stakeholders to validate requirements and mission workflows.
  • Support Agile development activities including daily standups, sprint planning, backlog refinement, and retrospectives.
  • Monitor regression impacts and recommend improvements to testing coverage within controlled cloud environments.
  • Ensure all testing results and documentation meet USCG quality assurance, security, and configuration management standards.

  Requirements

  • U.S. Citizenship
  • A minimum of a Department of Defense (DoD) Secret level Security Clearance or the ability to obtain and maintain one.
  • Minimum 5 years of experience in software testing or quality assurance.
  • Hands-on experience testing Appian applications, including workflows, integrations, and interface components.
  • Experience supporting applications in secure federal cloud environments (AGC, ADC, FedRAMP, DoD-authorized cloud environments).
  • Familiarity with Agile/Scrum development methodologies and tools such as Jira, ServiceNow, or Azure DevOps.
  • Strong analytical, troubleshooting, communication, and documentation skills.
  • Ability to work in structured, compliance-driven environments with strict security and testing protocols.
  • Bachelor’s degree in Computer Science, Information Systems, Engineering, or related discipline.

  Qualifications

  • Appian Certified Analyst, Designer, or Developer (Associate/Senior).
  • Experience supporting federal or DoD systems, particularly mission-critical or operational systems.
  • Knowledge of USCG operational requirements, system environments, or enterprise architecture.
  • Familiarity with NIST 800-53, FedRAMP, DoD cybersecurity policies, or STIG requirements.
  • Experience with API testing tools (Postman, SoapUI) or test automation frameworks.
  • Active Public Trust, Secret, or higher clearance preferred.

  Team Member Feedback

  “Atlas Tech has the culture, trust, and fairness that you expect of the best of communities. I feel lucky to