Project Analyst I

We need to output HTML fragment with sections: About the role? Actually the posting includes "Short Description", "Purpose", "Responsibilities", "Success Metrics and Competencies", "Qualifications", "About Bowman", "Physical Demands and Working Environment", "Job Description Disclaimer". We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map headings accordingly. We must not repeat job title as heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Job Description Disclaimer" maybe considered boilerplate? It's a disclaimer; likely remove. Also remove EEO statements. Also remove "If you’d like more information on your EEO rights..." etc. Also remove "If you have any questions about the application process, please email recruiting@bowman.com." That's application instruction, remove. We need to preserve all substantive information. So we need sections: maybe "About the role" (short description + purpose?), "Responsibilities", "Success Metrics and Competencies" (could be Skills), "Qualifications", "About Bowman" (company overview), "Benefits" (from About Bowman benefits), "Physical Demands and Working Environment". Pay and Schedule not present, so omit those sections. We must not create sections with filler like "commensurate with experience". In Qualifications we have "Bachelor’s degree in business administration or related field preferred, or equivalent commensurate experience." That's a phrase "equivalent commensurate experience" which is not filler? It's okay. We should keep it. We need to use

• for any list of duties/requirements/benefits. So we need to turn responsibilities into list items. Also success metrics/competencies into list. Qualifications maybe list. Benefits list. We need to use

  for prose. We must output only HTML fragment, no /, no markdown fences. Let's extract content. Short Description: "Bowman has an opportunity for a Project Analyst I to join our team in Charlotte, NC. At Bowman, we believe in creating opportunities for aspiring people to thrive and achieve ambitious goals. That’s why a career at Bowman is more than a job. It is an opportunity to be part of a diverse and engaged community of professionals, to be treated as a respected and valued member of a motivated team and to be empowered to do exceptional work that advances the best interest of everyone involved. We recognize the importance of creating a work environment that is both rewarding to our employees and supportive of our unwavering commitment to provide unparalleled service to our clients." Purpose: "Manage and coordinate the administrative aspects of projects to ensure they are completed on time and within budget. Support Project Manager by analyzing data and contributing to overall project strategy and performance evaluation." We could combine short description and purpose under "About the role". Or separate? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (includes short description and purpose). Then Responsibilities, then Skills (Success Metrics and Competencies), then Qualifications, then About Bowman (maybe as "About the company"? Not in list but we can still use heading? The instruction says use those headings for section headings, but we can also add other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate; we can also use other headings if needed? Safer to stick to those. So we could map: - About the role: short description + purpose. - Responsibilities: responsibilities section. - Skills: Success Metrics and Competencies. - Qualifications: qualifications. - Benefits: from About Bowman benefits. - About Bowman maybe not needed; but we have company overview that could be part of About the role? Might be redundant. However we have "About Bowman" section describing company mission, values, benefits. Could treat as "About the company" but not in list. Could incorporate into About the role? Might be okay to add a heading "About Bowman" as

  though not in list but still a heading. The instruction says 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

  for section headings (e.g. those). Likely they expect those headings only. But we can still include About Bowman as a paragraph under About the role? Might be okay. Better to follow exactly: Use those headings when appropriate. So we will have:

  About the role

  Short description + purpose.

  Responsibilities

  list items from responsibilities.

  Skills

  list items from Success Metrics and Competencies.

  Qualifications

  list items from qualifications.

  Benefits

  list items from benefits. We may also need a section for "Physical Demands and Working Environment". Not in list but could be omitted? It's substantive. Could be placed under a heading like "Working Conditions" but not in list. Perhaps we can incorporate into About the role? Not ideal. Could create a heading "Physical Demands and Working Environment" as

  even though not in the example list; but instruction says 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

  for section headings (giving examples). So we can use any heading we want as long as it's

  . So we can add a heading for Physical Demands. Thus final HTML:

  About the role

  Bowman has an opportunity for a Project Analyst I to join our team in Charlotte, NC. At Bowman, we believe in creating opportunities for aspiring people to thrive and achieve ambitious goals. That’s why a career at Bowman is more than a job. It is an opportunity to be part of a diverse and engaged community of professionals, to be treated as a respected and valued member of a motivated team and to be empowered to do exceptional work that advances the best interest of everyone involved. We recognize the importance of creating a work environment that is both rewarding to our employees and supportive of our unwavering commitment to provide unparalleled service to our clients. Manage and coordinate the administrative aspects of projects to ensure they are completed on time and within budget. Support Project Manager by analyzing data and contributing to overall project strategy and performance evaluation.

  Responsibilities

  • Receive general instruction on key objectives for execution.
  • Receive direction as needed, and especially complex assignments, modified techniques, and new approaches on assignments with conflicting criteria.
  • Work is completed using advanced techniques and principles and is reviewed by more senior staff to ensure application of sound professional judgement.
  • May review work produced by junior staff for quality assurance.
  • At the operational and company level may act as key point of contact for interdepartmental communications for a branch office, Business Unit / Service line.
  • In conjunction with Marketing, may support aspects of proposal preparation and contract pricing.
  • Assist project managers and local / Business Unit management team with revenue projections and budgeting.
  • Act as liaison between the management team and other technical staff, as needed.
  • Proactively communicate with internal and external constituents, acting as administrative point of contact for client.
  • Provide operational support to stakeholders by tracking timelines and ensuring project goals are being met.
  • Provide support in developing and improving internal processes while supporting strategic and tactical planning and execution.
  • May manage platforms and systems related to project development and management of the branch office, Business Unit / Service line.
  • Support principals, project managers, and team leads with planning and executing technical projects, including monitoring project schedules, reporting, cost estimates and budgets, and tracking of team activities.
  • Create and maintain project documentation, including timelines, resource plans, and meeting minutes.
  • Prepare presentations and ongoing status reports.
  • Research, monitor, and analyze data to provide insight and recommend action if necessary.
  • Assist local management team in preparing production schedules and project budgets.
  • Assist in responding to Requests for Proposal (RFP), ensuring compliance with requested requirements.
  • Coordinate multiple projects concurrently.
  • Monitor and communicate project progress and scope to key constituents and adapt to changes.
  • Review all project contractual documents for conformity and quality assurance.
  • May assist Accounting in providing and/or reviewing monthly billing information.
  • Work closely with Accounting to maintain project information in Bowman’s accounting systems.
  • May assist Accounting with collection efforts.
  • Using past metrics, work closely with management and Marketing on proposals and contracts for prospective projects.
  • Work to streamline operational processes through SOPs, software development, etc.

  Skills

  • Ability to work both independently and within a team environment.
  • Ability to effectively communicate with all levels of the organization and external partners.
  • Highly motivated and problem-solving attitude.
  • Strong sense of urgency in responding to constituents.
  • Strong work ethic and commitment to quality.
  • Self-reliance and ability to operate independently with limited direction.
  • Commitment to promoting the reputation of the company through quality of work.
  • Aspirations to grow professionally and advance within the company.
  • Commitment to driving profitability and growth.
  • Commitment to becoming a “citizen” of the broader organization, breaking down barriers and silos.
  • Commitment to working in partnership with others inside and outside the organization.
  • Ability to effectively manage multiple time-sensitive tasks.
  • Thorough understanding of data analysis techniques and deliverables.
  • Excellent written and verbal communication skills, including the ability to summarize conclusions and confidently present well-supported arguments with internal/external stakeholders.
  • Excellent analytical, problem-solving, and time management skills needed to meet deadlines.
  • Ability to synthesize complex information, coordinate and manage multiple projects, and multitask and prioritize deadlines demonstrated by work experience and/or academic record.
  • Ability to compose professional business-related correspondence, accurately proofread documents and read, interpret and understand Civil and Architectural Drawings.
  • Ability to establish and maintain effective relationships.

  Qualifications

  • Bachelor’s degree in business administration or related field preferred, or equivalent commensurate experience.
  • Entry level position, no prior experience required. Any professional experience is a plus.
  • Knowledge of project management from conception to delivery.
  • Proficient in Microsoft Office Suite (Word, Excel, PowerPoint, Outlook) and web browsers (Microsoft Edge and Google Chrome).
  • Proficiency in Adobe and/or Bluebeam a plus.
  • Familiarity with Deltek and PandaDoc a plus.
  • Project Management certification(s) or progress towards such certifications preferred (PMP, CAPM, CSM, CompTIA, etc.).

  Benefits

  • Medical, dental, vision, life, and disability insurance
  • 401(k) retirement savings plan with company match