Senior Appian Developer

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. Remove boilerplate: EEO, equal opportunity, scam warning, navigation, cookie, legal, application instructions. Also remove duplicated lines. Keep substantive info. We need to parse posting. Content: - Intro: "Atlas Technologies is seeking a skilled and motivated Senior Appian Developer to join our dynamic IT team and contribute to the design, development, and implementation of secure enterprise applications and process automation solutions. The ideal candidate is a strong Appian developer who understands application architecture, security, integrations and the full software development lifecycle. Experience integrating with enterprise systems such as PeopleSoft ERP or Oracle is a plus. 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" heading. - Key Responsibilities: list bullet points. - Then "You have Appian Expertise: ..." etc. That's requirements/qualifications/skills. We need to decide sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have info about benefits: "Atlas Tech offers a competitive salary, generous benefits package, and an opportunity to make a positive impact in your own community." That's benefits (competitive salary, generous benefits). No specifics like health, 401k. But it's still benefits content. Should we include Benefits section? Yes, we have real content: competitive salary, generous benefits package, opportunity to make positive impact. That's substantive enough. Pay: Not specified exact salary, just "competitive salary". That is vague but still mentions salary. The rule: do NOT include Pay section unless posting actually states them. It states "competitive salary". That's a statement about pay, albeit not numeric. Is that enough? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive salary, which is about pay. So we could include Pay section with that sentence. However they also said "Prefer a few substantive sections over many thin ones." Might combine Pay into Benefits? But they are separate headings allowed. Could we omit Pay because it's not specific? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive salary, which is a statement about pay. So we can include Pay. But we must avoid filler like "commensurate with experience". "competitive salary" is not filler? It's somewhat generic but still states something. I'd include Pay. Schedule: Not mentioned besides remote and travel up to 10%. No schedule like full-time, hours. Not stated. So we should not create Schedule section. Qualifications: We have "U.S. Citizenship A minimum of a Department of Defense (DoD) Secret level Security Clearance or the ability to obtain and maintain one. Security+ CE Certification (or equivalent DoD 8570 baseline certification) Bachelor’s degree in computer science, Information Technology, or equivalent experience Certifications: Appian Certified Senior Developer (ACD-201) or Lead Developer is highly preferred." That's qualifications. Skills: Could be separate: Appian Expertise, Database Proficiency, Web Services, etc. Might be better to put under Skills. But we also have Requirements. Could combine Requirements and Qualifications? The instruction: we can have multiple sections but prefer few substantive sections. We could have About the role, Responsibilities, Qualifications (including requirements/skills), Benefits, Pay. That's 5 sections. But we need to follow headings list: we can use any of those headings. We'll use About the role, Responsibilities, Qualifications, Benefits, Pay. We must not repeat job title as heading. Good. We need to use

• for any list of duties/requirements/benefits. For prose use

  . We need to preserve all substantive information; do not invent or summarize away detail. Let's extract details. About the role paragraph: combine first sentences plus remote location and travel. "Atlas Technologies is seeking a skilled and motivated Senior Appian Developer to join our dynamic IT team and contribute to the design, development, and implementation of secure enterprise applications and process automation solutions. The ideal candidate is a strong Appian developer who understands application architecture, security, integrations and the full software development lifecycle. Experience integrating with enterprise systems such as PeopleSoft ERP or Oracle is a plus. 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. Responsibilities: list bullet points: - Interface Design: Build intuitive SAIL forms and dashboards that aggregate data from multiple systems for a unified user experience. - Data Modeling: Design and maintain Custom Data Types (CDTs) and Record Types that support business applications and integrations. - Workflow Automation: Develop end-to-end process models that automate business processes, approvals, notifications and case management. - Integration Architecture: Design and configure Connected Systems and Integration Objects to integrate Appian with enterprise systems using REST/SOAP APIs. - API Development: Develop Appian integrations and Web APIs to securely exchange data with internal and external systems. - Security & Authentication: Implement secure handshakes between systems using OAuth 2.0, SAML, or certificate-based authentication. We need to keep as list items. Qualifications: combine the bullet-like statements. We have: - U.S. Citizenship - A minimum of a Department of Defense (DoD) Secret level Security Clearance or the ability to obtain and maintain one. - Security+ CE Certification (or equivalent DoD 8570 baseline certification) - Bachelor’s degree in computer science, Information Technology, or equivalent experience - Certifications: Appian Certified Senior Developer (ACD-201) or Lead Developer is highly preferred. - Preferred Qualifications (list): - Experience with Appian Data Fabric for unifying disparate data sources. - Background in Java or JavaScript for developing custom plugins if standard connectors are insufficient. - PeopleSoft Familiarity: Understanding of PeopleSoft Integration Broker, Component Interfaces, and the ability to work with PeopleSoft technical teams to define service requirements. - Experience working in a Center of Excellence (COE) or an Agile/DevOps environment - Attention to detail with a focus on delivering secure, high-quality solutions We need to keep all. Could separate Required vs Preferred but we can just list all as qualifications. Benefits: "Atlas Tech offers a competitive salary, generous benefits package, and an opportunity to make a positive impact in your own community." Pay: maybe we separate salary? But we already have competitive salary in benefits. Could combine? But we need Pay section if we want. However we might avoid duplication. Since benefits already mentions competitive salary, we could omit Pay section to avoid thin section. The rule: prefer few substantive sections over many thin ones. So we can omit Pay and keep Benefits with that sentence. Thus sections: About the role, Responsibilities, Qualifications, Benefits. Check if any other info: "Want to hear more? Read on to see what our Team Members say about their experience:" then quotes. That's testimonials; could be considered substantive? It's about team members say. Might be considered fluff but it's substantive content (quotes). Should we include? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should include the quotes. Where to put? Could be under a section like "Team Member Testimonials" but not in allowed headings list. We could maybe put under About the role as a paragraph? But it's not about role. Could create a section "Team Member Feedback" but not in allowed headings list. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning those are examples, not exclusive? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not add other headings. We could incorporate the quotes into About the role as a paragraph? Might be okay but it's not about role. Could put under Benefits? Not really. Could put under Qualifications? Not. Maybe we can omit the testimonials as they are not essential to job description? But instruction says preserve ALL substantive information. The quotes are substantive (they convey culture). However they might be considered boilerplate? Not exactly. They are employee testimonials. Might be considered part of company culture description. Could be placed under About the role as additional info about team. I'd include them as a paragraph under About the role after the initial description. Thus About the role paragraph will include the intro and then the quotes. Let's craft HTML. We'll output:

  About the role

  Atlas Technologies is seeking a skilled and motivated Senior Appian Developer to join our dynamic IT team and contribute to the design, development, and implementation of secure enterprise applications and process automation solutions. The ideal candidate is a strong Appian developer who understands application architecture, security, integrations and the full software development lifecycle. Experience integrating with enterprise systems such as PeopleSoft ERP or Oracle is a plus. 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%. “Atlas Tech has the culture, trust, and fairness that you expect of the best of communities. I feel lucky to be part of their amazing journey of growth as a standout organization.” - Syed “You are not just a number here at Atlas. I have been with Atlas for over 13 years now I can say that Atlas displays a genuine interest in its employees. This is evidenced in its commitment to mentoring every employee and providing educational paths for each employee’s personal and professional growth within the company.” - Ian

  Responsibilities

  • Interface Design: Build intuitive SAIL forms and dashboards that aggregate data from multiple systems for a unified user experience.
  • Data Modeling: Design and maintain Custom Data Types (CDTs) and Record Types that support business applications and integrations.
  • Workflow Automation: Develop end-to-end process models that automate business processes, approvals, notifications and case management.
  • Integration Architecture: Design and configure Connected Systems and Integration Objects to integrate Appian with enterprise systems using REST/SOAP APIs.
  • API Development: Develop Appian integrations and Web APIs to securely exchange data with internal and external systems.
  • Security & Authentication: Implement secure handshakes between systems using OAuth 2.0, SAML, or certificate-based authentication.

  Qualifications

  • U.S. Citizenship
  • A minimum of a Department of Defense (DoD) Secret level Security Clearance or the ability to obtain and maintain one.
  • Security+ CE Certification (or equivalent DoD 8570 baseline certification)
  • Bachelor’s degree in computer science, Information Technology, or equivalent experience
  • Certifications: Appian Certified Senior Developer (ACD-201) or Lead Developer is highly preferred.
  • Experience with Appian Data Fabric for unifying disparate data sources.
  • Background in Java or JavaScript for developing custom plugins if standard connectors are insufficient.
  • PeopleSoft Familiarity: Understanding of PeopleSoft Integration Broker, Component Interfaces,