Senior Advisory Solutions Consultant
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info; remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it — never emit heading followed by filler/placeholder text like "commensurate with experience", etc. Never create Pay/Schedule/Benefits sections unless posting actually states them.
We need to extract sections: About the Team, The Opportunity, What You’ll Do (Responsibilities), Required Qualifications, Preferred Qualifications, Base Salary Range (Pay), Benefits (Benefits), Tools and Resources Training and Development (maybe Skills? but it's more about growth opportunities). Also Community, About Appian maybe not needed? The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content to those headings.
We have:
- About the Team (could be "About the role"? Actually "About the Team" maybe similar to About the role. We'll use
About the Team
with paragraph.
- The Opportunity (maybe also part of About the role). Could be under About the role as well. But we can keep as separate? The instruction says prefer a few substantive sections over many thin ones. So maybe combine About the Team and The Opportunity into About the role? But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have Responsibilities: "What You’ll Do" bullet list.
We have Requirements: maybe "Required Qualifications" (education, experience, technical depth, communication & leadership, travel). That's Requirements.
We have Qualifications: maybe "Preferred Qualifications". That's Qualifications.
We have Skills: maybe "Technical Depth" etc but that's part of Required Qualifications. Could also include "Tools and Resources Training and Development" as Skills? But maybe we can treat "Tools and Resources Training and Development" as Skills? However the instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include Skills if we have content. We have "Tools and Resources Training and Development: During onboarding..." plus "Growth Opportunities..." plus "Community". Those could be under Skills or maybe under Benefits? Actually they are about development opportunities, not benefits. Could be Skills? Might be better to put under "Skills" heading: list of training, mentorship, growth opportunities, community.
But we also have Benefits section: we have benefits paragraph.
Pay: Base Salary Range.
Schedule: Not mentioned explicitly; there is location remote vs on-site note: "Location: Remote | Work Model: Remote, Field Role Note: In accordance with Appian's McLean headquarters policy for this search profile, this position is full-time on-site." That's contradictory but indicates schedule: full-time on-site. Could be considered Schedule? The instruction: include Schedule section only if posting actually states them. It does mention work model and location, but not explicit schedule like hours. Might be considered Schedule? Probably not; we can omit Schedule if no explicit schedule.
We must not include filler like "commensurate with experience". Not present.
We need to remove boilerplate: EEO, equal opportunity, accommodation, privacy notice, etc. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. Also remove "#SaaS #PreSales #SolutionsConsultant #PublicSectorTech #EnterpriseSoftware" maybe considered boilerplate? It's tags; could be removed as not substantive. Also remove "Follow Appian: LinkedIn, Youtube, Instagram, Facebook". Also remove "About Appian" maybe? It's somewhat substantive but could be considered boilerplate? It describes company; maybe keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Appian" is not those; it's company description. Could keep as part of About the role? But we already have About the Team and The Opportunity. Might be redundant. Could keep as a brief paragraph under About the role. However we need to avoid duplication.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from sections: About the Team, The Opportunity, What You’ll Do (list), Required Qualifications (list), Preferred Qualifications (list), Base Salary Range, Benefits (list), Tools and Resources Training and Development (list), Growth Opportunities (list), Community (list). Also maybe note about location and work model? Could be included under About the role? Might be considered Schedule? Not sure.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the Team
... (combined About the Team and The Opportunity maybe)
But we need to keep details: About the Team paragraph, The Opportunity paragraph. Could combine into one with both sentences.
Then Responsibilities:
Responsibilities
- ... each bullet.
Then Requirements:
Requirements
- ... each bullet from Required Qualifications.
Then Qualifications:
Qualifications
- ... each bullet from Preferred Qualifications.
Then Skills:
Skills
maybe include Tools and Resources Training and Development, Growth Opportunities, Community. Could be list.
Then Benefits: Benefits
- ... each benefit.
Then Pay:
Pay
Base Salary Range: $152,000 USD - $237,500 USD
We should not include Schedule.
We must ensure we don't create empty sections.
Now extract details precisely.
About the Team paragraph:
"Here at Appian, our values of Intensity and Excellence define who we are. We set high standards and live up to them, ensuring that everything we do is done with care and quality. We approach every challenge with ambition and commitment, holding ourselves and each other accountable to achieve the best results. When you join Appian, you’ll be part of a passionate team dedicated to accomplishing hard things, together."
The Solutions Consulting organization at Appian sits at the vital center of our global commercial engine, bridging the gap between sophisticated enterprise business needs and cutting-edge platform capabilities to secure the technical win. Our mission is to prove the undeniable value of Appian’s platform within the AI-Powered Process Automation market, driving customer acquisition and fueling corporate growth. Under our SC 2.0 operating model, our consultants don't just demo features—they tell compelling stories, co-create solutions with customers, and help shape strategy with technical credibility and business insight."
The Opportunity paragraph:
"Ready to take your career to the next level alongside the smartest, most creative people in the tech industry? As a Senior Advisory Solutions Consultant, you will step into a highly visible, strategic role serving as the trusted advisor for federal agencies, partners, sales leadership, and product teams. This is a game-changing opportunity to own account strategy and technical orchestration for strategic opportunities, translating intricate agency requirements directly into groundbreaking technical solutions that fuel our next stage of hyper-growth within our Enterprise-Grade Orchestration ecosystem."
We can combine these into About the Team section? Actually About the Team heading maybe should contain the first two paragraphs (About the Team and The Opportunity). We'll put them in maybe two paragraphs.
Now Responsibilities (What You’ll Do) list:
- Own Account Strategy: Own the technical strategy for strategic accounts and complex sales campaigns, acting as a true co-seller with Account Executives sharing accountability for pipeline health and revenue contribution.
- Facilitate Executive Workshops: Lead customer roadmap sessions, transformation workshops, and executive visioning discussions to connect customer objectives to Appian capabilities.
- Architect Custom Solutions: Lead the scoping, design, and delivery of high-quality, custom technical Proof of Concepts (POCs) and Proof of Values (POVs) with executive sponsorship and clear success criteria.
- Navigate Complex Landscapes: Understand customer IT landscapes including ERP, CRM, data, workflow, AI, partner solutions, and modern web or enterprise development systems to integrate Appian into complex enterprise environments.
- Own Technical Validation: Direct the technical response and functional strategy required to respond to complex functional and technical elements of RFIs, RFPs, security reviews, and architecture discussions.
- Influence Product Roadmap: Convey real-world customer requirements directly to core Product Management teams, actively serving as a vital feedback loop to influence Appian's long-term product roadmap.
- Scale & Mentor: Coach peers, lead field enablement sessions, and contribute strategic reusable assets, blueprints, and customer success stories to scale best practices.
Now Required Qualifications list:
- Education: Minimum of a Bachelor’s or Master’s degree in Computer Science, Engineering, Information Systems, Information Technology, Business Information Technology, or a related technical or business field.
- Experience: 8+ years of successful experience as a Pre-Sales Engineer, Solutions Consultant, or related enterprise software pre-sales professional, OR 10+ years in a client-facing Professional Services or technical consulting role heavily involved in enterprise sales scenarios.
- Technical Depth: Recent hands-on programming experience or technical fluency within modern development environments using languages such as Java, JavaScript, Python, C#, or C++, alongside database proficiency (SQL, HTML, XML).
- Communication & Leadership: Exceptional communication and influencing skills with a proven ability to conduct deep discovery, analyze requirements, present to executives, and engage C-level audiences.
- Travel: Willingness to travel up to 50% to customer locations throughout the assigned region.
Now Preferred Qualifications list:
- Prior experience selling into the Federal or Public Sector landscape with an emphasis on Application Development Platforms, AI-enabled automation, or Case Management frameworks.
- Experience contributing reusable demos, technical assets, enablement content, or industry points of view.
- We value experience with enterprise platforms such as Salesforce or ServiceNow, as these skills translate well into our Enterprise-Grade Orchestration environment.
Now Skills section: Tools and Resources Training and Development, Growth Opportunities, Community.
Tools and Resources Training and Development paragraph:
"Tools and Resources Training and Development: During onboarding, we focus on equipping new hires with the skills and knowledge for success through department-specific training. Continuous learning is a central focus at Appian, with dedicated mentorship and the First-Friend program being widely utilized resources for new hires."
Growth Opportunities paragraph:
"Growth Opportunities: Appian provides a diverse array of growth and development opportunities, including our leadership program tailored for new and aspiring managers, a comprehensive library of specialized department training through Appian University, skills based training, and tuition reimbursement for those aiming to advance their education. This commitment ensures that employees have access to a holistic range of development opportunities."
Community paragraph:
"Community: We’ll immerse you into our community rooted in respect starting on day one. Appian fosters inclusivity through our 8 employee-led affinity groups. These groups help employees build stronger internal and external networks by planning social, educational, and outreach activities to connect with Appianites and larger initiatives throughout the company."
We could turn each into list items under Skills.
Now Benefits list:
From Benefits paragraph: "Appian offers a comprehensive benefits package designed to support your health, wellbeing, and financial future. Benefits may include health coverage, Employee Assistance Program (EAP) with free mental health support, life and disability insurance, an Employee Stock Purchase Program (ESPP), a retirement/pension plan, wellness dollars, tuition reimbursement, family-forming benefits and more. Benefits vary by country—please
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info; remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it — never emit heading followed by filler/placeholder text like "commensurate with experience", etc. Never create Pay/Schedule/Benefits sections unless posting actually states them. We need to extract sections: About the Team, The Opportunity, What You’ll Do (Responsibilities), Required Qualifications, Preferred Qualifications, Base Salary Range (Pay), Benefits (Benefits), Tools and Resources Training and Development (maybe Skills? but it's more about growth opportunities). Also Community, About Appian maybe not needed? The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content to those headings. We have: - About the Team (could be "About the role"? Actually "About the Team" maybe similar to About the role. We'll use
About the Team
with paragraph. - The Opportunity (maybe also part of About the role). Could be under About the role as well. But we can keep as separate? The instruction says prefer a few substantive sections over many thin ones. So maybe combine About the Team and The Opportunity into About the role? But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Responsibilities: "What You’ll Do" bullet list. We have Requirements: maybe "Required Qualifications" (education, experience, technical depth, communication & leadership, travel). That's Requirements. We have Qualifications: maybe "Preferred Qualifications". That's Qualifications. We have Skills: maybe "Technical Depth" etc but that's part of Required Qualifications. Could also include "Tools and Resources Training and Development" as Skills? But maybe we can treat "Tools and Resources Training and Development" as Skills? However the instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include Skills if we have content. We have "Tools and Resources Training and Development: During onboarding..." plus "Growth Opportunities..." plus "Community". Those could be under Skills or maybe under Benefits? Actually they are about development opportunities, not benefits. Could be Skills? Might be better to put under "Skills" heading: list of training, mentorship, growth opportunities, community. But we also have Benefits section: we have benefits paragraph. Pay: Base Salary Range. Schedule: Not mentioned explicitly; there is location remote vs on-site note: "Location: Remote | Work Model: Remote, Field Role Note: In accordance with Appian's McLean headquarters policy for this search profile, this position is full-time on-site." That's contradictory but indicates schedule: full-time on-site. Could be considered Schedule? The instruction: include Schedule section only if posting actually states them. It does mention work model and location, but not explicit schedule like hours. Might be considered Schedule? Probably not; we can omit Schedule if no explicit schedule. We must not include filler like "commensurate with experience". Not present. We need to remove boilerplate: EEO, equal opportunity, accommodation, privacy notice, etc. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. Also remove "#SaaS #PreSales #SolutionsConsultant #PublicSectorTech #EnterpriseSoftware" maybe considered boilerplate? It's tags; could be removed as not substantive. Also remove "Follow Appian: LinkedIn, Youtube, Instagram, Facebook". Also remove "About Appian" maybe? It's somewhat substantive but could be considered boilerplate? It describes company; maybe keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Appian" is not those; it's company description. Could keep as part of About the role? But we already have About the Team and The Opportunity. Might be redundant. Could keep as a brief paragraph under About the role. However we need to avoid duplication. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from sections: About the Team, The Opportunity, What You’ll Do (list), Required Qualifications (list), Preferred Qualifications (list), Base Salary Range, Benefits (list), Tools and Resources Training and Development (list), Growth Opportunities (list), Community (list). Also maybe note about location and work model? Could be included under About the role? Might be considered Schedule? Not sure. We need to output only HTML fragment, no /, no markdown fences. We'll structure:About the Team
... (combined About the Team and The Opportunity maybe)
But we need to keep details: About the Team paragraph, The Opportunity paragraph. Could combine into onewith both sentences. Then Responsibilities:
Responsibilities
- ... each bullet.
Then Requirements:
Requirements
- ... each bullet from Required Qualifications.
Then Qualifications:
Qualifications
- ... each bullet from Preferred Qualifications.
Then Skills:
Skills
maybe include Tools and Resources Training and Development, Growth Opportunities, Community. Could be list. Then Benefits:Benefits
- ... each benefit.
Then Pay:
Pay
Base Salary Range: $152,000 USD - $237,500 USD
We should not include Schedule. We must ensure we don't create empty sections. Now extract details precisely. About the Team paragraph: "Here at Appian, our values of Intensity and Excellence define who we are. We set high standards and live up to them, ensuring that everything we do is done with care and quality. We approach every challenge with ambition and commitment, holding ourselves and each other accountable to achieve the best results. When you join Appian, you’ll be part of a passionate team dedicated to accomplishing hard things, together." The Solutions Consulting organization at Appian sits at the vital center of our global commercial engine, bridging the gap between sophisticated enterprise business needs and cutting-edge platform capabilities to secure the technical win. Our mission is to prove the undeniable value of Appian’s platform within the AI-Powered Process Automation market, driving customer acquisition and fueling corporate growth. Under our SC 2.0 operating model, our consultants don't just demo features—they tell compelling stories, co-create solutions with customers, and help shape strategy with technical credibility and business insight." The Opportunity paragraph: "Ready to take your career to the next level alongside the smartest, most creative people in the tech industry? As a Senior Advisory Solutions Consultant, you will step into a highly visible, strategic role serving as the trusted advisor for federal agencies, partners, sales leadership, and product teams. This is a game-changing opportunity to own account strategy and technical orchestration for strategic opportunities, translating intricate agency requirements directly into groundbreaking technical solutions that fuel our next stage of hyper-growth within our Enterprise-Grade Orchestration ecosystem." We can combine these into About the Team section? Actually About the Team heading maybe should contain the first two paragraphs (About the Team and The Opportunity). We'll put them inmaybe two paragraphs. Now Responsibilities (What You’ll Do) list: - Own Account Strategy: Own the technical strategy for strategic accounts and complex sales campaigns, acting as a true co-seller with Account Executives sharing accountability for pipeline health and revenue contribution. - Facilitate Executive Workshops: Lead customer roadmap sessions, transformation workshops, and executive visioning discussions to connect customer objectives to Appian capabilities. - Architect Custom Solutions: Lead the scoping, design, and delivery of high-quality, custom technical Proof of Concepts (POCs) and Proof of Values (POVs) with executive sponsorship and clear success criteria. - Navigate Complex Landscapes: Understand customer IT landscapes including ERP, CRM, data, workflow, AI, partner solutions, and modern web or enterprise development systems to integrate Appian into complex enterprise environments. - Own Technical Validation: Direct the technical response and functional strategy required to respond to complex functional and technical elements of RFIs, RFPs, security reviews, and architecture discussions. - Influence Product Roadmap: Convey real-world customer requirements directly to core Product Management teams, actively serving as a vital feedback loop to influence Appian's long-term product roadmap. - Scale & Mentor: Coach peers, lead field enablement sessions, and contribute strategic reusable assets, blueprints, and customer success stories to scale best practices. Now Required Qualifications list: - Education: Minimum of a Bachelor’s or Master’s degree in Computer Science, Engineering, Information Systems, Information Technology, Business Information Technology, or a related technical or business field. - Experience: 8+ years of successful experience as a Pre-Sales Engineer, Solutions Consultant, or related enterprise software pre-sales professional, OR 10+ years in a client-facing Professional Services or technical consulting role heavily involved in enterprise sales scenarios. - Technical Depth: Recent hands-on programming experience or technical fluency within modern development environments using languages such as Java, JavaScript, Python, C#, or C++, alongside database proficiency (SQL, HTML, XML). - Communication & Leadership: Exceptional communication and influencing skills with a proven ability to conduct deep discovery, analyze requirements, present to executives, and engage C-level audiences. - Travel: Willingness to travel up to 50% to customer locations throughout the assigned region. Now Preferred Qualifications list: - Prior experience selling into the Federal or Public Sector landscape with an emphasis on Application Development Platforms, AI-enabled automation, or Case Management frameworks. - Experience contributing reusable demos, technical assets, enablement content, or industry points of view. - We value experience with enterprise platforms such as Salesforce or ServiceNow, as these skills translate well into our Enterprise-Grade Orchestration environment. Now Skills section: Tools and Resources Training and Development, Growth Opportunities, Community. Tools and Resources Training and Development paragraph: "Tools and Resources Training and Development: During onboarding, we focus on equipping new hires with the skills and knowledge for success through department-specific training. Continuous learning is a central focus at Appian, with dedicated mentorship and the First-Friend program being widely utilized resources for new hires." Growth Opportunities paragraph: "Growth Opportunities: Appian provides a diverse array of growth and development opportunities, including our leadership program tailored for new and aspiring managers, a comprehensive library of specialized department training through Appian University, skills based training, and tuition reimbursement for those aiming to advance their education. This commitment ensures that employees have access to a holistic range of development opportunities." Community paragraph: "Community: We’ll immerse you into our community rooted in respect starting on day one. Appian fosters inclusivity through our 8 employee-led affinity groups. These groups help employees build stronger internal and external networks by planning social, educational, and outreach activities to connect with Appianites and larger initiatives throughout the company." We could turn each into list items under Skills. Now Benefits list: From Benefits paragraph: "Appian offers a comprehensive benefits package designed to support your health, wellbeing, and financial future. Benefits may include health coverage, Employee Assistance Program (EAP) with free mental health support, life and disability insurance, an Employee Stock Purchase Program (ESPP), a retirement/pension plan, wellness dollars, tuition reimbursement, family-forming benefits and more. Benefits vary by country—please
- ... each benefit.
Then Pay:
- ... each bullet from Preferred Qualifications.
Then Skills:
- ... each bullet from Required Qualifications.
Then Qualifications: