Your engineering project may have taken a semester to build, but the interview question gives you only a short space to explain it. The difficulty is choosing the detail that shows how you think.
Start with one decision you can defend. What were you trying to achieve? What made the task difficult? What did you personally change, and what did the test show? These points give the listener something to understand beyond the project's name.
Choose a project with a clear decision
A technically ambitious project is not automatically your strongest interview example. Choose work where you can identify your contribution and discuss the evidence behind a decision.
Before choosing, check whether you can answer these questions without relying on a teammate:
- What was the practical objective?
- What constraint changed the design or the plan?
- What part did I own?
- What alternative did I consider?
- How did I test the result?
- What remained unresolved?
If you know the software names but cannot explain why the team used them, recover that reasoning or choose a better-understood example. Keep confidential research, personal data and restricted project material out of the answer.
Build the answer around goal, decision and evidence
Use this sequence to organize your notes. It is an editorial practice structure, not a standardized engineering interview rubric.
| Step | What the listener needs | Example of useful specificity |
|---|---|---|
| Goal | The problem in ordinary language | We wanted the prototype to give repeatable readings. |
| Constraint | What made the solution difficult | We had limited time and could test only on the department's bench equipment. |
| Responsibility | Your part in the work | I handled the measurement procedure and compared the readings. |
| Decision | What you chose and why | I tested the measurement conditions before changing the sensor. |
| Evidence | What the test actually showed | The repeated runs were more consistent under the controlled condition. |
| Limit and learning | What you cannot conclude yet | We had not established performance outside that test setup. |
Give enough background for the decision to make sense. A long explanation of the assignment brief can use up the space you need for your contribution.
Columbia's interview preparation material distinguishes experience-based discussion from technical assessments. A well-explained project can support the former; it does not replace preparation for coding, calculations or other technical work specified in your invitation.
Replace a tool list with a decision story
A weak starting point: “We built a sensor system with a microcontroller, Python and a dashboard. I did the data part, and it worked well.”
The listener still does not know what was difficult, what “the data part” involved or how you decided it worked.
Here is a fictional teaching example. The project and test details are invented for illustration; they are not a customer result or an employer question.
For a university prototype, our goal was to make a sensor's readings consistent enough to compare across repeated runs. My responsibility was the measurement procedure and analysis. We saw that the readings drifted between tests, and the team initially considered replacing the sensor. Before changing the hardware, I proposed checking whether our test conditions were causing the difference. I used the same reference input, recorded the warm-up period and compared repeated runs under the same setup. The controlled runs were more consistent, which gave us a reason to revise the procedure before buying another component. We had only tested on that bench setup, so I would not claim the issue was solved for every environment. My main learning was to check the measurement method before treating a difference as a design failure.
The answer describes a hypothesis, a test and a bounded conclusion. It also separates the student's proposal from the team's larger project.
Add the technical detail that changes the reasoning
Different disciplines need different evidence. The useful detail is the one that explains the choice, rather than every technical term you remember.
| Project type | A decision worth explaining | Evidence to discuss if you have it |
|---|---|---|
| Software | How you investigated an intermittent failure or handled an edge case | A reproducible test, logs or a comparison before and after the change |
| Mechanical | Why you selected one design under a weight, cost or manufacturing constraint | Test results, calculations and the conditions they depend on |
| Electrical | How you separated a component issue from a measurement issue | A controlled input, repeatability and the limits of the setup |
| Process or environmental | Why you changed a step or compared two approaches | A baseline, the changed condition and any uncertainty in the comparison |
These are possible angles, not claims about what every employer evaluates. Use only the evidence your project actually produced.
If a result is numerical, include its context. A faster run on one input does not prove the software is faster in general. A prototype meeting a lab target does not establish a certified product. Explain the baseline, conditions and sample before drawing the conclusion.
Discuss a setback without hiding the engineering
A project that missed its target can still give you a useful decision to explain. State the target and the result directly, then show how you investigated the gap.
For example, you might explain that an initial model did not match the measured result, identify the assumption you checked, and describe what further test was needed. Separate a next step you proposed from work you actually completed.
Avoid converting every setback into a success story. “We had not resolved the source of the variation, but I narrowed the next test to these two explanations” can be an accurate, complete ending.
Copy this project interview worksheet
Project and purpose:
Role or internship I am preparing for:
Constraint that mattered:
My responsibility:
One decision I made or proposed:
Alternative I considered:
Reason for the choice:
Test or comparison:
Result, including conditions and limits:
What I learned:
What I would investigate next:
Now explain the project to someone outside your course. Ask what they think you did and what the test established. If they remember only the tools, simplify the setup and give the decision more space.
Match the practice to the engineering role
There is no single engineering video interview format. For a specific example of scope, Schneider Electric's Boston Energy Tech Accelerator posting refers to HireVue in its assessment notice. That establishes context for that posting, not all engineering jobs or every Schneider Electric programme.
Review your own invitation for the required stage and controls. Use the answer-length guide to shorten an explanation while keeping the decision and evidence. If you are preparing specifically for software, the JPMorgan software guide addresses that separate context.
You can explore engineering-related practice directions and read the company and role descriptions before choosing. Full interview practice requires Interview Practice or Complete Practice access; the project worksheet can also be rehearsed independently with a peer.
FAQ
Can I discuss a group project?
Yes. Give the team context, then identify the decisions and work you were personally responsible for. Credit other people's contributions accurately.
What if the project did not meet its target?
Explain the target, what your tests showed and the limitation. Describe a justified next step or a later change you actually made instead of inventing a successful ending.
Do I need to show code, slides or a prototype?
Follow the instructions for your assessment. Prepare an explanation that makes sense without visuals, and use additional material only when the format and rules allow it.
Sources
Related Guides
Tell Me About Yourself for an Internship: Student Examples and Practice
Build an internship interview introduction from your studies, projects and interests. Includes three student examples, sentence edits and a copyable worksheet.
Read GuideJPMorgan Software Engineer HireVue: A Preparation Guide
Prepare project explanations, debugging examples and role motivation for JPMorgan software interviews, with a clearly scoped Emerging Talent practice guide.
Read GuideCheck the role and practice description. Independent interview practice does not replace technical tests or reproduce an employer's exact assessment.
Explore engineering interview directions