Fastpath Onboarding Manager
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, legal, etc. Also remove navigation, cookie, etc. The posting includes sections: About Delinea (company description) maybe not needed? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we need to map content to those headings. The posting includes "Position Summary" which is about the role. So we can put that under About the role
. Then "Key Responsibilities" -> Responsibilities
. Then "Required Skills And Qualifications" -> could split into Requirements, Qualifications, Skills? The instruction says we can have sections for Requirements, Qualifications, Skills. We need to decide how to split content. The posting lists: Required Skills And Qualifications bullet list includes experience, GRC concepts, familiarity with ERP, project management skills, communication skills, cross-functional, certification plus, bachelor's degree. We could treat that as Requirements (experience) and Qualifications (education/certification) and Skills (specific skills). But we must not create empty sections. We need to include only sections with real specific content. We could combine into one section maybe "Requirements" covering all. But we have to follow instruction: "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 mandatory to include all. We can include only those that have content. So we could include About the role, Responsibilities, Requirements (maybe combine skills and qualifications). But we also have Benefits section: "Why work at Delinea?" includes benefits description. So we can put that under Benefits
. Pay and Schedule: not mentioned, so we omit those sections.
We must not include boilerplate like EEO, legal, etc. Also remove "About Delinea" company description? That is not about the role; but it's substantive info about company. Should we include? The instruction says preserve ALL substantive information; do not invent or summarize away detail. The company description is substantive. However the headings list does not include a company overview heading. Could we include it under About the role? Might be okay to include as part of About the role? But About the role is supposed to be about the role, not company. However we could add a separate heading like "About Delinea" but not in allowed list? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings (e.g.) maybe implying we should use those headings for sections. Safer to stick to those headings only. So we need to fit company description somewhere. Could we put it under About the role as a preamble? Might be okay. The About the role section could include both role summary and company description. But the instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid adding other content under About the role. So we can include company description there.
We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO paragraph, background check, social media review, etc. Also remove "Apply today to help us achieve our mission." maybe considered application instruction; we should remove. Also remove "Learn more about Delinea on Delinea.com, LinkedIn, X, and YouTube." maybe not boilerplate but it's promotional; could keep? It's not about role but maybe okay. However it's not under any heading; we could include under About the role as well.
We need to preserve all substantive information: company description, position summary, responsibilities, required skills/qualifications, benefits description (why work at Delinea). Also core values description maybe part of benefits? It's under "Why work at Delinea?" includes core values and benefits. We'll keep that.
Now produce HTML fragment:
About the role
About the role
. Then "Key Responsibilities" ->Responsibilities
. Then "Required Skills And Qualifications" -> could split into Requirements, Qualifications, Skills? The instruction says we can have sections for Requirements, Qualifications, Skills. We need to decide how to split content. The posting lists: Required Skills And Qualifications bullet list includes experience, GRC concepts, familiarity with ERP, project management skills, communication skills, cross-functional, certification plus, bachelor's degree. We could treat that as Requirements (experience) and Qualifications (education/certification) and Skills (specific skills). But we must not create empty sections. We need to include only sections with real specific content. We could combine into one section maybe "Requirements" covering all. But we have to follow instruction: "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 mandatory to include all. We can include only those that have content. So we could include About the role, Responsibilities, Requirements (maybe combine skills and qualifications). But we also have Benefits section: "Why work at Delinea?" includes benefits description. So we can put that under Benefits
. Pay and Schedule: not mentioned, so we omit those sections.
We must not include boilerplate like EEO, legal, etc. Also remove "About Delinea" company description? That is not about the role; but it's substantive info about company. Should we include? The instruction says preserve ALL substantive information; do not invent or summarize away detail. The company description is substantive. However the headings list does not include a company overview heading. Could we include it under About the role? Might be okay to include as part of About the role? But About the role is supposed to be about the role, not company. However we could add a separate heading like "About Delinea" but not in allowed list? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings (e.g.) maybe implying we should use those headings for sections. Safer to stick to those headings only. So we need to fit company description somewhere. Could we put it under About the role as a preamble? Might be okay. The About the role section could include both role summary and company description. But the instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid adding other content under About the role. So we can include company description there.
We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO paragraph, background check, social media review, etc. Also remove "Apply today to help us achieve our mission." maybe considered application instruction; we should remove. Also remove "Learn more about Delinea on Delinea.com, LinkedIn, X, and YouTube." maybe not boilerplate but it's promotional; could keep? It's not about role but maybe okay. However it's not under any heading; we could include under About the role as well.
We need to preserve all substantive information: company description, position summary, responsibilities, required skills/qualifications, benefits description (why work at Delinea). Also core values description maybe part of benefits? It's under "Why work at Delinea?" includes core values and benefits. We'll keep that.
Now produce HTML fragment:
About the role
About the role
... company description + position summary ...
But we need to avoid too long paragraph; we can split into multiplefor readability. Let's extract company description: "About Delinea Delinea is a pioneer in securing human and machine identities through intelligent, centralized authorization, empowering organizations to seamlessly govern their interactions across the modern enterprise. Leveraging AI-powered intelligence, Delinea’s leading cloud-native Identity Security Platform applies context throughout the entire identity lifecycle – across cloud and traditional infrastructure, data, SaaS applications, and AI. It is the only platform that enables you to discover all identities – including workforce, IT administrator, developers, and machines – assign appropriate access levels, detect irregularities, and respond to threats in real-time. With deployment in weeks, not months, 90% fewer resources to manage than the nearest competitor, and a 99.995% uptime, Delinea delivers robust security and operational efficiency without compromise. Learn more about Delinea on Delinea.com, LinkedIn, X, and YouTube. Join our passionate, global team at Delinea and help us make the world a safer and more secure place. Our success is driven by world-class product leadership, outstanding engineers, and strategic investment from TPG. We value diversity, innovation, and a culture of respect and fairness. If you're ready to push boundaries and challenge the status quo in security, we want to hear from you." We should remove the "Apply today to help us achieve our mission." That's after that paragraph. Also remove the EEO etc later. Now Position Summary: "The Delinea Fastpath Customer Onboarding Manager owns the customer journey immediately following the sale, guiding new Fastpath Assure customers through implementation, configuration, training, and adoption, and ultimately transitioning them into an ongoing Customer Success or account management relationship. This role serves as the primary point of contact for new customers throughout the onboarding and implementation lifecycle, translating each customer's governance, risk, and compliance (GRC) objectives, whether that's segregation of duties (SoD) analysis, access certifications, or IT general controls (ITGC) automation, into a structured onboarding plan. The Onboarding Manager works closely with customers' security, audit, and IT teams to ensure Fastpath Assure is properly configured against their business applications (such as Microsoft Dynamics 365, Oracle, SAP, NetSuite, Sage Intacct, or Workday), that risk rulesets and workflows are tuned to their environment, and that customers are fully trained and confident using the platform to identify conflicts, manage mitigations, and produce audit-ready reporting from day one." We can combine with company description under About the role. Now Responsibilities: list bullet points. We'll convert each line to
- .
Responsibilities list:
- Manage multiple customer onboarding and implementation projects simultaneously, from post-sale handoff through go-live and completion.
- Lead kickoff meetings, recurring customer check-ins, product training sessions, and implementation status calls, covering core Fastpath Assure capabilities including SoD rule configuration, access risk analysis, user access reviews, and audit reporting.
- Develop onboarding plans, timelines, milestones, and success criteria based on each customer's compliance objectives, application landscape, and technical requirements.
- Serve as the primary customer contact, providing clear communication around expectations, deliverables, timelines, risks, and next steps throughout implementation.
- Partner cross-functionally with Sales, Professional Services, Customer Success, Support, Product, and Engineering to ensure smooth handoffs and coordinated delivery.
- Identify implementation risks, roadblocks, and dependencies, including application connectivity, ruleset customization needs, or data access issues, and coordinate resources to keep projects on track.
- Educate customers on Fastpath Assure functionality, workflows, and best practices, including rule configuration, conflict remediation, certification campaigns, and self-service reporting, to accelerate time to value.
- Track onboarding progress, customer engagement, implementation health, and time-to-value metrics across the onboarding portfolio.
- Advocate internally for customer needs, feeding back insights that help improve the product, onboarding processes, documentation, and overall customer experience.
- Continuously evaluate and refine onboarding processes and playbooks to improve efficiency, scalability, customer satisfaction, and successful adoption of Fastpath Assure.
- Facilitate a structured, well-documented transition from onboarding into the customer's long-term Customer Success relationship, ensuring no continuity gaps as the customer matures in their use of the platform.
Now Requirements/Qualifications/Skills: we need to split.
The Required Skills And Qualifications list:
- 3+ years of experience in customer onboarding, implementation, or project management, ideally within a SaaS, security, or compliance software environment.
- Experience with Governance, Risk, and Compliance (GRC) concepts such as segregation of duties (SoD), access certifications, or IT general controls (ITGC) is strongly preferred; direct experience with Fastpath Assure or similar access governance tools (SailPoint, Saviynt, Pathlock, etc.) is a plus.
- Familiarity with common ERP and business applications (Microsoft Dynamics 365, Oracle, SAP, NetSuite, Sage Intacct, Workday) and how access risk is managed within them.
- Strong project management skills, with the ability to manage multiple concurrent onboarding engagements while maintaining clear timelines, milestones, and stakeholder communication.
- Excellent verbal and written communication skills, with the ability to translate technical configuration work into clear business outcomes for both technical and non-technical stakeholders.
- Comfortable working cross-functionally across Sales, Professional Services, Customer Success, Support, Product, and Engineering teams.
- PMP, CAPM, or similar project management certification is a plus but not required.
- Bachelor's degree in Business, Information Systems, Accounting, or a related field, or equivalent practical experience.
We could categorize:
Requirements: experience (3+ years), GRC experience, ERP familiarity, project management skills, communication skills, cross-functional comfort.
Qualifications: education (Bachelor's degree), certification (PMP etc) maybe as qualification.
Skills: maybe the specific skills like project management, communication, cross-functional, etc. But there is overlap.
Given instruction to prefer few substantive sections over many thin ones, we could combine into one section "Requirements" covering all. But we have also "Qualifications" and "Skills" as possible headings. To be safe, we could make two sections: Requirements (experience, GRC, ERP) and Qualifications (education, certification). Skills maybe covered under Requirements. But we need to avoid empty sections. Let's decide:
Section