Project Analyst
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map content to those headings. About Us maybe not needed; could be omitted as not in list. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It may be that we should only use those headings; other headings not allowed. So we should not create About Us heading. We could incorporate that info into maybe "About the role" or "Qualifications"? But that would be misrepresenting. Better to omit company description if not allowed. However instruction says "Preserve ALL substantive information". If we omit About Us, we lose substantive info. But maybe they consider About Us as boilerplate? It's not boilerplate; it's company description. But they gave examples of headings; maybe they expect us to use those headings only, and any other content should be placed under appropriate existing headings (like "About the role" could include company overview). However "About the role" is about the role, not company. But we could put company info under "About the role" as a brief description? Might be okay.
Alternatively, we could create a section with heading "About the role" and include the summary plus company description? But that might mix.
Better to follow the instruction strictly: only use those headings. So we need to map content:
- About the role: could include summary and maybe daily interaction description.
- Responsibilities: essential duties list.
- Requirements: maybe education/experience etc? But they also have Qualifications and Skills separate. The list includes Requirements, Qualifications, Skills. We need to decide what goes where.
Typically: Requirements = education/experience; Qualifications = maybe certifications; Skills = abilities. But we have both.
We can allocate:
- Requirements: Education Required, Preferred Education, Experience.
- Qualifications: Regular Attendance required, maybe other qualifications like ability to read/interpret documents etc? Actually those are skills.
- Skills: Language Skills, Mathematical Skills, Reasoning Ability, Other skills and abilities (including knowledge of NEC, etc.)
But we also have "Complexity of Work" and "Relationship Outside Work Group". Those could go under "Requirements" or maybe separate sections not in list; but we could incorporate them into "About the role" or "Responsibilities"? Might be better to create separate sections even if not in list? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can create any heading as long as we use . The examples are just typical. So we can create headings for Complexity of Work, Relationship Outside Work Group, Physical Demands, Work Environment, etc. That would preserve all info.
Thus we will output sections: About the role (summary), Responsibilities (essential duties), Complexity of Work, Relationship Outside Work Group, Qualifications (maybe attendance?), Requirements (education/experience), Skills (language, math, reasoning, other), Physical Demands, Work Environment.
We must not include Benefits, Pay, Schedule unless present. Not present.
We must not repeat job title.
We must not include boilerplate like EEO, Note about not inclusive, etc.
We must preserve all substantive info.
Let's extract details.
Summary paragraph: "The Project Analyst position provides day to day support to project managers and supervisors to ensure assigned projects are properly set up, assigned, and tracked appropriately throughout their lifecycle. The Project Analyst must have a strong working knowledge of both client and Pike Engineering work management and accounting processes/systems in order to perform the functions of the role. The role will have daily interaction with field and engineering groups as well as client representatives."
We'll put that in
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It may be that we should only use those headings; other headings not allowed. So we should not create About Us heading. We could incorporate that info into maybe "About the role" or "Qualifications"? But that would be misrepresenting. Better to omit company description if not allowed. However instruction says "Preserve ALL substantive information". If we omit About Us, we lose substantive info. But maybe they consider About Us as boilerplate? It's not boilerplate; it's company description. But they gave examples of headings; maybe they expect us to use those headings only, and any other content should be placed under appropriate existing headings (like "About the role" could include company overview). However "About the role" is about the role, not company. But we could put company info under "About the role" as a brief description? Might be okay.
Alternatively, we could create a section with heading "About the role" and include the summary plus company description? But that might mix.
Better to follow the instruction strictly: only use those headings. So we need to map content:
- About the role: could include summary and maybe daily interaction description.
- Responsibilities: essential duties list.
- Requirements: maybe education/experience etc? But they also have Qualifications and Skills separate. The list includes Requirements, Qualifications, Skills. We need to decide what goes where.
Typically: Requirements = education/experience; Qualifications = maybe certifications; Skills = abilities. But we have both.
We can allocate:
- Requirements: Education Required, Preferred Education, Experience.
- Qualifications: Regular Attendance required, maybe other qualifications like ability to read/interpret documents etc? Actually those are skills.
- Skills: Language Skills, Mathematical Skills, Reasoning Ability, Other skills and abilities (including knowledge of NEC, etc.)
But we also have "Complexity of Work" and "Relationship Outside Work Group". Those could go under "Requirements" or maybe separate sections not in list; but we could incorporate them into "About the role" or "Responsibilities"? Might be better to create separate sections even if not in list? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can create any heading as long as we use . The examples are just typical. So we can create headings for Complexity of Work, Relationship Outside Work Group, Physical Demands, Work Environment, etc. That would preserve all info.
Thus we will output sections: About the role (summary), Responsibilities (essential duties), Complexity of Work, Relationship Outside Work Group, Qualifications (maybe attendance?), Requirements (education/experience), Skills (language, math, reasoning, other), Physical Demands, Work Environment.
We must not include Benefits, Pay, Schedule unless present. Not present.
We must not repeat job title.
We must not include boilerplate like EEO, Note about not inclusive, etc.
We must preserve all substantive info.
Let's extract details.
Summary paragraph: "The Project Analyst position provides day to day support to project managers and supervisors to ensure assigned projects are properly set up, assigned, and tracked appropriately throughout their lifecycle. The Project Analyst must have a strong working knowledge of both client and Pike Engineering work management and accounting processes/systems in order to perform the functions of the role. The role will have daily interaction with field and engineering groups as well as client representatives."
We'll put that in
. The examples are just typical. So we can create headings for Complexity of Work, Relationship Outside Work Group, Physical Demands, Work Environment, etc. That would preserve all info. Thus we will output sections: About the role (summary), Responsibilities (essential duties), Complexity of Work, Relationship Outside Work Group, Qualifications (maybe attendance?), Requirements (education/experience), Skills (language, math, reasoning, other), Physical Demands, Work Environment. We must not include Benefits, Pay, Schedule unless present. Not present. We must not repeat job title. We must not include boilerplate like EEO, Note about not inclusive, etc. We must preserve all substantive info. Let's extract details. Summary paragraph: "The Project Analyst position provides day to day support to project managers and supervisors to ensure assigned projects are properly set up, assigned, and tracked appropriately throughout their lifecycle. The Project Analyst must have a strong working knowledge of both client and Pike Engineering work management and accounting processes/systems in order to perform the functions of the role. The role will have daily interaction with field and engineering groups as well as client representatives." We'll put that in
under About the role. Responsibilities: list bullet points. Need to capture each bullet. Let's list them: - Plays an active role in project analysis, project workflow and assists in the preparation of deliverables to achieve defined objectives to the satisfaction of the client and of management. - Utilizes data gathering tools and methods to analyze and gather data needed for project requirements. - Supports the project team on project administration and process improvements. - Reviews and documents the requirements of a project throughout its lifecycle. - Provide lead support on local employee relations activities, office functions, client functions, etc - Ensures the entire project team completes the project within its planned scope and schedule. Works with project team to proactively identify issues and workable solutions affecting project results and profitability. - Enters necessary project information into the financial accounting system to allow for accurate project coding, invoicing, and accounting and reviews field technician timesheets for accuracy and operative time management. - Facilitate effective project meetings (project kickoff, client alignment, status meeting, progress review, etc.) - Promote meaningful performance related feedback/input to appropriate management and project team members - Maintain proper levels of quality control and manage document control on all projects as required; including paper and electronic filing and record keeping - Perform other duties as assigned by management. Note some bullets have formatting issues; we will capture as is. Complexity of Work: "Non-routine; general polices applied to frequently changing situations." Relationship Outside Work Group: "Influences decisions of moderate nature requiring high degree of tact." Qualifications: includes "REGU L A R A T TEND A NC Eisrequired." So Regular Attendance required. Also maybe other qualifications like "Be held accountable for maintaining all confidences regarding highly sensitive and proprietary information." etc. But those are under Other skills. We'll treat Qualifications as Regular Attendance required. Requirements: Education and Experience. Education Required: High school degree or GED. Preferred Associates degree (AA or equivalent from two-year college or technical school), in Engineering Technology or related field. Experience: 5-7 Year(s) Experience in distribution/utility or related field. Skills: Language Skills, Mathematical Skills, Reasoning Ability, Other skills and abilities. Language Skills: Ability to read and interpret documents such as procedure manuals, operational procedures, etc. Ability to write reports, Business correspondence, and procedure manuals. Ability to effectively present information in one-on one and small group situations to customers, clients, and other employees of the organization. Mathematical Skills: Ability to apply concepts such as fractions, percentages, ratios and proportions to practical situations. Ability to compute rate, ratio and percent and to draw and interpret spread sheets. Ability to compute rate, ratios, and percent and to draw and interpret spreadsheets (duplicate). Ability to apply concepts of basic algebra and geometry. Reasoning Ability: Ability to interpret a variety of instructions furnished in written, oral, diagram, or schedule form. Ability to solve practical problems and deal with a variety of concrete variables in situations where only limited standardization exists. Other skills and abilities: list: - Be well versed in the basic tenants of line construction and maintenance. - Must have a working knowledge of and adhere to the National Electric Safety Code and the ability to recognize distribution equipment and associated hazards. - Be held accountable for maintaining all confidences regarding highly sensitive and proprietary information. - Assures quality workmanship and on time delivery to the client for all projects assigned. - Supports the organization’s vision and strategy and demonstrates initiative and personal accountability to meet work demands according to the highest standard. - Exhibit organizational and planning skill - High commitment to achieving goals and plans - Demonstrated skills in verbal/written communications - Demonstrated negotiating and decision-making skill - Demonstrated management and business skills - Demonstrated skills in providing leadership, motivation, vision, and direction - High energy level with the ability to work in a fast paced, ambiguous environment - Demonstrated ability to work independently and follow through on assignments Physical Demands: includes table of time spent, weight lifting, vision requirements. We need to format as
or maybe
- for list? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. For physical demands table, it's not a list but a set of statements. Could be prose. We'll put as
with sentences. We need to capture all details: How much on the job time is spent in the following physical activities? Stand Up to 1/3 (Occasionally) Walk Up to 1/3 (Occasionally) Sit 1/3 to 2/3 (Frequently) Talk or Hear 1/3 to 2/3 (Frequently) Use Hands to Feel, Handle or finger tools or controls 1/3 to 2/3 (Frequently) Climb or balance None Stoop, Kneel, Crouch or crawl Up to 1/3 (Occasionally) Reach with Hands and Arms Up to 1/3 (Occasionally) Taste or Smell None Does this job require that weight be lifted or force be exerted? Up to 10 Pounds Up to 1/3 Up to 25 Pounds Up to 1/3 Up to 50 Pounds None Up to 100 Pounds None More than 100 Pounds None Does this job have any special vision requirements? ☒ Close Vision (clear vision at 20 inches or less) ☒ Color Vision (ability to identify and distinguish colors) ☒ Ability to Adjust Focus (ability to adjust the eyes to bring an object into sharp focus) Work Environment: includes list of conditions with frequencies. We need to capture: Wet, humid conditions (non-weather) None Work near moving mechanical parts Up to 1/3 (Occasionally) Work in high, precarious places None Fumes or airborne particles
- for any list of duties/requirements/benefits, and