Burns & McDonnell logo
Burns & McDonnellSoftware Engineer
Updated · Reviewed by the Dataford team

Burns & McDonnell Software Engineer interview questions & guide 2026

Every question Burns & McDonnell interviewers actually ask, the frameworks that win the room, and the language hiring managers respond to.

4 rounds · ≈ 3-5 weeks
1
Asynchronous Screen
2
Direct Conversations
3
Live Panel Interview
4
Team Interaction

What is a Software Engineer at Burns & McDonnell?

A Software Engineer at Burns & McDonnell plays a pivotal role in delivering technology solutions that support large-scale infrastructure, energy, environmental, and facility engineering projects. Unlike purely consumer-facing tech firms, Burns & McDonnell operates as a 100% employee-owned engineering and architecture giant. In this environment, software engineers build internal tools, data pipelines, client-facing dashboards, and specialized applications that power critical engineering workflows across various global practices.

In this position, your work directly impacts how multi-disciplinary teams plan, design, and execute complex capital projects. Whether you are automating workflows for substation design, building enterprise web applications, or engineering algorithms for field data collection, your technical contributions streamline operations and improve safety, accuracy, and efficiency. The software solutions you build bridge the gap between traditional engineering disciplines and modern computer science practices.

What makes the Software Engineer role at Burns & McDonnell compelling is the combination of tangible real-world impact and a distinct employee-ownership culture. You are not just writing code for abstract features; you are directly contributing to the growth and operational excellence of a firm where every team member is an owner. Expect a collaborative environment where strong interpersonal skills and domain interest are valued alongside technical capability.

Common Interview Questions

The interview questions at Burns & McDonnell are designed to evaluate your background, communication skills, career motivations, and practical problem-solving capabilities. Questions are drawn from real candidate experiences and may vary slightly depending on the specific team, location, or seniority level. Rather than testing abstract algorithmic puzzles, the evaluation focuses heavily on your work history, team collaboration, and alignment with company values.

Behavioral & Background Questions

These questions assess your work history, how you manage project challenges, and your ability to work within a multi-disciplinary team structure.

  • Tell me about yourself, your educational background, and your past work experience.
  • Can you share an example of a time you handled a team conflict during a project and how you resolved it?

Access the full Burns & McDonnell Software Engineer prep plan

  • Every Software Engineer question, updated weekly
  • Model answers with full code walkthroughs
  • Recent, real interview reports
Get my prep plan
03 · Question bank

The questions most likely to come up

Sorted by relevance to this company
Web, Databases, and Cloud ExperienceMedium
Assesses your hands-on experience with core web and data infrastructure components.
cloud infrastructuredatabases
Recently asked
Testing and Debugging QualityMedium
Assesses your engineering practices for testing, debugging, and quality at scale.
code qualityDebuggingTesting
Recently asked
Access the full Burns & McDonnell Software Engineer prep plan
Everything you need to walk in ready.
Get my prep plan

Getting Ready for Your Interviews

Preparing for an interview at Burns & McDonnell requires a balanced focus on technical fundamentals, clear articulation of past experiences, and strong interpersonal delivery. Because the hiring team evaluates your potential as a future employee-owner, how you present your ideas and interact with team members is just as important as your technical skill set.

Role-Related Knowledge – Demonstrating solid knowledge of software development principles, database management, and object-oriented programming is essential. Interviewers look at how well you understand the practical software development life cycle rather than asking hyper-theoretical algorithm questions. You can showcase strength here by discussing real projects you have built, detailing the frameworks used and technical trade-offs made.

Communication & Presentation Skills – Clear, articulate verbal and presentation skills are heavily scrutinized during the hiring process. Candidates are frequently asked to deliver a presentation on their background, education, and career vision. You demonstrate strength by structuring your ideas logically, maintaining strong eye contact, and presenting complex technical concepts in an approachable, engaging manner.

Problem-Solving & Initiative – Teams value self-starters who take ownership of challenges and drive solutions. Evaluation focuses on your analytical approach when navigating project constraints, bug fixes, or new feature requests. You can show strength by highlighting instances where you proactively identified workflow bottlenecks, integrated new tools, or solved complex problem scenarios.

Culture Fit & Collaboration – As an employee-owned firm, Burns & McDonnell seeks candidates who display humility, adaptability, and strong teamwork habits. Interviewers assess whether you will integrate seamlessly into cross-functional project teams and uphold company values. Demonstrate strength by sharing detailed examples of successful group projects, showing genuine interest in the company's business model, and actively engaging during informal team settings like lunch meetings.

Interview Process Overview

The recruitment process for a Software Engineer at Burns & McDonnell is structured, personal, and heavily focused on evaluating communication, cultural fit, and practical experience. While specific steps may adapt based on location, office practice, or candidate seniority, the progression follows a distinct and predictable trajectory.

The initial stage typically involves an asynchronous pre-recorded video interview or a phone screen with a university/corporate recruiter. The asynchronous screen presents pre-determined prompts on a digital portal where you record video responses under time limits. Following a successful initial screen, candidates move into direct conversations with department managers or technical leads via Microsoft Teams to discuss resume details, team alignment, and position expectations.

The final stage usually consists of a live panel interview, which can occur virtually or onsite at a regional office (such as Kansas City, Houston, Chicago, or Atlanta). A hallmark of this round is a candidate-led presentation where you spend 10 to 15 minutes presenting your background, education, key projects, and career goals to hiring managers and team engineers. In many regional offices, this onsite evaluation includes campus tours and an informal lunch with team members to assess personal fit and offer candid insight into daily life at the company.

06 · The loop

The interview process, end to end

≈ 3-5 weeks · 4 rounds
1
Asynchronous Screen

Candidates complete a pre-recorded video interview or phone screen with a recruiter, responding to predetermined prompts.

2
Direct Conversations

Successful candidates engage in discussions with department managers or technical leads via Microsoft Teams about their resume and team alignment.

3
Live Panel Interview

Candidates present their background and career goals in a 10 to 15-minute session to hiring managers and team engineers, either virtually or onsite.

4
Team Interaction

Onsite evaluations may include campus tours and informal lunches with team members to assess cultural fit.

The visual timeline above outlines the standard progression from initial screening through to the final onsite panel and team interaction. Candidates should use this roadmap to pace their preparation, ensuring they dedicate sufficient time early on to draft their candidate presentation slides alongside practicing behavioral STAR stories. Note that candidates in certain international offices or specialized tracks may also encounter preliminary technical aptitude tests prior to live interview rounds.

Deep Dive into Evaluation Areas

To excel across all rounds at Burns & McDonnell, you must understand the specific competencies hiring managers evaluate. The interview process is designed to assess your technical versatility, presentation abilities, and collaborative mindset in a professional engineering environment.

Presentation & Communication Skills

Effective communication is critical because software engineers at Burns & McDonnell frequently interact with non-technical project managers, internal engineering clients, and business stakeholders. Hiring managers want to verify that you can articulate complex ideas simply, structure formal presentations cleanly, and convey enthusiasm for your work.

Be ready to go over:

  • Structured Presentation Delivery – Designing a 10–15 minute PowerPoint covering your background, key technical achievements, and career vision.

Access the full Burns & McDonnell Software Engineer prep plan

  • Every Software Engineer question, updated weekly
  • Model answers with full code walkthroughs
  • Recent, real interview reports
Get my prep plan
08 · Topic breakdown

What they actually test for

Weighting based on 278 reported loops
Topic distribution
All topics
Behavioral/Personality QuestionsCommunication Skills (Verbal Delivery)Pre-recorded Video InterviewsStructural Engineering Concepts (Domain)Power Systems Fundamentals

Key Responsibilities

As a Software Engineer at Burns & McDonnell, your daily responsibilities center around building, updating, and maintaining application systems that support large engineering projects and business operations. You work within cross-functional teams alongside structural, electrical, civil, and mechanical engineers, translating business and engineering requirements into clean, scalable software tools.

Your primary deliverables include developing web applications, backend services, database architectures, and automation scripts. On a typical day, you might write code in languages like C# (.NET), Java, Python, or JavaScript/TypeScript, conduct code reviews, write unit tests, and troubleshoot production software issues. You are also involved in requirement gathering sessions with internal business practices to identify pain points in current workflows.

In addition to pure development, you collaborate closely with project managers and department leadership to estimate project timelines, contribute to architectural reviews, and present software solutions to internal stakeholders. You will participate in continuous improvement initiatives, keeping team standards aligned with modern software engineering practices while learning domain knowledge related to energy, infrastructure, and construction management.

Role Requirements & Qualifications

To be competitive for a Software Engineer position at Burns & McDonnell, candidates need a solid foundation in computer science principles, strong project experience, and excellent interpersonal skills.

  • Must-have technical skills – Strong proficiency in at least one major programming language (such as C#, Java, Python, or C++), foundational knowledge of object-oriented programming, experience with relational databases (SQL Server, PostgreSQL, or MySQL), and familiarity with modern web development frameworks.
  • Must-have soft skills – Clear oral and written communication skills, confident presentation abilities, demonstrated teamwork habits, and an active problem-solving initiative.
  • Nice-to-have technical skills – Experience with cloud platforms (Microsoft Azure or AWS), container technologies (Docker, Kubernetes), automated testing frameworks, CI/CD tools, or GIS/engineering-related dataset integrations.
  • Experience level & background – A Bachelor’s degree in Computer Science, Software Engineering, Computer Engineering, or a related field. Roles range from entry-level/new graduate positions to experienced senior roles, with candidates showing relevant internship or industry project experience.

Frequently Asked Questions

Q: How technical is the interview process for a Software Engineer at Burns & McDonnell? A: The interview process relies less on abstract algorithm puzzles and more on practical engineering concepts, past project discussions, and soft skills. Interviewers want to understand your real-world coding projects, design approaches, database knowledge, and how effectively you communicate technical details.

Q: What is expected during the candidate presentation in the final round? A: You are expected to prepare a 10 to 15 minute slide presentation covering your personal background, education, relevant technical projects, leadership activities, and why you want to join Burns & McDonnell. Treat this as a formal presentation to showcase your structure, technical expertise, and public speaking skills.

Q: How should I approach the pre-recorded video interview screening? A: Prepare concise, structured behavioral responses using the STAR method (Situation, Task, Action, Result) before starting the recording. Take advantage of the preparation time provided for each question, speak clearly into your microphone, dress professionally, and maintain direct eye contact with the camera.

Q: What is the company culture like at Burns & McDonnell? A: As a 100% employee-owned firm, the culture emphasizes high accountability, pride in work quality, collaboration, and social camaraderie. Team members are friendly and supportive, and interviews often include casual interactions like office tours and team lunches to see how well you fit into the group dynamic.

Q: How long does the entire interview process take from application to offer? A: The overall timeline usually ranges between 3 to 6 weeks, depending on office location, holiday schedules, and requisition urgency. Communication is typically straightforward following live panel rounds, though pre-recorded screening reviews can occasionally take a couple of weeks to process.

Other General Tips

  • Master the Candidate Presentation: Treat your PowerPoint presentation as a core deliverable. Structure it cleanly, keep slides visually uncluttered, practice your timing, and use it to highlight your passion for technology and engineering solutions.
  • Structure Behavioral Answers with STAR: Practice telling clear stories about past team projects, initiative, and conflict resolution using Situation, Task, Action, and Result format to keep your responses focused and impactful.
  • Emphasize Communication & Social Skills: Burns & McDonnell values sociable, articulate engineers who work well in teams. Engage warmly during panel discussions, campus tours, and informal team lunches.
  • Research the Employee-Ownership Model: Take time to understand how the ESOP (Employee Stock Ownership Plan) works and express genuine interest in contributing to a company where employees share directly in organizational success.
  • Prepare Thoughtful Questions for Interviewers: Ask detailed questions about team workflows, current technology stack initiatives, cross-disciplinary project collaboration, and career development opportunities.

Summary & Next Steps

Targeting a Software Engineer position at Burns & McDonnell offers a unique opportunity to apply modern software engineering skills to world-class infrastructure and energy projects while enjoying the benefits of an employee-owned corporate culture. Success in the hiring process requires showing both software craftsmanship and strong interpersonal delivery. By mastering your behavioral stories, practicing your candidate presentation, and demonstrating a collaborative mindset, you can position yourself as an outstanding candidate.

Focus your preparation efforts on polishing your communication skills, reviewing core software engineering concepts, and articulating your past project contributions with clarity. Prepare thoroughly for each round—from the initial pre-recorded screen to the final live panel and team interaction—and demonstrate why you are ready to contribute as a future employee-owner. To dive deeper into interview strategies, explore candidate experience reports, and access comprehensive practice materials, visit Dataford for additional prep resources tailored to top engineering firms.

14 · Compensation

What this role pays

116 reports
USUSD
Estimated total compHigh confidence · 116 data points
$0k-$0k
Median $88k / year
Base salary · 100%Stock (RSU) · 0%Cash bonus · 0%
25thEntry / smaller markets
$2k
50thTypical offer
$88k
90thTop performers / major metros
$175k
Breakdown by component
Base salary
100% of total
$2k$109k
$55k
median
Stock (RSU)
0% of total
$0$0
$0
median
Cash bonus
0% of total
$0$0
$0
median
Aggregated from 116 self-reported salaries via Glassdoor. Estimates only. Verify against your offer.

The compensation data above illustrates expected salary ranges for software engineering positions, reflecting base pay alongside potential performance bonuses and profit-sharing components typical of employee-owned organizations. Compensation varies depending on experience level, specialized technical skills, and geographical office location. Use these figures to benchmark your expectations and inform salary discussions during final recruiter interactions.

15 · Candidate reports

What candidates actually reported

Interview difficulty
Easy
25%
Medium
65%
Hard
10%
65% rated it medium, the most common response.
Candidate sentiment
66%positive
Positive 66%Neutral 23%Negative 11%
Offer rate
0.0%received an offer
From a recent candidate
Average Positive United States

After I connected with recruiting, the process felt pretty manageable and even slightly casual. First there was a video pre-screen where I had to answer a small set of questions while the prompts appeared on screen. The questions were limited in number, but the format meant it was just me responding without much back-and-forth.

Next I had a virtual recruiter conversation for about 30 to 45 minutes. The questions were mostly behavioral and centered on my background and fit for the role. Overall it was a good experience; the recruiter came across as genuinely nice, and the discussion felt more like getting to know the person behind the resume than a high-pressure interrogation.

Read more
Read all 183 interview experiences
16 · The role

Inside the Software Engineer guide at Burns & McDonnell

19 · FAQ

Burns & McDonnell Software Engineer interview FAQ

Answered from real candidate and compensation data
How many interview rounds does Burns & McDonnell have for a Software Engineer role, and what does the loop look like?
Interviews for a Software Engineer role typically move through an Asynchronous Screen, followed by Direct Conversations with department managers or technical leads. Candidates who advance then complete a Live Panel Interview presented to hiring managers and team engineers, either virtually or onsite. In some onsite evaluations, you may also meet team members during informal interactions like lunches and campus tours to assess cultural fit.
How hard is it to get an offer for a Software Engineer role at Burns & McDonnell?
In candidate-reported data, the most common interview difficulty level for this company and role is average. The offer rate reported across interviews is 14%, with 566 reported interviews in the dataset. These signals suggest the process is not extreme, but performance still needs to stay consistent across screens and conversations.
What technical topics does Burns & McDonnell test for Software Engineer interviews?
Technical coverage leans toward both communication and domain relevant concepts. Common topics include one-line diagrams and substation diagramming, transformer protection, and power systems fundamentals, alongside Structural Engineering Concepts. You should also be prepared for Behavioral and Personality questions and Communication Skills, because the process explicitly evaluates how you present and discuss your background.
What are the most common question types I will face for Burns & McDonnell Software Engineer interviews?
The interview questions focus heavily on your work history, team collaboration, and alignment with company values. Expect Behavioral and Career Goals and Culture Fit prompts, like explaining your background or handling conflict, and why you want to work at Burns & McDonnell. You will also see Technical and Domain Knowledge questions, such as walking through a recent software project and discussing testing, debugging, and code quality.
What should I prioritize when preparing for Burns & McDonnell Software Engineer interviews?
Prioritize clear storytelling about past projects, since the process evaluates your background and how you work with multi-disciplinary teams. Be ready to explain real architecture choices, how you test and debug across multi-tier applications, and how you maintain code quality. Communication and verbal delivery matter, and cultural fit themes like employee-owner mentality and long-term career orientation are explicitly part of the question set.
What is the expected pay for a Software Engineer at Burns & McDonnell?
I do not have reliable pay figures for Burns & McDonnell Software Engineer compensation in the provided data. Because compensation varies by level and location, you should confirm the range directly from the job posting or recruiter for the specific office and seniority.