Business Process Consultant
Randstad Digital Americas · Tallahassee, FL · 1 mo ago
Management$70–$80/hrFull-time
We need to output HTML fragment with sections: About the role? Not present. Responsibilities: we have many bullet points. Requirements/Qualifications: we have mandatory qualifications and preferred qualifications. Also we have location, job type, salary, work hours, education. Those could go under Pay, Schedule, Benefits? Actually Pay: salary $70-80 per hour. Schedule: work hours 8am to 5pm. Benefits: none mentioned. Education: Bachelors (but that's part of qualifications). We should not repeat job title. Use headings: for Qualifications and then inside have
for sections like Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real specific content. We have Responsibilities (detailed). We have Qualifications (mandatory and preferred). We have Skills (maybe list of abilities). We have Pay (salary). We have Schedule (work hours). Benefits: none, so omit. About the role: not present. Could combine Mandatory Qualifications and Preferred Qualifications under Qualifications heading. Could also separate Requirements and Qualifications? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Responsibilities, Requirements, Qualifications, Skills, Pay, Schedule. We need to decide what goes where. Responsibilities: the long list under "Contractor Responsibilities..." etc. Requirements: maybe mandatory qualifications (minimum years, degree, etc). Qualifications: preferred qualifications (abilities, etc). Skills: maybe list of specific skills like Microsoft Office, SharePoint, Visio, etc. But we could also put those under Qualifications. However we need to avoid thin sections. Could combine Requirements and Qualifications into one Qualifications section? But we have both mandatory and preferred; we could put all under Qualifications. Then we could have Skills separate for technical skills. Let's see content: Mandatory Qualifications: - Minimum Seven (7) Years Of IT Experience. - Bachelor's degree in Computer Science, Information Systems, Business Administration, or related field. Equivalent professional experience may substitute for degree requirements. - Minimum four (4) years of experience performing business process analysis, business process reengineering, process improvement, or organizational change initiatives. - Minimum Two (2) Years Of Experience Performing Project Management. - Experience working on large, complex enterprise-wide projects requiring coordination across multiple business units and stakeholders. - Experience facilitating process improvement efforts involving multiple departments, agencies, or organizational units. - Experience documenting current-state and future-state business processes, workflows, and operational procedures. Preferred Qualifications (list many): - Ability to create/harness harmony amongst team members. - Ability to keep stakeholders informed appropriately. - Ability to work with minimal supervision. - Able to work onsite in Tallahassee, Florida. - Excellent general documentation skills. - Excellent interpersonal skills. - Experience interacting with functional groups within the Accounting organization to communicate and clarify customer requirements. - Experience using Microsoft Office Suite (Word, Excel, PowerPoint, Outlook). - Experience using SharePoint for collaboration and document management. - Experience working under general direction of senior level management. - Experience documenting business processes and standard operating procedures. - Experience working with the State or with other governments similar in size in terms of annual budget and full-time equivalent (FTE) employee count. - Knowledge and/or experience with the Florida Accounting Information Resource (FLAIR) subsystem. - Knowledge and application of Finance and Accounting practices. - Knowledge of Florida PALM project. - Knowledge and application of State of Florida financial, accounting, budgeting, procurement, or grants management processes. - Strong facilitation and interpersonal skills. - Strong verbal and written communication skills. - Track record of taking responsibility for end-to-end execution of tasks/assignments. - Demonstrated experience leading business process improvements. - Experience supporting fiscal year-end activities, financial reporting budgeting, procurement, or grants management processes - Strong engagement skills. - Strong Organizational skills. - Knowledge and application of prepartion of policy and position description documents. - Knowledge and application of functional flow charting using Visio or compriable software. Also later there is "Contractor Responsibilities..." repeated. We also have location: Tallahassee, Florida; job type: Contract; salary: $70 - 80 per hour; work hours: 8am to 5pm; education: Bachelors. We could put location and job type maybe under a short paragraph meta? But instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include a
for location, job type, etc. But we also have Pay and Schedule sections for salary and work hours. Thus:
Responsibilities
- ... each bullet from responsibilities list.
for Qualifications and then inside have ? Not allowed? The instruction only says use for section headings (list). It doesn't forbid other headings, but to be safe we can just use for Qualifications and then separate mandatory and preferred as
for section headings (list). It doesn't forbid other headings, but to be safe we can just use for Qualifications and then separate mandatory and preferred as
or
- with maybe a note. Could also split into Requirements (mandatory) and Qualifications (preferred). That seems reasonable: Requirements heading for mandatory qualifications; Qualifications heading for preferred qualifications. Then Skills heading for specific technical skills (Microsoft Office, SharePoint, Visio, etc). But many of those are also in preferred qualifications. Might be redundant.
Better: Use Requirements for mandatory qualifications; Qualifications for preferred qualifications; Skills for technical tools (Microsoft Office Suite, SharePoint, Visio, etc). However many preferred qualifications include abilities and soft skills; we could keep them under Qualifications.
Let's extract mandatory qualifications as list:
- Minimum Seven (7) Years Of IT Experience.
- Bachelor's degree in Computer Science, Information Systems, Business Administration, or related field. Equivalent professional experience may substitute for degree requirements.
- Minimum four (4) years of experience performing business process analysis, business process reengineering, process improvement, or organizational change initiatives.
- Minimum Two (2) Years Of Experience Performing Project Management.
- Experience working on large, complex enterprise-wide projects requiring coordination across multiple business units and stakeholders.
- Experience facilitating process improvement efforts involving multiple departments, agencies, or organizational units.
- Experience documenting current-state and future-state business processes, workflows, and operational procedures.
Preferred qualifications list (as above). We'll put them under Qualifications.
Skills: maybe list of specific tools: Microsoft Office Suite (Word, Excel, PowerPoint, Outlook), SharePoint, Visio or comparable software, People First LMS (maybe), etc. Also knowledge of FLAIR subsystem, Florida PALM project, State of Florida financial/accounting/budgeting/procurement/grants management processes. Could be considered skills.
But to avoid thin sections, we could combine Skills into Qualifications. However the instruction says prefer a few substantive sections over many thin ones. So maybe we just have Responsibilities, Requirements, Qualifications, Pay, Schedule. That's five sections. That seems fine.
We'll put Requirements = mandatory qualifications. Qualifications = preferred qualifications (including abilities, soft skills, technical skills). Pay = salary. Schedule = work hours.
We also might include location and job type as a short paragraph before sections? Could be minor metadata; we can include a
with location and job type. We must not repeat job title. The page already shows it, so we don't add heading for it. Now produce HTML fragment:
Location: Tallahassee, Florida. Job type: Contract.
Requirements
- ...
Qualifications
- ...
Pay
$70 - 80 per hour
Schedule
8am to 5pm
We should not include Benefits section. Check that we preserve all substantive information: Did we miss any? Let's verify. From mandatory qualifications we captured all. From preferred qualifications we captured all? Let's list them and ensure each appears. Preferred qualifications list from text: - Ability to create/harness harmony amongst team members. - Ability to keep stakeholders