Jobs · Engineering · New York

Entry Level Civil/Wastewater Engineers - Hiring Event with AECOM - New York

AECOM · New York, NY · 1 mo ago
HybridEngineering$75k–$90k/yrFull-time
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use
  • for any list of duties/requirements/benefits, and

    for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

    or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Key content: Company Description: "Work with Us. Change the World. At AECOM, we're delivering a better world..." etc. This is company description. Should we include a section? Possibly "About the role" or "Company Description"? The instructions say use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include "About the role" heading for description of role? Or maybe "About AECOM"? But they gave examples; we can choose appropriate headings based on content. We have: - Job Description: AECOM is hosting an exclusive, invitation-only hiring event in New York, New York October 15th and 16th. This is a great opportunity to learn and connect with AECOM for career opportunities starting Spring/Summer 2027. The event kicks off on Thursday evening with a networking mixer from 6-8 pm, where you can hear from AECOM staff about various projects, career paths, and the company itself. You’ll also have the chance to meet other students, recent graduates, and AECOM professionals from across our business lines. On Friday, interviews will take place at our New York office. This is a fantastic opportunity to learn about and connect with AECOM for early career opportunities. AECOM is seeking a motivated Civil/Water Resources Engineer to join our team in the Bloomfield, NJ office. This is an entry-level opportunity for a recent graduate interested in developing a career in water resources, stormwater management, and civil engineering. The ideal candidate is eager to learn, collaborative, client-focused, and ready to contribute to a variety of water resource projects. This position is expected to begin in May/June 2027. - Responsibilities: list bullet points. - Qualifications: Minimum Requirements and Preferred Requirements. - Additional Information: Relocation assistance not available, sponsorship not available, posting for current vacancy, intend to fill no sooner than June 1 2027, onboarding requirement, offered rate based on education etc. The range for this position is $75000 to $90000. - About AECOM: description of benefits etc. - What makes AECOM a great place to work: bullet-ish paragraphs. - Compensation line: USD 75000 - USD 90000 - yearly. We need to decide sections. We have substantive content for: - About the role (maybe combine job description and event details). Could be "About the role" heading. - Responsibilities: definitely. - Qualifications: definitely (maybe combine Minimum and Preferred). - Skills: maybe we can extract from qualifications: "Strong analytical, problem-solving, written, and verbal communication skills. Ability to work effectively both independently and as part of a team." Could be a Skills section. - Benefits: The posting mentions benefits in "About AECOM" and "What makes AECOM a great place to work". It lists medical, dental, vision, life, AD&D, disability benefits, paid time off, leaves of absences, voluntary benefits, perks, flexible work options, well-being resources, employee assistance program, business travel insurance, service recognition awards, retirement savings plan, employee stock purchase plan. Also training and development programs, award-winning training, etc. So we have benefits content. - Pay: The posting explicitly states salary range $75000 to $90000. So we should include Pay section. - Schedule: Not explicitly mentioned; there is mention of hybrid work model? At bottom: "Work Location Model: Hybrid". That's schedule? It's location model, not schedule. No explicit schedule like full-time, part-time, hours. So we should not create Schedule section unless posting actually states them. It does not state schedule (like full-time). So omit. - Also we have event details (hiring event). Could be part of About the role or separate section like "Hiring Event". But instructions only list certain headings; we could still create other headings if needed? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Probably we should stick to those headings where applicable. The event details could be part of About the role. We need to preserve all substantive information. So we need to include event details, location (Bloomfield, NJ office), start date (May/June 2027), etc. We need to avoid boilerplate: EEO, equal-opportunity, scam-warning, cookie/navigation/legal, duplicated lines, application instructions. Also remove "ReqID: J10158610 Business Line: Water Business Group: DCS Strategic Business Unit: East Career Area: Engineering Work Location Model: Hybrid Compensation: USD 75000 - USD 90000 - yearly". We already have compensation; we can keep compensation but not the metadata. The work location model hybrid could be mentioned maybe in About the role or Benefits? It's not a benefit but location model. Could be included in About the role as note. We need to avoid duplication: The posting repeats some content (like AECOM description). We'll keep unique. Now produce HTML. Structure:

    About the role

    ... (company description? Actually about the role includes event details, position description, location, start date). We'll combine. Maybe:

    About the role

    AECOM is hosting an exclusive, invitation-only hiring event in New York, NY on October 15‑16, 2027. The event begins with a networking mixer Thursday evening (6‑8 pm) followed by interviews Friday at the New York office. AECOM is seeking a motivated Civil/Water Resources Engineer to join the Bloomfield, NJ office in an entry‑level role focused on water resources, stormwater management, and civil engineering. The position is expected to start in May/June 2027.

    Then Responsibilities:

    Responsibilities

    • Apply fundamental engineering principles and standard procedures to support the design and analysis of civil and water resources projects.
    • Assist with stormwater modeling, hydrologic and hydraulic analyses, and drainage design using tools such as GIS, HEC‑HMS, and HEC‑RAS.
    • Develop and modify engineering drawings, plans, profiles, sections, and details using Autodesk Civil 3D.
    • Support floodplain management studies and other water resources projects through hydrologic and hydraulic modeling and analysis.
    • Perform engineering calculations and assist with the preparation of technical reports, exhibits, figures, and other project deliverables.
    • Assist project teams with data collection, analysis, design development, and preparation of construction documents.
    • Apply engineering concepts learned through coursework, internships, and academic projects to real‑world engineering challenges.
    • Work closely with project managers, senior engineers, and multidisciplinary teams to complete project assignments.
    • Develop an understanding of engineering standards, regulations, and professional and ethical responsibilities.
    • Communicate effectively with team members and contribute to a collaborative project environment.
    Qualifications: Could split into Minimum Requirements and Preferred Requirements under Qualifications heading, maybe using
      for each.

      Qualifications

      Minimum Requirements:

      • Bachelor’s degree in Civil Engineering, Environmental Engineering, Water Resources Engineering, or a related field.

      Preferred Requirements:

      • Familiarity with basic hydrology, hydraulics, stormwater management, and civil engineering principles.
      • Experience with or coursework involving Civil 3D, GIS, HEC‑RAS, HEC‑HMS, or similar engineering software is a plus.
      • Strong analytical, problem‑solving, written, and verbal communication skills.
      • Ability to work effectively both independently and as part of a team.
      • Interest in pursuing a career in water resources and civil engineering.
      • EIT certification or plans to pursue the FE/EIT is preferred.
      Skills: Could be separate but we already included some in qualifications. Might be redundant. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine Skills into Qualifications. But we already have Qualifications covering both minimum and preferred. The skills like analytical etc are already there. So we may not need separate Skills section. Benefits: We have benefits info from About AECOM and What makes AECOM a great place to work. We'll combine.

      Benefits

      • Medical, dental, vision, life, AD&D, disability benefits
      • Paid time off and leaves of absence
      • Voluntary benefits and perks
      • Flexible work options
      • Well‑being resources and employee assistance program
      • Business travel insurance
      • Service recognition awards
      • Retirement savings plan
      • Employee stock purchase plan
      • Award‑winning training and development programs to expand technical expertise and leadership skills
      Pay: We have salary range.

      Pay

      The offered rate of compensation will be based on individual education, qualifications, experience, and work location. The range for this position is $75,000 to $90,000 per year.

      We should not include Schedule. We also need to include maybe location model hybrid? Could be included in About the role or Benefits? It's not a benefit but work arrangement. Could add a sentence in About the role: "The role follows a hybrid work model." But we need to preserve all substantive information. The posting includes "Work Location Model: Hybrid". So we should include that. Add to About the role: "The position follows a hybrid work model." Also note about relocation assistance not available, sponsorship not available, onboarding requirement, start date no sooner than June 1 2027. These are substantive. Should we include them? They are under Additional Information. We should preserve them. Where to place? Could be in About the role or a separate section like "Additional Information". But we only have prescribed headings; we could add a

      Additional Information

      if we want, but instructions only gave examples; not forbidden. However they said "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies we should use those headings for sections; but we could also use other headings if needed? Safer to stick to those headings. Where to put relocation assistance, sponsorship, onboarding, start date constraints? Could

Similar jobs