Professional Services Consultant (Finance Software) - Remote

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: "What We’re About", "Your Growth Matters", "Your Commitment Deserves Reward", "The Role", "Job Duties", "Requirements". We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map headings accordingly. The posting has "What We’re About" (maybe about company). Could be "About the role? Actually "The Role" heading. "Job Duties" could be Responsibilities. "Requirements" heading. Also there is "Your Growth Matters" and "Your Commitment Deserves Reward" which talk about benefits and growth. Could be Benefits section. Also there is mention of compensation: "We offer competitive compensation and a benefits package designed to support your life inside and outside of work—tuition reimbursement, parental leave, paid volunteer hours, and unlimited PTO. Plus, our flexible work environment gives you the freedom to balance your heroic work with personal well-being, whether you’re in the office or remote." That's benefits and maybe schedule? Not explicit schedule. So we can have Benefits section with list of benefits. Also "Your Growth Matters" could be about career development, maybe not a standard heading; but we could incorporate into Benefits or maybe a separate "Growth Opportunities" but not in allowed list. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says use those as examples, but we can use other headings if needed? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect we use those headings when applicable. So we should map content to those headings. We have: - About the role: could be "The Role" description (the paragraph about Naviline consultant role). That fits About the role. - Responsibilities: Job Duties list. - Requirements: Requirements list. - Benefits: benefits described (tuition reimbursement, parental leave, paid volunteer hours, unlimited PTO, flexible work environment). Also maybe "competitive compensation" but we don't have specific pay, so we should not create Pay section unless posting actually states them. It says "competitive compensation" but no specifics, so we should not create Pay section because it's not specific. So we omit Pay. - Schedule: not mentioned, so omit. - Qualifications/Skills: maybe we could combine with Requirements? But we have Requirements already. Could also have Skills separate but not needed. We must not repeat job title as heading. The job title is "Naviline consultant". Not to be used as heading. We must not include Job ID/requisition numbers. We must remove boilerplate like cookie/navigation/legal/EEO etc. Not present. We must preserve all substantive information. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

... paragraph ...

Responsibilities

• ...
...

Requirements

• ...
...

Benefits

• Tuition reimbursement
• Parental leave
• Paid volunteer hours
• Unlimited PTO
• Flexible work environment (office or remote)

Maybe also include "Your Growth Matters" content: mentorship, learning programs, clear paths for advancement. Could be part of Benefits or maybe a separate section "Growth Opportunities". But not in allowed list. Could incorporate into Benefits as bullet points: mentorship, learning programs, career advancement paths. However the instruction: "Prefer a few substantive sections over many thin ones." So we could add those under Benefits as well. Thus Benefits section bullet list includes: tuition reimbursement, parental leave, paid volunteer hours, unlimited PTO, flexible work environment, mentorship, learning programs, clear paths for advancement. We must not invent details; we have those from "Your Growth Matters" and "Your Commitment Deserves Reward". So include them. Now we need to ensure we preserve all substantive information from the posting. Let's extract the substantive paragraphs: First paragraph: "CentralSquare Technologies is Hero-Grade. As the trusted provider of public sector software in North America, more than 8,000 agencies rely on our comprehensive, cloud-based platform to manage critical operations - from dispatch to records, permitting to payroll. We serve with purpose and stand together with our heroes, committed to supporting the public sector with software built for impact." Second: "What We’re About At CentralSquare, we don’t just build software - we power public servants and uplift communities with Hero-Grade Technology. Every line of code, every feature we deliver helps heroes across North America protect, serve, and save lives. When you join us, you become part of a mission-driven team creating technology that makes communities safer and stronger." Third: "Your Growth Matters. We believe heroes deserve opportunities to rise. That’s why we invest in your career with mentorship, learning programs, and clear paths for advancement. If you’re motivated, there’s no limit to how far you can go." Fourth: "Your Commitment Deserves Reward. We offer competitive compensation and a benefits package designed to support your life inside and outside of work—tuition reimbursement, parental leave, paid volunteer hours, and unlimited PTO. Plus, our flexible work environment gives you the freedom to balance your heroic work with personal well-being, whether you’re in the office or remote." Fifth: "Join us and help build the tools that power real-life heroes. Together, we make a difference." Then "The Role This Naviline consultant role requires the ability to engage in discussions with customers' Finance and/or Human Resource/Payroll staff relating to new implementations, internal projects, and new service offerings, as a subject matter expert in Naviline. The consultant will have a passion for the customer, demonstrated through professionalism and striving for excellence in all aspects of the customer experience. This includes implementing complex projects to conclusion while maintaining high customer satisfaction. The role requires an individual who is resourceful, confident under pressure, and has demonstrated skill as a subject matter expert in multiple areas of the software. Travel is required as needed." Then "Job Duties" list bullet points (starting with "Assist customers..."). Then "Requirements" list bullet points. We need to include all that. Thus About the role section should include the description of the role (the paragraph after "The Role"). We also might include the introductory company description? That is not about the role but about company. Could be part of About the role? Might be better to include as a separate section like "About the company" but not in allowed headings. However we could incorporate into About the role? The instruction: "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. It might be okay to have other headings but they'd like those specific ones. Safer to stick to those headings and put all relevant content under them. Thus we need to decide where to put the company overview and mission statements. Could be part of About the role? Not exactly. But we could treat "About the role" as including both role description and company context? Might be okay. Alternatively we could create a section "About the company" but not in list; risk of being considered filler. Better to include under About the role? The instruction says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples of possible headings; we can use others if needed but they'd prefer those. However the company overview is substantive; we could put it under a heading like "About CentralSquare" but that's not in list. Might be considered a heading not in the list but still okay? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, just that we should use h3 for section headings, and gives examples. So we could add a heading like "About the company". But they said "Prefer a few substantive sections over many thin ones." Adding another heading may increase sections. But we could incorporate company overview into About the role section as introductory paragraph. Thus About the role section will have multiple paragraphs: first the company overview, then the role description. Now Responsibilities: list of duties. Requirements: list. Benefits: list of benefits plus growth items. We must not include Pay or Schedule. Now ensure we preserve all substantive information: we need to include the bullet points exactly as given (or close). Let's extract them. Job Duties bullet points: - Assist customers with system configuration based on recommended best practices, workflows, and business requirements. - Perform system demonstrations and assist the customer with system review prior to go-live. - Develop and maintain subject matter expert knowledge for the configuration of our software solutions. - Provide consistent follow-through on the project tasks, deliverables, and communications with the Project Manager and the clients. - Build and maintain strong working relationships with customers. - Work independently with minimal supervision to meet required deadlines for a project as well as taking responsibility and ownership of issues and assignments. - Work with a wide range of disciplines and personalities, both internally and externally. - Collaborates with senior consultants and Project Managers to align on best practices and project delivery standards. - Performs all other duties as assigned. Note some have capitalization differences; we keep as is. Requirements bullet points: - B.A. or B.S. Degree, or an Associate's Degree, or certificate with equivalent work experience - 2+ years of experience with Financial software implementation, consulting, and/or usage, with preference for hands-on implementation or consulting experience - Excellent presentation skills - Ability to adapt quickly to changing business and customer needs, maintaining a high degree of flexibility - Ability to handle multiple projects and tasks simultaneously - Ability to learn new applications and system features quickly - Dedicated to the best possible customer experience and takes initiative toward improving it - Desire to travel up to 25% for training at customer sites - Ability to articulate technical and functional concepts to technical and non-technical audiences Now Benefits: from "Your Commitment Deserves Reward": tuition reimbursement, parental leave, paid volunteer hours, unlimited PTO, flexible work environment (office or remote). Also "competitive compensation" but not specific; we should not create Pay section. Could mention competitive compensation as a sentence in Benefits paragraph? The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". So we should not create a Pay section because we don't have specific numbers. But we could include a sentence about competitive compensation inside Benefits section as prose, not as a heading. That's okay. Also from "Your Growth Matters": mentorship, learning programs, clear paths for advancement. Thus Benefits section could be a

with those items, plus maybe a preceding paragraph about competitive compensation. We need to ensure we don't miss any substantive info: also the line "Join us and help build the tools that power real-life heroes. Together, we make a difference." That's a call to action; could be considered boilerplate? It's not navigation/legal; it's motivational. Might be considered part of the posting but not essential? It's substantive but could be considered a closing statement. We could include it as a paragraph under About the role or maybe after Benefits. Since it's not a heading, we can add