Appian Quality Assurance Tester

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse 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. Could be "About the role". We'll put that as

About the role

then

with that content. - Then "Primary Duties And Responsibilities" heading. We'll treat as Responsibilities section. Provide list of duties. 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. We'll put under

Responsibilities

then

• ... etc. - Then "Required Qualifications" heading. We'll treat as Requirements or Qualifications? The spec says we can have sections: Requirements, Qualifications, Skills. We need to decide mapping. The posting has "Required Qualifications" and "Preferred Qualifications". Also mentions "Strong analytical, troubleshooting, communication, and documentation skills." That's skills. We'll separate. We'll create sections:

  Requirements

  maybe for required qualifications? Or we could put Required Qualifications under Requirements. Then Preferred Qualifications under Qualifications? Or we could combine. The instruction: "Prefer a few substantive sections over many thin ones." So we might combine required and preferred into one Qualifications section? But we need to preserve all info. Could have sections: Requirements (mandatory), Qualifications (preferred), Skills (maybe from required). Let's see. 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. Preferred 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. Skills: The posting includes "Strong analytical, troubleshooting, communication, and documentation skills." Already in required. Could also list other skills like "Ability to work in structured, compliance-driven environments". Might be considered skill. We could create a Skills section pulling out skill-related items: Strong analytical, troubleshooting, communication, and documentation skills; Ability to work in structured, compliance-driven environments; Familiarity with Agile/Scrum; etc. But maybe better to keep Required Qualifications as Requirements, Preferred Qualifications as Qualifications, and Skills as separate if there are distinct skill statements not covered. But we have skill statements already in Required Qualifications. To avoid duplication, we could put them under Skills and keep Requirements for citizenship, clearance, experience, education. However the instruction says preserve ALL substantive information; we can reorganize but must not lose info. It's okay to categorize differently as long as all info appears. Let's design: - About the role (intro + remote location + travel) - Responsibilities (list) - Requirements (mandatory: US Citizenship, DoD Secret clearance ability, 5 years experience, hands-on Appian testing, experience in secure federal cloud environments, Bachelor's degree) - Qualifications (preferred: Appian certification, federal/DoD experience, USCG knowledge, NIST/FedRAMP/DoD/STIG familiarity, API testing tools/experience, active clearance) - Skills (analytical, troubleshooting, communication, documentation; Agile/Scrum familiarity; ability to work in structured compliance-driven environments; etc.) But we need to ensure we don't miss any: Familiarity with Agile/Scrum development methodologies and tools such as Jira, ServiceNow, or Azure DevOps. That could be skill or requirement. We'll put under Skills. Also "Ability to work in structured, compliance-driven environments with strict security and testing protocols." Skill. Now Benefits: The posting ends with "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. No specific salary numbers, but it's a statement about benefits. According to rule: never create Benefits section unless posting actually states them. It does state "generous benefits package". That's substantive enough? It's vague but it's a statement. We'll include Benefits section with that sentence. Pay: The posting does not give specific salary or pay range. It says "competitive salary". That's vague but it's a statement about pay. According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state "competitive salary". That's a statement about pay, albeit not specific. Should we include Pay section? The rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "competitive salary". So we can include Pay section with that sentence. However also note "Prefer a few substantive sections over many thin ones." Might be better to combine Pay and Benefits into one "Compensation and Benefits" but we only have allowed headings: Benefits, Pay, Schedule. We could include both Pay and Benefits sections if they have content. But we might combine into Benefits only and drop Pay because it's not specific. However the rule says we can include Pay if posting states it. It does state "competitive salary". That's a statement. I'd include Pay section with that sentence. Schedule: The posting mentions "Fully remote position available to residents in ... Travel up to 10%". That's about schedule/location/travel. Could be considered Schedule? It mentions remote and travel. Not exactly schedule like hours. But we could treat as Schedule section: remote work, travel up to 10%. However the rule says only create Schedule if posting actually states them. It does state travel up to 10% and remote. So we can include Schedule. But we must avoid filler like "not specified". We have specifics. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Now we need to output HTML fragment only, no /, no markdown. We'll produce:

  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).
  • Bachelor’s degree in Computer Science, Information Systems, Engineering, or related discipline.

  Qualifications

  • Appian Certified Analyst, Designer, or Developer (Associate/Senior