Implementation Consultant

We need to output HTML fragment with sections: headings

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 — fold minor metadata into short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Key sections: Position Summary (maybe "About the role" or "Position Summary"? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content to these headings. We have: - Position Summary: description of role. - Key Responsibilities: with subheadings Implementation Ownership, Project Management & Delivery, Cross-Functional Collaboration, Documentation & Reporting. - Required Qualifications & Skills: with subheadings Project Management, Client-Facing Skills. - Preferred Experience: bullet list. - What Success Looks Like: description. - Salary: "The expected salary for this position ranges from $70,000 to $80,000 annually. The actual salary will be determined on an individualized basis..." - Benefits: "In addition to base salary and a competitive benefits package, this position may be eligible for additional types of compensation such as bonuses." - Applicants must be authorized to work in the U.S. (maybe part of Requirements? Not a benefit.) - EEO boilerplate etc to remove. - "Your Right to Work: ..." also legal boilerplate to remove. - "We are unable to sponsor or take over sponsorship of an employment Visa or STEM OPT at this time." Also legal. We need to remove all legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we keep: Position Summary, Responsibilities (maybe as a section), Required Qualifications & Skills (maybe combine Qualifications and Skills?), Preferred Experience (maybe part of Qualifications?), What Success Looks Like (maybe part of Responsibilities?), Salary, Benefits. But we must not create sections with filler. So we need to decide which sections to include. We have substantive content for: - About the role (Position Summary) - Responsibilities (Key Responsibilities) - Qualifications (Required Qualifications & Skills) maybe also Preferred Experience. - Skills (maybe part of Qualifications & Skills). But we could combine Qualifications and Skills into one section? The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could have separate Qualifications and Skills sections if we have content. But we might not have distinct separate lists for qualifications vs skills; they are intertwined. However we could split: Qualifications: Required Qualifications & Skills (maybe treat as Qualifications). Skills: maybe list specific skills from Preferred Experience? But that might be thin. Better to follow instruction: Prefer a few substantive sections over many thin ones. So we can combine Qualifications and Skills into one section called "Qualifications & Skills" but the instruction only gave examples; we can still use that heading? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should stick to those examples. However we could use "Qualifications" and "Skills" separately if we have content. Let's see if we can extract distinct lists. Qualifications: Required Qualifications & Skills includes Project Management and Client-Facing Skills subheadings. That's more like skills. Preferred Experience includes prior experience, experience with workflow automations using Claude, data migration, delivering implementation and post-implementation engagements, troubleshooting integration issues, strong working knowledge of BigTime platform. Those are more like qualifications/experience. Thus we could have: - Qualifications: list of required qualifications (maybe from Required Qualifications & Skills) and preferred experience. - Skills: maybe list of specific skills like project management, consultative communication, etc. But to avoid thin sections, maybe we just have one "Qualifications & Skills" section. However the instruction says we can use those headings as examples; not mandatory to use exactly those. It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings; we can also use others if needed, but better to stick to those. Thus we can have sections: - About the role (Position Summary) - Responsibilities (Key Responsibilities) - Qualifications (Required Qualifications & Skills + Preferred Experience) - Skills (maybe we can extract from Required Qualifications & Skills subheadings: Project Management, Client-Facing Skills). But that might be redundant. - Pay (salary range) - Benefits (competitive benefits package, bonuses) - Schedule? Not mentioned. So we should not create Schedule section. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Pay is stated, Benefits is stated (competitive benefits package, bonuses). So we include Pay and Benefits. We must not include filler like "commensurate with experience". Not present. Now we need to preserve all substantive information, not invent or summarize away detail. So we need to keep details like: - Position Summary: leading customers through implementation, managing project, guiding configuration, ensuring prepared, delivering additional services such as training, workflow optimization, stabilization assessments, other approved PS engagements as needs evolve. Success requires strong project management skills, consultative problem solving, ability to translate business requirements into effective solutions within BigTime platform. - Key Responsibilities: we need to keep all bullet points under each subheading. We should format as

  • for any list of duties/requirements/benefits. So we need to turn the responsibilities into list items. The subheadings (Implementation Ownership, Project Management & Delivery, Cross-Functional Collaboration, Documentation & Reporting) could be headings inside the Responsibilities section? But we only have

    for section headings; we could use

    for subheadings? Not prohibited but not mentioned. Safer to keep them as part of list items? But we need to preserve the structure. Could we make each subheading a inside a list item? Or we could keep them as separate

    but not required. The instruction only says use

    for section headings; doesn't forbid other headings. But to be safe, we can keep them as

    inside the section. However the instruction says output ONLY the HTML fragment; we can include

    . It didn't forbid. But to be safe, we could just treat each responsibility as a list item and include the subheading as part of the item text. But we need to preserve ALL substantive information; we can include the subheadings as part of the list item text (maybe bold). That preserves meaning. Similarly for Required Qualifications & Skills: we have subheadings Project Management and Client-Facing Skills. We'll preserve them as part of list items. Preferred Experience: list of items. What Success Looks Like: prose. Pay: prose. Benefits: prose. Now we need to remove boilerplate: EEO, Right to Work, visa sponsorship, etc. Also remove duplicated lines (none visible). Also remove application instructions (none explicit). Also remove cookie/navigation/legal. Now we need to ensure we don't include any mention of "Applicants must be authorized to work in the U.S." That is a requirement but not boilerplate? It's a requirement about work authorization. It's substantive? It's a requirement for applicants. Should we keep? It's not EEO; it's a legal requirement but it's a condition of employment. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. "Applicants must be authorized to work in the U.S." is a legal requirement; could be considered boilerplate? It's a standard line but it's substantive about eligibility. Might be considered legal boilerplate. However it's not EEO; it's about work authorization. The instruction says remove legal boilerplate. So we should drop that line. Also "BigTime Software, Inc. is proud to be an Equal Opportunity Employer..." remove. Also "Your Right to Work: ..." remove. Also "We are unable to sponsor or take over sponsorship of an employment Visa or STEM OPT at this time." remove. Now we need to ensure we keep all other substantive info. Let's extract the content. Position Summary paragraph: "The Implementation Consultant is responsible for leading customers through a successful implementation of BigTime products, from project kickoff through go-live. This role manages the implementation project, guides customers through configuration and best practices, and ensures they are prepared to confidently use BigTime in their day-to-day operations. Beyond implementation, the Implementation Consultant may deliver additional services such as training, workflow optimization, stabilization assessments, and other approved Professional Services engagements as customer needs evolve. Success in this role requires strong project management skills, consultative problem solving, and the ability to translate business requirements into effective solutions within the BigTime platform." Now Responsibilities: We have headings: Implementation Ownership - Establish and partner on the overall relationship with each assigned client throughout implementation with the Relationship Manager. - Identify the client's core business drivers early and use them as the throughline for kickoff calls, working sessions, follow-up emails, and the close-out meeting. - Build and maintain an Implementation and project timeline, sharing an updated version with the client before every session. - Identify at-risk implementations early, create an at-risk record, and build a recovery plan in partnership with the Relationship Manager. - Own the end-to-end data migration process, partnering with Escalation Engineers when custom scripting or technical expertise is required. - Close out each implementation once the client is stabilized and confident, and capture client sentiment through a satisfaction survey. Project Management & Delivery - Run the implementation like a project: scoped milestones, a documented timeline, clear ownership, and a defined path to go-live. - Schedule and run working sessions at a cadence that keeps momentum, adjusting scope and timeline transparently when the client's needs change. - Record sessions, and follow up every call with a written recap covering what was covered, what's next, and any open items. - Escalate platform issues or enhancement requests that put an implementation at risk, and keep the Service’s Management Team informed of escalation impact. - Apply core project management principles (scope, schedule, risk, and stakeholder management). - Deliver approved Professional Services engagements, including additional training, workflow optimization, custom invoice calculators, XML invoice templates, reporting, and other post-implementation services. - Provide consultative guidance on BigTime best practices for time tracking, billing, invoicing, reporting, and project management, helping customers maximize the value of the platform. Cross-Functional Collaboration - Work closely with Sales, Solutions Consulting, Customer Success, Product, and Support to keep the client's experience consistent end-to-end. - Flag areas of concern before an implementation kicks off by consulting with Sales and Solutions Consulting on anything that may require nonstandard configuration. Documentation & Reporting - Maintain accurate, current notes in Salesforce for every engagement, including the Implementation Plan, timeline, and key decisions. - Keep engagement status, at-risk flags, and PS Opportunity fields current so leadership