What is a Software Engineer at Burns & McDonnell?

As a Software Engineer at Burns & McDonnell, you are not just writing code; you are building the digital backbone for critical infrastructure projects that power, connect, and sustain the modern world. Unlike a traditional tech firm where the software is the product, here your work enables complex engineering feats in aviation, power transmission, construction, and environmental services. You will join a 100% employee-owned firm where your contributions directly impact the efficiency and success of multi-million dollar capital projects.

In this role, you will likely sit within a specific Global Practice (such as Transmission & Distribution, Aviation & Federal, or 1898 & Co.) or the corporate IT function. Your responsibilities may range from developing internal automation tools that speed up engineering designs to creating client-facing dashboards for utility management. You will work in a collaborative, multidisciplinary environment alongside civil, mechanical, and electrical engineers, translating their technical needs into robust software solutions.

Getting Ready for Your Interviews

Preparation for Burns & McDonnell requires a shift in mindset compared to standard tech interviews. While technical competence is required, the company places a massive premium on communication skills, cultural fit, and your ability to present complex information clearly.

Presentation Skills – 2–3 sentences describing: This is often the defining factor in their hiring process. You will likely be asked to create and deliver a slide deck about yourself. Interviewers evaluate your ability to structure a narrative, speak confidently to a group, and synthesize your professional history into a compelling story.

Behavioral Alignment & Ownership – 2–3 sentences describing: Because Burns & McDonnell is employee-owned, they look for an "owner's mindset"—accountability, initiative, and long-term thinking. You must demonstrate that you are a self-starter who cares about the company's bottom line and client success, not just a ticket-closer.

Technical Pragmatism – 2–3 sentences describing: Evaluators focus on your ability to apply technology to solve business problems rather than your ability to memorize obscure algorithms. Be prepared to discuss your resume projects in depth, explaining the why and how of your technical choices, and how they served the end-user.

Interview Process Overview

The interview process at Burns & McDonnell is structured, rigorous, and distinctive, often blending modern digital screening with traditional corporate evaluation methods. It typically begins with an asynchronous (pre-recorded) video interview. This stage is automated; you will be prompted with questions on a screen and must record your video responses within a set time limit. This is a filter for communication skills and genuine interest before you ever speak to a human.

If you pass the digital screen, you will move to live interactions, which may include a phone screen with HR or a hiring manager, followed by the "Super Day" or onsite interview (which may be virtual depending on circumstances). The hallmark of the final round is the Personal Presentation. You will present a PowerPoint about your background, education, and projects to a panel of managers and engineers. This is followed by behavioral and technical questions, and often a lunch with the team to assess cultural chemistry in a more relaxed setting.

This timeline illustrates a process that tests your poise as much as your coding ability. The initial asynchronous stage requires you to be comfortable talking to a camera without feedback, while the final stage demands high-level interpersonal skills. You should prepare to sustain your energy through a multi-hour final round that includes presentation, Q&A, and social components.

Deep Dive into Evaluation Areas

The evaluation strategy at Burns & McDonnell is heavily weighted toward finding candidates who are "client-ready" and culturally additive. While you need to be a competent engineer, being a brilliant coder who cannot communicate effectively is usually a disqualifier here.

The Personal Presentation

This is the most unique and critical part of the Burns & McDonnell loop. You will typically be given a prompt to prepare a 10–15 minute PowerPoint presentation about yourself. This is not just an icebreaker; it is a formal assessment of your communication skills.

Be ready to go over:

• Your "Why": A clear narrative of why you chose engineering/software, why you chose your university, and why you want to work at Burns & McDonnell.
• Project Highlights: High-level overviews of 1–2 key projects where you can discuss the technical challenges and your specific contributions.
• Future Goals: Where you see yourself in 5 years and how this role fits that trajectory.

Example questions or scenarios:

• "Walk us through your background and what brings you here today."
• "Present a project you are proud of and explain the technical hurdles you overcame."

Behavioral & Cultural Fit

As an ESOP (Employee Stock Ownership Plan) company, the culture is collaborative and invested. Interviewers use behavioral questions to weed out candidates who prefer to work in isolation or who lack accountability. They want to see that you can work on multidisciplinary teams and handle conflict maturely.

Be ready to go over:

• Conflict Resolution: Specific examples of how you handled disagreements with teammates or managed difficult stakeholders.
• Adaptability: How you handle changing requirements or learning new technologies on the fly.
• Safety & Integrity: A commitment to quality and safety, which is paramount in the engineering and construction industry.

Example questions or scenarios:

• "Tell me about a time you had a conflict with a team member. How did you resolve it?"
• "Describe a situation where you had to learn a new technology quickly to meet a deadline."

Technical Competency

Technical interviews here are generally less focused on LeetCode-style brain teasers and more focused on your practical experience and resume. They want to verify that you actually know the technologies you listed and that you understand fundamental engineering principles.

Be ready to go over:

• Resume Deep Dives: Be prepared to explain every line of code or tool mentioned on your CV.
• Object-Oriented Programming (OOP): Core concepts like inheritance, polymorphism, and encapsulation.
• Database & Systems: Basic SQL queries, API design, and how different software components interact.

Example questions or scenarios:

• "Explain the difference between an abstract class and an interface."
• "How would you design a database schema for [specific engineering scenario]?"

Key Responsibilities

Software Engineers at Burns & McDonnell are often tasked with bridging the gap between raw data and engineering decisions. You will design, develop, and implement software applications that may be used internally to automate complex calculations or externally by clients to monitor assets. This involves the full software development lifecycle (SDLC), from gathering requirements with non-technical stakeholders to testing and deployment.

Collaboration is a daily reality. You will frequently work with electrical, civil, or mechanical engineers who act as your subject matter experts. Your job is to translate their physical infrastructure needs into digital logic. This might involve working with GIS data, SCADA systems, or building web applications that visualize project progress. You are also expected to participate in code reviews, maintain documentation, and adhere to the company’s quality standards.

Role Requirements & Qualifications

Candidates who succeed at Burns & McDonnell generally possess a blend of solid technical foundations and professional maturity.

• Technical Skills: Proficiency in languages such as C#, .NET, Python, or Java is standard. Experience with SQL and database management is frequently required. Familiarity with cloud platforms (Azure/AWS) and modern web frameworks (React/Angular) is increasingly important.
• Experience Level: For entry-level or "Assistant" roles, a relevant degree (Computer Science, Computer Engineering, or related ABET-accredited program) and internship experience are key. For experienced roles, a track record of delivering full-stack solutions in a corporate environment is expected.
• Soft Skills: Exceptional verbal and written communication skills are non-negotiable. You must be able to explain technical concepts to non-technical engineers and clients.
• Nice-to-have vs. Must-have:
  • Must-have: A "team-first" attitude, strong presentation skills, and core programming competency.
  • Nice-to-have: Experience in the engineering, construction, or utility industries (EPC experience); knowledge of GIS (Geographic Information Systems); EIT/FE certification (rare for pure software, but valuable in this hybrid environment).

Common Interview Questions

The following questions are drawn from candidate data and reflect the company's focus on behavior and practical experience. While you cannot predict every question, preparing for these categories will cover the majority of what you will face.

Behavioral & Values

These questions assess your "owner mindset" and ability to work within the Burns & McDonnell culture.

• "Why do you want to work for Burns & McDonnell specifically?"
• "Tell me about a time you made a mistake. How did you handle it?"
• "Describe a time you had to juggle multiple deadlines. How did you prioritize?"
• "What does diversity and inclusion mean to you?"
• "Tell me about a time you demonstrated leadership."

The Presentation & Resume

Expect questions that probe the details of the presentation you deliver.

• "You mentioned using [Technology X] in your project. Why did you choose that over [Technology Y]?"
• "What was your specific contribution to this group project versus what the team did?"
• "How would you improve this project if you had to do it again today?"

Technical & Practical

Questions here verify your foundational knowledge and problem-solving approach.

• "What are the four pillars of Object-Oriented Programming?"
• "Explain the difference between == and .equals()."
• "How do you handle error handling and logging in your applications?"
• "Describe a challenging technical bug you encountered and how you debugged it."
• "Basic database questions (e.g., types of joins, normalization)."

These questions are based on real interview experiences from candidates who interviewed at this company. You can practice answering them interactively on Dataford to better prepare for your interview.

Frequently Asked Questions

Q: How long does the interview process take? The timeline can vary significantly. Some candidates report a process of 2–3 weeks, while others experience gaps of a month or more between the digital screen and the onsite. Be patient, but proactive in following up.

Q: Is the "Asynchronous Video Interview" really important? Yes. It is the primary gatekeeper. Many candidates are rejected at this stage. Treat it like a real conversation: dress professionally, ensure good lighting, and use the preparation time for each question wisely before recording.

Q: What is the dress code for the interview? Burns & McDonnell is a professional services firm with a more traditional corporate culture than Silicon Valley. Business professional attire (suit and tie or equivalent) is strongly recommended for the onsite/final presentation to show respect and seriousness.

Q: Will I be asked to write code on a whiteboard? It is less common than at big tech firms. While you might be asked to talk through logic or write pseudo-code, the focus is usually on your past projects and conceptual understanding rather than live coding syntax. However, be prepared just in case.

Q: What is the "Lunch Interview"? If you are invited onsite (or sometimes virtually), you may have lunch with younger associates. While this feels casual, it is absolutely part of the evaluation. They are assessing if they would enjoy working with you every day. Keep it professional.

Other General Tips

• Research the Employee Ownership Model: Burns & McDonnell is proud of being an ESOP. Understanding what this means and asking intelligent questions about it (e.g., "How does employee ownership influence decision-making here?") demonstrates deep interest and cultural alignment.
• Master the STAR Method: For every behavioral question, structure your answer with Situation, Task, Action, and Result. This prevents rambling and ensures you highlight your specific contributions.
• Know Your Audience: Your interview panel may include engineers from non-software disciplines. Practice explaining your technical projects in a way that emphasizes business value and logic, rather than just jargon.
• Prepare Questions: At the end of interviews, ask insightful questions about the team's current challenges, the training process for new hires, or the company's long-term vision. This shows engagement.

Summary & Next Steps

Interviewing for a Software Engineer role at Burns & McDonnell is a unique experience that prioritizes your ability to communicate and collaborate just as much as your ability to code. You are applying to join a firm where you will be an owner, and the interview process is designed to find individuals ready to take on that responsibility. The combination of a digital screening followed by a formal presentation allows you to showcase your full professional profile.

To succeed, focus heavily on your Personal Presentation. This is your greatest opportunity to control the narrative and demonstrate your value. Pair this with a solid grasp of your resume's technical details and a polished, professional demeanor. If you approach the process with preparation and genuine enthusiasm for the company's mission, you will stand out as a strong candidate.

The compensation at Burns & McDonnell often includes a competitive base salary, but the real differentiator is the benefits package, specifically the Employee Stock Ownership Plan (ESOP) and potential bonuses. When evaluating an offer, consider the long-term value of stock accumulation and profit-sharing, which can be significant compared to base salary alone. Be sure to ask HR to explain how the total compensation package vests and grows over time.