Jobs · Marketing · Arizona

Product Consultant - AZ - On Site

PrismHR · Chandler, AZ · 1 mo ago
MarketingFull-time
We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes: About Us (company description) but not "About the role". There's a Position Summary, Essential Duties And Responsibilities, Knowledge, Skills, and Abilities, Required Education & Experience, Physical, Mental, & Communication Demands, Environmental Conditions, Benefits section. Also there is mention of travel up to 25% (Schedule? maybe schedule not given). No explicit Pay or Schedule details. So we should not create Pay or Schedule sections because no specific content. Benefits section is present with details. We could have sections: About the role? Could use Position Summary as About the role. Responsibilities: Essential Duties And Responsibilities. Requirements: maybe Required Education & Experience plus Knowledge, Skills, and Abilities? But we need separate sections: Requirements, Qualifications, Skills. The posting has Knowledge, Skills, and Abilities (which could be Skills). Required Education & Experience could be Qualifications. We could also have a Requirements section for knowledge of PEO etc. But we must not create thin sections; we need substantive content. Let's map: - About the role: Position Summary paragraph. - Responsibilities: Essential Duties And Responsibilities (list of duties). - Qualifications: Required Education & Experience (including experience, education, etc.) - Skills: Knowledge, Skills, and Abilities (list). - Benefits: Benefits section. We should not include Physical, Mental, & Communication Demands, Environmental Conditions as they are not requested headings; we could omit or maybe include under a generic section? The instruction says use headings for those specific section names; we should not create other headings. So we omit those. We must preserve all substantive information; we need to include the content from those sections. For omitted sections like Physical Demands etc., we need to still include that information somewhere? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we omit a heading, we must still include that info somewhere else, maybe within existing sections? But we cannot add new headings not listed. Could we incorporate that info into existing sections like Responsibilities or Skills? That would be altering meaning but maybe acceptable if we keep the info. However the instruction says "Prefer a few substantive sections over many thin ones." It doesn't forbid adding other headings not listed, but says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive list? It says use

for section headings (e.g. ...). Likely they expect only those headings. So we need to fit all info into those sections. We can incorporate Physical Demands etc. into Responsibilities or Skills? Might be okay but could be seen as summarizing away detail. Better to create a section like "Working Conditions" but not allowed. Could we put them under Responsibilities as additional bullet? That would preserve detail but change semantics. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." Adding them under Responsibilities is not inventing or summarizing; it's just placing them elsewhere. Might be acceptable. But we also have "Environmental Conditions" etc. Could be placed under Responsibilities as bullet points. Alternatively, we could create a section named "Requirements" and include both Required Education & Experience and Physical/Mental/Communication Demands there. But Requirements heading is allowed. Qualifications also allowed. Skills allowed. We need to decide mapping: - About the role: Position Summary. - Responsibilities: Essential Duties And Responsibilities. - Requirements: Required Education & Experience (maybe also include Knowledge, Skills, and Abilities? but that's more Skills). - Qualifications: maybe combine Knowledge, Skills, and Abilities? Actually Qualifications often includes education/experience; Skills separate. But we have both. Let's assign: - About the role: Position Summary. - Responsibilities: Essential Duties And Responsibilities. - Requirements: Required Education & Experience (experience, education, certifications). - Skills: Knowledge, Skills, and Abilities (list). - Benefits: Benefits section. We need to also include Physical, Mental, & Communication Demands and Environmental Conditions somewhere. Could we add them under Responsibilities as additional bullet points? That would be mixing duties with demands, but still preserving info. Might be okay. Alternatively, we could add a section "Working Conditions" but not allowed. So we will incorporate them into Responsibilities. We must not include boilerplate like EEO, diversity, privacy policy, accommodation, etc. Remove those. We must not repeat job title as heading. No Job ID. We must output only HTML fragment. Let's extract content. About Us: company description. Not needed for role? Could be part of About the role? Might be considered company overview but not role. The instruction: "About the role" heading for section headings. The About Us is not about the role. Could we include it under About the role? It's about company, not role. Might be considered not specific to role. But we need to preserve all substantive information; if we omit About Us, we lose company description. However maybe it's not essential for the role posting; but instruction says preserve ALL substantive information. So we need to include it somewhere. Could we put it under About the role as a preamble? Might be okay. Better: Include About Us as a paragraph under About the role heading (since it's about the company, but still relevant). Or we could treat it as part of About the role. Let's parse the sections: - About Us PrismHR is the leading payroll... (company description) - Position Summary The Product Consultant serves as a trusted advisor... - Essential Duties And Responsibilities (list bullet points) - Knowledge, Skills, and Abilities (list) - Required Education & Experience (list) - Physical, Mental, & Communication Demands (list) - Environmental Conditions (paragraph) - This Position Is Eligible For The Following Benefits (list) - PrismHR is a fast-paced SaaS company... (additional company description) - Diversity, Equity And Inclusion Program/Affirmative Action Plan (EEO boilerplate) - remove. - Privacy Policy etc - remove. - Accommodation contact - remove. We need to keep the company description paragraphs (About Us and the later PrismHR is a fast-paced SaaS company...). Both are substantive about company. We'll include them under About the role maybe as two paragraphs. Now we need to format lists as
  • . For responsibilities, we have bullet points starting with "Own the customer relationship..." etc. We'll turn each into
  • . For Knowledge, Skills, and Abilities: each line is a bullet? It's a paragraph with sentences separated by periods. We'll split into separate
  • items for each ability? The instruction: Use
    • for any list of duties/requirements/benefits. So we need to treat them as list items. We'll break each distinct statement. Similarly for Required Education & Experience: bullet points. For Benefits: list. We must not include headings with empty content. Now craft HTML. We'll start with

      About the role

      then

      About Us paragraph...

      then

      Position Summary paragraph...

      then maybe also include the later PrismHR SaaS description as another

      . Then

      Responsibilities

      • ... each duty
      Then

      Requirements

      • ... each requirement from Required Education & Experience
      Then

      Skills

      • ... each from Knowledge, Skills, and Abilities
      Then

      Benefits

      • ... each benefit
      We need to ensure we don't include Pay or Schedule sections. Now extract details. About Us paragraph: "PrismHR is the leading payroll, benefits, and HR software for Human Resource Outsourcing (HRO) organizations, including Professional Employer Organizations (PEOs) and Administrative Service Organizations (ASOs). Powering more than 80,000+ companies, 2.5 million worksite employees, and $85 billion in payroll processed annually, PrismHR is the most efficient, reliable, and scalable software solution to help PEOs and ASOs grow and prosper. The PrismHR platform is a complete, integrated HR solution supporting the full "hire-to-retire” lifecycle of HR services. And PrismHR provides a wide range of additional resources that go beyond just technology and support: PrismHR SEEDS sales and marketing program, the annual PrismHR LIVE Conference, and numerous learning opportunities throughout the year are all designed specifically to help PrismHR customers grow their business." Later company description: "PrismHR is a fast-paced SaaS company which provides customers with a cloud-based payroll process software application. PrismHR also provides professional services including system implementation consulting, custom configurations, and training. Lastly, via the Company’s Marketplace platform customers and end users access other human resources and employee benefits applications from PrismHR’s Marketplace Partners." We'll combine as two paragraphs. Position Summary: "The Product Consultant serves as a trusted advisor to PrismHR customers and is responsible for implementing new customers and consulting existing customers on software and industry best practices for the PrismHR core platform. The role independently leads customers through successful implementations and projects by providing technical, product, and PEO/ASO/staffing industry expertise while coordinating cross-functional delivery and maintaining high standards for quality, documentation, and customer outcomes." Now Responsibilities bullet points from "Essential Duties And Responsibilities": List: - Own the customer relationship, evaluate business requirements, and provide best-practice guidance on implementing PrismHR solutions from technical and industry perspectives. - Document requirements and use cases in functional design documents, and interpret Statements of Work that define project scope, assumptions, deliverables, estimated hours, and schedules. - Maintain complete project documentation and detailed customer notes, and communicate project status proactively and regularly to management and relevant stakeholders. - Independently manage multiple customer implementations and consulting projects to ensure deliverables meet established quality standards, schedules, and customer expectations. - Collaborate with cross-functional teams to design, develop, and implement robust solutions in an Agile environment. - Design and execute complex merges and customer processes in support of implementation and consulting objectives. - Deliver effective presentations remotely and in person to customers at PrismHR meetings, customer engagements, and industry events. - Occasional domestic travel up to 25% is required to attend team onsite meetings, client visits, customer events, industry conferences, and training sessions. Travel may include air and ground transportation. Also "Marginal Functions" bullet points: - Build, maintain and promote relationships with team members, peers across disciplines, and all other company team members ensuring effective coordination of communications and services affecting clients. - Attend webinars and training to stay up to date on best practices related to the company and department. - Complete projects and other duties as assigned by supervisor. We should include these as responsibilities as well (they are part of duties). So add them. Now Knowledge, Skills, and Abilities bullet points (split each sentence): - Knowledge of PEO, ASO, staffing, payroll, benefits, and implementation-software processes. - Ability to work independently, analyze complex business and technical requirements, and develop practical solutions. - Ability to define and document workflows, requirements, use cases, and business processes clearly and accurately. - Excellent written and verbal communication skills, including the ability to explain technical and industry concepts to varied audiences. - Strong presentation and facilitation skills for remote and in-person customer engagements and industry events. - Ability to prioritize and manage multiple projects, tasks, schedules, and customer expectations in a fast-paced environment. - Strong technical aptitude and demonstrated commitment to continuous learning. - Ability to collaborate effectively with cross-functional teams in an Agile environment. Now Required Education & Experience bullet points: - At least five years of

Similar jobs

Product Specialist

VinciPalo Alto, CA· 3 wk ago
Business Development$150k–$180k/yrapply on jobs.ashbyhq.com