Assistant Resident Engineer (ARE)

About the role

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Project schedules monitor budget and progress to maintain adherence to contract requirements on infrastructure projects. Daily construction operations advance as contractors, field staff, and airport operations coordinate activities for on-time project delivery. Requests for information, submittals, contractor payments, and project documentation receive review to verify contract compliance. Field inspectors supervise site activities so quality standards, safety protocols, and contractual obligations remain consistent on infrastructure projects.

Requirements

The posting states a minimum of 10 years of experience.

The posting states a minimum of 25 years of experience.

A Professional Engineer (PE) license prefers this infrastructure role for engineering validation. Contract administration and project documentation knowledge demonstrates strength as mandatory for compliance. On site requires OSHA-30 certification for safety standards on construction sites. Complex inspections prefer ACI Concrete Special Inspector and other construction safety certifications for specialized verification. Documentation and reporting necessitate proficiency with eBuilder and Microsoft Office for record management. Site performance requires a valid driver's license for regional mobility. Airport access requires the ability to obtain a SIDA badge for secure entry. Project demands mandate availability for nights and weekends as needed for project timelines.

Practical notes

This role requires onsite presence at JFK Airport as dictated by project operational needs. Travel may be required between project sites in the region to maintain continuity.

Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Infrastructure roles focus on the construction and maintenance of essential public works to serve community needs. Professionals in this field apply engineering principles to ensure safety, quality, and regulatory compliance in built environments. Common tools include project management software, document control systems, and scheduling platforms to organize workflows. General practices emphasize collaboration with contractors and stakeholders to align project objectives. Roles often require flexible schedules to meet project demands and regulatory standards.

Questions to ask

Worth asking in any interview: how the team measures success, who the role works with daily, what the onboarding looks like, and what the company is trying to achieve this year. Asking what past hires did well is a strong final question. Keep the list short and pick the questions that matter most to you.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.