What Young Engineers Should Ask Their Managers During Their First Five Years


What Young Engineers Should Ask Their Managers During Their First Five Years

The first five years of an engineering career are important.

This is when young engineers build technical skills, learn how projects really work, develop professional habits, and begin to understand what kind of engineer they want to become.

But growth does not happen automatically.

You can work hard, complete assignments, attend meetings, and still miss opportunities to learn if you never ask the right questions. Your manager plays an important role in your development, but they may not always know what you are thinking, what you want to learn, or where you feel uncertain.

That is why young engineers should learn how to ask better questions.

Good questions show initiative. They help you understand expectations. They make feedback easier. They also help your manager see that you are serious about growing, not just getting through the week.

Here are the questions young engineers should ask their managers during their first five years.

What Skills Should I Focus on Developing Next?

Early in your career, it can feel like everything matters.

You may be trying to improve technical knowledge, software skills, writing, field judgment, communication, project management, and client interaction all at the same time.

That is normal, but it can also be overwhelming.

Ask your manager what skills would be most valuable for you to develop next. This helps you focus your effort where it will have the greatest impact.

You might ask:

“What are the two or three skills I should focus on improving this year?”

“Based on the work I am doing now, what would help me become more useful to the team?”

“What technical areas should I strengthen if I want to take on more responsibility?”

This kind of question shows that you are thinking about development, not just task completion.

It also helps you avoid guessing. Your manager may see gaps or opportunities that you do not see yet.

What Does Good Work Look Like for This Assignment?

Young engineers sometimes receive an assignment and immediately start working without fully understanding what success looks like.

That can lead to frustration.

You may spend too much time on details that do not matter, miss the real purpose of the task, or produce something that needs major revisions because expectations were not clear at the beginning.

Before starting an assignment, ask what good work looks like.

For example:

“What level of detail are you looking for?”

“Is this a quick internal review or something that may go to the client?”

“Are you looking for a rough first pass or a polished draft?”

“What should I be most careful about on this task?”

These questions can save time and improve quality.

They also show that you understand an important professional lesson: different assignments require different levels of effort, polish, and review.

A trusted engineer does not just complete work. A trusted engineer understands the purpose of the work.

Check out this video about great career advice.

What Should I Do Differently Next Time?

Feedback is one of the fastest ways to grow, but many young engineers wait for feedback instead of asking for it.

After a report, calculation, drawing, presentation, field visit, or client meeting, ask your manager what you should do differently next time.

This is a simple but powerful question.

It shifts the conversation from “Was this good or bad?” to “How do I improve?”

You might ask:

“What is one thing I should improve before the next submittal?”

“Were there any issues in my draft that I should watch for in the future?”

“What would you have done differently?”

“Is there anything I missed that an experienced engineer would have noticed?”

Do not take every comment personally. Review comments, edits, and corrections are part of the learning process.

The goal is not to avoid feedback. The goal is to use feedback to become better.

Am I Communicating Enough, Too Much, or Not Clearly Enough?

Communication is one of the most important skills for young engineers, and one of the easiest to misjudge.

Some engineers communicate too little. They work quietly, run into problems, and wait until someone asks for an update.

Other engineers communicate too much. They send long messages, include unnecessary details, or ask questions before organizing their thoughts.

The best approach depends on the manager, project, client, and assignment.

Ask your manager what they prefer.

For example:

“How would you like me to keep you updated on this project?”

“Would you prefer quick status emails, scheduled check-ins, or updates when something changes?”

“Am I giving you the right level of detail?”

“When I run into a problem, how much should I try to resolve before bringing it to you?”

These questions help you become easier to manage and more effective on project teams.

Good communication reduces uncertainty. It helps managers plan, prevents surprises, and builds trust.

What Should I Learn About How Projects Are Managed?

Engineering is technical work, but it happens inside projects.

Projects have budgets, schedules, scopes, deliverables, contracts, clients, risks, and deadlines. Young engineers who understand this context become more valuable because they see how their work fits into the bigger picture.

Ask your manager to help you understand the project side of engineering.

You might ask:

“How was this project scoped?”

“What are the main budget or schedule risks?”

“What does the client care about most?”

“What are the key deliverables?”

“How do we know if this project is going well?”

These questions help you move beyond task-level thinking.

Instead of only asking, “What do I need to do?” you begin asking, “Why does this work matter, and how does it affect the project?”

That is a major step in professional growth.

What Meetings or Conversations Should I Sit In On?

Not all learning happens through assigned tasks.

Some of the best learning happens when you listen to experienced engineers talk through problems, explain decisions, respond to clients, negotiate scope, review risk, or handle difficult conversations.

Ask your manager if there are meetings you can observe.

For example:

“Would it be helpful for me to sit in on the client meeting so I can understand the project background?”

“Can I join the design review even if I am not presenting?”

“Would it be okay if I listened to the contractor coordination call?”

“Are there project meetings I should attend to better understand how decisions are made?”

You do not need to speak in every meeting. Sometimes your job is to listen, take notes, and learn.

Over time, you will understand how experienced engineers communicate, what questions they ask, and how they handle uncertainty.

That kind of exposure is hard to get from textbooks or training courses.

How Can I Take More Ownership?

At some point, every young engineer needs to move from completing assigned tasks to owning pieces of work.

That transition does not always happen automatically. You may need to ask for opportunities.

A good question is:

“What is something I can take more ownership of on this project?”

This might mean managing a small deliverable, coordinating with a vendor, preparing a meeting agenda, tracking action items, leading a technical memo, or handling a specific part of a client update.

Ownership does not mean you work without guidance. It means you are responsible for moving something forward.

You track it. You ask questions. You follow up. You communicate progress. You make sure it does not get forgotten.

Managers notice when young engineers take ownership. It is one of the clearest signs that someone is ready for more responsibility.

What Mistakes Should I Watch Out for at This Stage of My Career?

Every stage of an engineering career has common mistakes.

In the first few years, young engineers may underestimate the importance of documentation, fail to check their work carefully, communicate too late, avoid asking questions, focus only on technical details, or miss the business context of a project.

Ask your manager what mistakes you should watch for.

For example:

“What are common mistakes you see engineers make at my experience level?”

“What should I be careful not to overlook?”

“What habits should I build now that will help me later?”

“What habits should I avoid?”

This question can lead to practical advice that you might not get in a formal review.

It also shows humility. You are not assuming you already know everything. You are asking how to grow responsibly.

How Should I Prepare for the PE License?

If you have not yet earned your PE license, your first five years are the time to prepare.

Ask your manager how your current work experience relates to licensure. Ask what kinds of projects, responsibilities, and technical exposure will help you become a stronger PE candidate.

You might ask:

“What experience should I try to get before applying for the PE exam?”

“Are there project types I should be involved in to broaden my experience?”

“What should I be documenting now for future licensure?”

“How did you prepare for the PE exam?”

Your PE license is more than an exam. It represents professional responsibility, judgment, ethics, and competence.

A good manager can help you think beyond simply passing the test and toward becoming a licensed professional who is ready for greater responsibility.

What Continuing Education Would Help Me Grow?

Continuing education is often discussed as a PE license renewal requirement, but it can be valuable before and after licensure.

Young engineers should use training, webinars, technical courses, internal lunch-and-learns, professional society events, and PDH courses strategically.

Ask your manager what continuing education would help you.

For example:

“Are there technical courses you recommend for the type of work we do?”

“Should I focus on codes and standards, design methods, project management, or communication skills?”

“Are there topics that would make me more useful on future projects?”

“Would this course help me develop in the direction the team needs?”

This helps you choose learning opportunities that support your career, not just your resume.

The best continuing education closes real knowledge gaps and prepares you for the next level of responsibility.

What Would Make You More Comfortable Giving Me More Responsibility?

This may be the most direct question on the list.

If you want more responsibility, ask what it will take.

You might say:

“I would like to take on more responsibility over time. What would you need to see from me to feel comfortable with that?”

This question can lead to very useful feedback.

Your manager may tell you to improve communication, check your work more carefully, build technical depth, become more consistent with deadlines, understand project budgets, or show more confidence in meetings.

That feedback may not always be easy to hear, but it gives you a roadmap.

Young engineers often wonder why they are not being trusted with more. Sometimes the answer is simple: no one has explained what they need to demonstrate next.

Ask the question.

Then act on the answer.

How Am I Doing Overall?

Formal performance reviews are useful, but they often happen only once or twice a year. That is not enough feedback for a young engineer who wants to grow quickly.

Ask for informal feedback throughout the year.

For example:

“Can I get a quick check-in on how I am doing?”

“Are there any areas where I am falling short of expectations?”

“What progress have you seen, and where should I focus next?”

“Is there anything you wish I were doing differently?”

These conversations do not need to be long. Even a ten-minute check-in can help you correct course before small issues become bigger problems.

Regular feedback helps you grow with less guesswork.

How to Ask Without Sounding Needy

Some young engineers hesitate to ask these questions because they do not want to seem insecure or high-maintenance.

The key is to ask professionally and at the right time.

Do not interrupt your manager constantly. Do not ask vague questions when everyone is rushing to meet a deadline. Do not expect a full career development discussion in the middle of a project crisis.

Instead, pick appropriate moments.

You can ask during a one-on-one meeting, after a project milestone, during a performance check-in, or when starting a new assignment.

Keep the tone practical:

“I want to make sure I am developing in the right direction.”

“I would appreciate your feedback on how I can improve.”

“I want to take more ownership, and I would like to understand what I need to demonstrate.”

Most managers appreciate young engineers who show initiative, self-awareness, and a willingness to improve.

Bottom Line

The first five years of an engineering career are a critical learning period.

You are building technical skills, professional habits, communication skills, project awareness, judgment, and confidence. Your manager can help you grow, but you need to take an active role in the process.

Ask what skills to develop. Ask what good work looks like. Ask for feedback. Ask how to communicate better. Ask how projects are managed. Ask to observe important meetings. Ask how to take more ownership. Ask what mistakes to avoid. Ask how to prepare for licensure and continuing education. Ask what would make your manager comfortable giving you more responsibility.

These questions do more than help you get answers.

They show that you care about becoming a better engineer.

And that is exactly the kind of professional people want to invest in.

Jordan

Engineering education specialist at PDH-Pro. Creating clear, practical continuing education content for licensed engineers.

Recent Posts