Associate Project Manager 1 (Entry-Level) - Data Analytics
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. We have content: hybrid arrangement (work from home and office) – could be part of About the role or maybe a separate "Work Arrangement" but not in list; we could put under About the role. Responsibilities: The bullet list after "you may perform the following tasks:" includes many duties. That's responsibilities. Requirements: The posting has "Requirements" heading then a paragraph about interfacing with project team leadership etc. Actually after "Requirements" heading there is a paragraph describing role. Then later "Qualifications" heading with subheadings: "We do not sponsor employees for work authorization in the U.S. for this position." then "Essential Skills And Experience" list, then "Valued But Not Required Skills And Experience" list, then "Technology & Innovation" paragraph, then "About Sargent & Lundy" with benefits etc. Also "Compensation Range" and "Transparency Statement". Also "Equal Opportunity" boilerplate to remove. We need to preserve all substantive info, remove boilerplate like EEO, navigation, legal, etc. Also remove duplicated lines. We need sections: About the role (maybe include hybrid arrangement and description), Responsibilities (the task list), Requirements (maybe the paragraph after Requirements heading?), Qualifications (maybe combine Essential Skills and Valued But Not Required?), Skills (maybe separate?), Benefits (the benefits list), Pay (compensation range), Schedule (maybe not present; we have hybrid arrangement but schedule not given; we could omit Schedule if not specific). The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated (list). Pay is stated (compensation range). Schedule: not given; we have hybrid arrangement but not schedule specifics; we could treat hybrid arrangement under About the role, not Schedule. We must not repeat job title as heading. No Job ID. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. First, About the role: The posting starts: "This position allows for a hybrid arrangement with a mix of work from home and in the office." Then after that maybe a sentence? Actually after that line there is a line break then "Requirements". So the hybrid arrangement is the only description before Requirements. Could also include the sentence after Requirements? Actually after Requirements heading there is a paragraph: "This position will interface with project team leadership and stakeholders to coordinate project management functions throughout the project life cycle in support of Grid work. The role will provide an opportunity to understand and develop solutions to meet Project Management needs and Client requirements for the successful execution of projects." That seems like role description. Could be part of About the role or Responsibilities? Usually that is role summary. We'll put under About the role. Thus About the role content: hybrid arrangement sentence + the paragraph about interfacing etc. Now Responsibilities: The list after "you may perform the following tasks:" includes many items. We'll put each as
- .
Now Requirements: The heading "Requirements" appears before that paragraph? Actually the text: "Requirements This position will interface..." So the heading "Requirements" then the paragraph. So we can treat that paragraph as Requirements section. However we already used that paragraph in About the role. Might duplicate. Better to follow the headings: Requirements section contains that paragraph. Then About the role maybe not needed? But we need About the role heading only if we have content. We could treat the hybrid arrangement as About the role, and the paragraph after Requirements as part of Requirements. But the paragraph after Requirements is more about role description; could be considered Responsibilities? However we already have a responsibilities list. The paragraph is more about purpose. Could be part of About the role. But we already used heading Requirements for that paragraph; we need to decide.
Let's examine original:
"This position allows for a hybrid arrangement with a mix of work from home and in the office.
Requirements This position will interface with project team leadership and stakeholders to coordinate project management functions throughout the project life cycle in support of Grid work. The role will provide an opportunity to understand and develop solutions to meet Project Management needs and Client requirements for the successful execution of projects.
Using a variety of industry and proprietary software tools, and under the direction of project leadership, you may perform the following tasks:
[list]"
Thus the heading "Requirements" is misplaced; actually it's likely a label for the following description. So we can treat that as "About the role" or "Job Summary". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put the hybrid arrangement + that paragraph under About the role. Then Responsibilities is the task list. Then Requirements could be the "Essential Skills And Experience" maybe? But there is a separate "Qualifications" heading later. Actually after the task list, we see "Qualifications" heading then "We do not sponsor employees..." then "Essential Skills And Experience" list then "Valued But Not Required Skills And Experience" list then "Technology & Innovation" paragraph then "About Sargent & Lundy" etc. So Qualifications section likely includes the essential and valued skills. The "Requirements" heading earlier might be a mistake; we could ignore it as duplicate or treat as part of About the role. Since we must not create sections with filler, we should not create a Requirements section if the content is not substantive beyond what we already used. The content after "Requirements" heading is substantive (role description). But we already used that in About the role. If we create a Requirements section, we would duplicate. Better to put that content under About the role and not create a separate Requirements section. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine.
Thus sections: About the role (hybrid arrangement + role description), Responsibilities (task list), Qualifications (essential skills + valued but not required + technology & innovation), Benefits (list), Pay (compensation range). Possibly also include "Work Arrangement" but we already have hybrid in About the role.
Now extract details.
About the role content:
- "This position allows for a hybrid arrangement with a mix of work from home and in the office."
- "This position will interface with project team leadership and stakeholders to coordinate project management functions throughout the project life cycle in support of Grid work."
- "The role will provide an opportunity to understand and develop solutions to meet Project Management needs and Client requirements for the successful execution of projects."
We can combine into a paragraph or two paragraphs. Use
for prose. Responsibilities list items (extract each bullet): 1. Understand S&L and client procedures and processes, and ensure project team deliverables are in compliance 2. Implement project controls and project management tools and methodology 3. Assemble supporting data and documentation in response to project team and client requests 4. Create workflows, processes, flowcharts, and procedures 5. Support contract processing and new project setup 6. Develop and compile periodic project reporting to support project monitoring and decision making 7. Compile and coordinate the preparation of invoice packages 8. Process Subcontractor Purchase Orders with procurement department 9. Work with project management and controls department to maintain budgets, update accruals, and forecast cash flow 10. Prepare, maintain, and track Change Order Logs and RFI Logs 11. Attend project walkdowns and regular site visits to interface with contractors and material vendors 12. Attend or run regular project stakeholder meetings and document minutes to disperse to the team 13. Help prepare and compile proposals, org charts, and PowerPoint presentations 14. Coordinate with project management to organize, report and present project financials, schedule status, risks and mitigation plans, contract backlogs, project status, and staffing plans 15. Provide training and supervise administrative assistants 16. Travel to client offices and project sites, as required Now Qualifications: We have several subparts. First: "We do not sponsor employees for work authorization in the U.S. for this position." This is a requirement (maybe under Qualifications). We'll include as a paragraph. Then "Essential Skills And Experience" list: - A BS in Construction Management, Business, Engineering, or similar degree - Knowledge of field/site work sequencing including civil, structural, electrical, and other related trades in the power, heavy civil, or commercial construction industry - Demonstrated ability to organize and prioritize work and work under pressure to meet deadlines - Working knowledge in MS Office tools, with emphasis on the advanced use of MS Excel in creating and maintaining detailed, interactive spreadsheets, workbooks, and databases - Excellent written and verbal communication skills, with a proven ability to interact and multitask with project team members, clients, and vendors of varying position levels - Eager to cultivate program and project knowledge to make a valuable impact to the PMO team operation; willing to engage with others to understand PMO team and client needs - Committed to deliver high quality, accurate deliverables with attention to detail - Comfortable with a pproximately 10-25% domestic travel (note typo "pproximately"; we keep as is) Then "Valued But Not Required Skills And Experience" list: - 1+ years of construction or engineering internship, co-op, or work experience which includes project controls, project planning, project scheduling, and earned value performance, preferably within the power industry - Experience analyzing, validating, and reporting project, operational, financial, or engineering data using advanced Excel, Power BI, SQL, or similar analytics tools. - Familiarity with data visualization, dashboard development, and KPI reporting to support project performance monitoring and decision-making. - Experience working with large datasets, data quality validation, data cleansing, and process automation using Python, R, SQL, Power Query, or comparable tools. - Knowledge of database concepts, data pipelines, ETL processes, or business intelligence platforms such as Power BI, Databricks, Tableau, or similar technologies. - Demonstrated ability to identify trends, anomalies, risks, and improvement opportunities through quantitative analysis and present findings to stakeholders. - Experience documenting business processes, developing standard operating procedures (SOPs), and supporting continuous improvement initiatives. - Familiarity with scheduling software, preferably Primavera - Familiarity with finance and accounting systems - Engineering design experience is a plus - PMP Certification is a plus - Construction/field knowledge or experience is a plus Then "Technology & Innovation" paragraph: "Sargent & Lundy values the appropriate use of technology to improve how work gets done and deliver high-quality outcomes for our clients. Depending on the role, employees may use data, automation, artificial intelligence, and other digital tools to support research, analysis, engineering and design activities, workflow improvement, or other aspects of their work. We value candidates who demonstrate an interest in learning and effectively using emerging technologies where relevant to their role. Employees remain accountable for their work and are expected to apply appropriate professional judgment and review when using technology-assisted tools. Experience with AI, automation, programming, or similar technologies is valued where relevant but is not required unless specifically identified elsewhere in the job description." We can include that as a paragraph under Qualifications or maybe a separate Skills section? The instruction includes Skills heading. Could put technology paragraph under Skills. But we already have essential and valued skills lists; those are skills. The technology paragraph is more about company values. Could be part of About the role or Qualifications. I'd put it under Qualifications as additional note. Now Benefits: list after "About Sargent & Lundy" includes many items. Let's extract: - Health Plans: Medical, Dental, Vision - Life & Accident Insurance - Disability Coverage - Employee Assistance Program (EAP) - Back-Up Daycare - FSA & HSA - 401(k) - Pre-Tax Commuter Account - Merit Scholarship