Strategy consulting firms count many engineers in their teams, and many engineering schools see part of each graduating class apply every autumn. Yet these candidates’ CVs and interviews often betray the same flaws: vocabulary that is too technical, projects described by their tool rather than their effect, and a business reading that is still fragile. This article explains why firms are interested in this profile, what an engineer genuinely brings, and what to work on before applying. It also gives concrete methods for rewriting a technical project in consulting language and for preparing cases.
Why firms recruit engineers
A strategy firm does not sell a degree, it sells an ability to structure a fuzzy problem, analyse it rigorously and convince a management committee. Engineering training prepares precisely for part of this work: breaking down a complex system, setting hypotheses, testing them, accepting that an answer may be approximate but defensible.
Two developments reinforce this interest. Engagements increasingly involve data, modelling and technology: industrial transformation, energy, mobility, digital, artificial intelligence. On these topics, a consultant who can understand an architecture, a manufacturing process or a statistical model saves time and gains credibility with a technical client. In addition, firms look for varied profiles and do not limit themselves to business schools: McKinsey’s careers site for France states, for example, that it recruits graduates of engineering schools as well as business schools, and also more atypical profiles (what the firm looks for 🔗).
This openness should nonetheless be read with nuance. The firm does not recruit “an engineer” the way it would recruit an expert: it recruits a future consultant who happens to have a scientific background. The difference is crucial for everything that follows. Your degree opens the door of the initial screening; it does not replace business reading, ease in communication or the ability to work in a team under pressure, which are assessed afterwards. To understand how that screening works, read how consulting firms screen CVs.
Finally, the engineering title is a clear marker for the recruiter. In France, the Commission des titres d’ingénieur (CTI) is the independent body that evaluates and accredits engineering programmes; its site sets out the framework within which these degrees are awarded (CTI 🔗). This guarantee of level partly explains why recognised schools appear in recruitment pools, and why a degree outside this framework needs to be explained more precisely on the CV.
The strengths to put forward
Not all the supposed strengths of an engineer are equal. The ones that count are those the firm can verify or observe.
Analytical rigour. An engineer is usually comfortable with orders of magnitude, units and dependencies between variables. In a case interview, this shows in how an estimate is set up or a result is checked. It is a real strength, provided you demonstrate it rather than announce it: a phrase like “analytical mind” on a CV proves nothing.
Modelling. Building a model, simplifying a system to make it workable, knowing what you are deliberately ignoring: this reflex is at the heart of consulting work, when you must build a financial model, a market model or a scenario simulation.
Technical understanding. On an industrial, energy or digital engagement, understanding how a process or a piece of software works avoids depending on experts for every question. This knowledge is valuable, but it must be translated into value for the client, as we see below.
Project culture. Engineering curricula include group projects, internships and sometimes simulations under tight deadlines. A candidate who has led a project, arbitrated between constraints and delivered a result already shows a way of working close to that of a consulting team.
Versatility. An engineer who has worked in a design office, in production, in R&D or in data has seen several facets of a company. They can talk to a plant director as well as to an IT director, which eases integration into mixed teams.
These strengths are best backed by figures within your own scope: a budget managed, a team coordinated, a measured gain. The article on how to quantify your results on a consultant’s CV details the method, including when you have no official figure to quote.
Frequent blind spots
This is the part candidates prefer to avoid, and the one that weighs most during screening. The same weaknesses come back from one profile to the next.
Jargon. A CV that talks about a “finite element model”, an “ETL pipeline” or a “test bench” without saying what it was for is hard to read for a generalist recruiter, who has a few seconds to assess it. They are not trying to understand the technique, they are trying to spot an impact.
Description by tool. “Development of a Python data-processing tool” describes what you did, not what it changed. The reader must be able to answer: for whom, for which decision, with what result.
A still fragile business reading. Many engineers know how to solve a problem that is set, fewer ask whether it is worth solving. Questions of market, competition, profitability or strategic positioning are not always part of the curriculum. In an interview, this translates into analyses that are correct but detached from the client’s question: the candidate optimises a cost without asking what it weighs in the margin.
The search for the exact solution. A culture of precision can become a handicap in a case: the candidate wants to calculate rather than estimate, and digs into a detail before laying out the structure. A firm expects a usable answer in little time, not the best possible answer.
Oral communication. A solid analysis presented in a linear way, without an opening message, loses its audience. The consulting rule is the reverse of the scientific approach: you give the conclusion first, then the arguments.
A too uniform background. A CV that contains only technical projects, with no associative involvement, no team mission and no trace of responsibility, suggests the candidate has not yet worked on the human side of the job.
These blind spots are not disqualifying. They can be corrected, sometimes in a few weeks, provided they are identified honestly.
Translating a technical project into consulting language on the CV
The most profitable work before applying is to rewrite each technical line using the same grid: context, action, decision, effect. Take a fictional example, as a model and not as a real career.
Before: “Thermal modelling of a plate heat exchanger in Matlab, validation by bench tests.”
After: “Sizing of a heat exchanger for an industrial equipment maker: comparison of three architectures by modelling, recommendation of the cheapest one meeting the specification, validated by tests.”
The second version says who the client is, what was compared and what was recommended. The technique is still there, but it serves the argument.
A few rules to reproduce this work:
- Replace the tool name with the result. The software can appear at the end of the line or in a skills section; it should not open the sentence.
- Name the decision. What was chosen, stopped, launched or avoided thanks to your work? This is the wording consulting understands.
- Give the scale. Team size, duration, budget, data volume: an order of magnitude is enough, as long as it is true and you can defend it in an interview.
- Keep technical vocabulary for what proves a rare skill. One precise term in the right place reassures; ten unreadable ones tire the reader.
- Use the language of the end client. A yield gain becomes a lower unit cost, a shorter lead time, a reduced risk.
The same logic applies to the overall presentation. Experiences are easier to group by type of work than by laboratory or design office; the article on consulting engagements on a CV shows how to organise experiences of different natures. And if you want to see a finished result, the strategy consultant CV example shows the expected format: one page, action verbs, situated results.
A point of form also matters. Applicant screening software reads complex layouts poorly (columns, icons, boxes). In our editor, you write the content and the layout is handled for you; the resulting PDF is structured to be read correctly by such software, which matters when automatic screening comes before human reading. You can create your CV and start from scratch with this grid.
Preparing cases with an engineering profile
The case interview is the moment when the profile’s strengths and weaknesses show most clearly. The starting point is favourable: engineers are often comfortable with numbers. Training must therefore focus on the rest.
Learn to structure before calculating. Setting out a clear, hierarchical structure that covers the problem without overlap is the skill firms work on most. The frameworks used in case interviews provide a foothold, provided you do not apply them mechanically: the right framework is the one that adapts to the question asked.
Estimate rather than calculate. Practise rounding boldly, stating your assumptions aloud and checking the consistency of the result by a second route. The aim is not the decimal, it is the logic.
Give the conclusion first. At each checkpoint, start with the answer in one sentence, then justify it. This synthesis exercise is often the hardest for scientific profiles, and the most visible to the interviewer.
Put the client back at the centre. For each analysis, ask yourself: which decision does it serve? What is the economic stake? What would be the risk of being wrong? A good practice is to end each answer with the recommendation and its financial implication.
Work in pairs. Cases are learned aloud, with someone playing the interviewer. A friend from another programme, or a business school student, will send back questions that your own curriculum does not prompt.
Do not forget the part that is not a case: the firm also asks about your background, your motivations and your choices. An engineer who can explain clearly why they are leaving technical work for consulting, without disparaging their original profession, makes a good impression.
The most sought-after specialities
An engineering degree covers very different specialities, and their value depends on the engagement. Rather than looking for the right stream, it is better to identify where your speciality meets a precise need of the firms.
- Industry and operations. Production, supply chain, quality, maintenance: industrial performance and site reorganisation topics call on profiles who know the field. This is the domain of the operations consultant.
- Data and artificial intelligence. Statistics, machine learning, data architecture: these skills are in demand for data-driven transformation engagements. The data and AI consultant CV shows how to present them without sliding into jargon.
- Energy and environment. Energy transition, decarbonisation, grids, mobility: understanding physical systems and regulatory constraints gives an edge on sector strategy engagements.
- Digital and information systems. Software architecture, cybersecurity, cloud: firms need consultants who understand the technical stakes of a digital transformation.
- Mechanics, aerospace, materials. These specialities open the aerospace, defence, automotive and chemicals sectors, where knowledge of the product and the value chain is a real differentiator.
- Market finance and financial engineering. Programmes combining applied mathematics and finance prepare well for financial strategy and due diligence engagements.
In every case, what counts is the ability to link your field to a general-management issue. Your school gives you a network, alumni and company forums; the Conférence des grandes écoles brings together the institutions concerned and publishes work on graduate employment outcomes (CGE 🔗). To place the sector and its professions more broadly, the website of Syntec Conseil, the professional organisation of consulting professions in France, is a good reference point (Syntec Conseil 🔗).
To build your application, choose two or three experiences that best show impact, rewrite them using the grid above, check that no line needs a dictionary, then test the CV on someone who does not know your field. If they understand the point of each line, you are close to the right level.
Frequently asked questions
Do I need to graduate from a top engineering school to join a strategy firm?
No, but the initial screening remains sensitive to education and background. Firms say they look for potential and varied profiles. A less well-known school simply requires strengthening the other proofs: internship results, responsibilities, the quality of the CV writing and case preparation.
Should my engineering CV stay technical to show my competence?
It should stay precise, but not technical for its own sake. Keep the terms that prove a rare skill and translate the rest into decision and effect. The reader must understand the point of each line without knowing your field.
Is a dual engineering and business school degree essential?
It is not mandatory. It reassures about business reading, but an engineer can demonstrate it otherwise: economics or finance courses, an internship in a commercial environment, student associations, serious case preparation.
How do I explain my choice to leave technical work for consulting?
Present what attracts you rather than what you are fleeing: the variety of topics, the proximity to decisions, the desire to learn fast. Avoid disparaging your original profession, and rely on one or two examples where you already enjoyed this type of work.
When should I start preparing cases?
Several months before applications, regularly, aloud and in pairs. Starting early leaves time to correct engineer reflexes (over-precise calculation, late synthesis) before the deadline.