gtag('config', 'G-6TW216G7W9', { 'user_id': wix.currentUser.id });
top of page

A Day In The Life Of An Engineer II At Kleinfelder

Alan's typical day as an Engineer II at Kleinfelder Inc. involves a mix of remote and in-office work, starting with a status meeting to discuss current assignments. The bulk of the day focuses on "engineering and design," including client consultations and presentations of project alternatives, culminating in formal stakeholder meetings where Alan presents cost analyses and proposed solutions in documents like "L2 scoping documents" to help clients address pipeline and infrastructure issues.

Project Management, Communication, Problem-Solving, Client Interaction, Technical Skills

Advizer Information

Name

Job Title

Company

Undergrad

Grad Programs

Majors

Industries

Job Functions

Traits

Alan Iannaccone

Engineer II

Kleinfelder Inc

University of Portland 2018

N/A

Engineering - Mechanical

Energy & Utilities

Product / Service / Software Development and Management

Scholarship Recipient

Video Highlights

1. Engineer II responsibilities include daily status meetings, design work, and client consultations.

2. A significant portion of the work involves creating and presenting project alternatives and cost analyses to clients in formal stakeholder meetings.

3. Engineers create documentation like operating diagrams and L2 scoping documents to thoroughly explain project details and solutions to clients

Transcript

What does a day in the life of an engineer two look like?

What I do is hop on. Right now, we're doing this work remote thing. I work from home four days a week and am in the office one day.

The day usually starts with a status meeting. We all check in with each other, give a current status of our assignments, and see if there are any bottlenecks or issues holding us up.

After that, I'll go into engineering and design. I'll look at whatever project I'm on and spend most of my day focused on that. In my current position, I do a lot of meeting with the client and consulting with them for many of the projects.

When I wrap up a project, I create a couple of different alternatives for clients to decide on how they want to fix their pipelines and infrastructure. I'll present these to them in a stakeholder meeting.

At stakeholder meetings, which are very formal, I have to present different costs for different alternatives and the layout of each. For example, I'll take an operating diagram, which is like a layout of a station. I'll mark it up and create an L2 scoping document.

This document is like a Word document that tells them everything they need to know about their station, the issues they're facing, and how to fix them. Then I present it. It's a staggered answer, but hopefully, that answers the question.

Advizer Personal Links

Linkedin

bottom of page