Why Mba After Engineering Essay Titles
If you have been scouring the net for international MBA related information, you’d know that a huge number of applicants from India have B.E, B.Tech, M.Tech degrees and several years of work experience after completing their engineering course. You don’t see a similar trend in other professions such as medicine, law, finance / chartered accountancy, entrepreneurship. Why is an MBA after engineering such a popular option for Indian professionals?
Engineers most likely to pursue an MBA
Let’s broaden the definition of what kind of engineers we are talking about here.
Category 1:Computer engineering graduates who work in the IT industry (primarily software development & testing roles)
Category 2:Engineering graduates with a non-IT specialisation (e.g. mechanical engineers, electrical engineers, mining engineering graduates).
Category 3:Non IT Engineers in non-IT roles e.g. mechanical engineers working in a production planning role, electrical engineering students who get into the energy sector, power generation / distribution / transmission jobs
Category 4:Engineers who are already in business oriented roles (like marketing and sales, finance etc).
Of course, you could mix and match these in many more ways, but for the sake of simplicity let’s take these 4 types of engineers.
The fact that the software industry takes up 2 out of 4 slots here, gets reflected in the actual MBA applications as well. Adcoms get overwhelmed (and confused) by the number of almost similar looking profiles they get each year.
Why MBA after engineering
The rationale for category 1 is relatively straight-forward. Why do software professionals go for an MBA after engineering? Ironically, it links back to the underlying reason that gets MBA Admission committees flummoxed.
Despite being ahead of the pack in their academic life, most software professional lose their identities in the ocean of faceless people just like them. Read this related post on Life after IIM / IIT.
The mid-life career crisis starts its onset earlier in the career. As opposed to the earlier generation of professionals who’d start hitting the glass wall after 15-20 years of working, for the current generation, the career cycles are shorter and more frequent.
Within 3-4 years, all the excitement of joining a new company at a higher salary dies down.
For category 2, things aren’t very different. If you thought, they are emotionally scarred for having to work in an industry that they were never trained for by their engineering college, you’d be mistaken.
For mechanical, electrical and mechatronics (yup, we got one from that stream too) engineers who have already transitioned outside their academic specialisation, very few express a desire to get back to their original domains.
But they suffer the same another-brick-in-the-wall syndrome like their peers who have relevant qualifications in computers and software.
An MBA seems like a good way to break away from the clutter and add a recognisable face back. Add to this the fact that the only way for IT engineers to rise through the ranks in the software industry is to take on managerial responsibility in the same field (as opposed to a diagonal or horizontal shift into unrelated areas).
So a few become team leads, project managers and start dabbling in new areas like recruitment, business development, budgeting.
The naturally gifted (and politically savvy) ones manage it well. For the others, an international MBA could get give their career vehicle the little nudge that it needs to start the growth phase again.
For categories 3 and 4, the problem of market saturation and oversupply of similar skills is there. But a bigger challenge is to deal with slower moving career paths. As opposed to software engineers who can expect to become manager in 4-5 years, the path to managerial roles in other industries is painfully slow.
For a category 4 professional who’s done well in the sales role and generated millions in revenue for his employers, there’s less of an incentive for the management to rock the boat and move him into a new role where his skills have been untested.
Ditto for category 3 folks in technical (and not business roles). A production engineer may spend many years in an operational role in companies that still believe in the traditional tenure based approach to promotions. No matter how much potential they have, there’s a long queue of seniors waiting in line for salvation.
Career growth issues for Engineers
The annual appraisals in the office appear to be more of a formality (in some cases, bordering on being a complete farce) to retain the employee rather than being really concerned about how he can develop and grow.
Which is probably why the Career Mock Appraisal Process that we launched purely as an experiment has generated so much interest (we had to turn down / defer most of them as our primary focus has been on MBA applications).
Focussing on the candidate’s interest (& not the employer’s) seems to be an alien concept for most companies.
Hoping that the company will one day realise the employee’s tremendous potential and reward him with all the goodies he deserves could be a naive expectation. Fast-tracking their career needs more than just patience and good work.
This realisation is the wake up call for many engineers that prompts them to consider an MBA.
Whatever your reasons might be, do be aware of the pitfalls of taking up the MBA route. Bschools, just like companies, have their idiosyncrasies. If you’ve read Beyond the MBA Hype, you already know what these are.
Are you an engineer? Which category (from the list above) do you fall in? Why and how do you think an MBA after engineering will help?
The pool of MBA applicants is filled with all sorts of diverse backgrounds: doctors, lawyers, bankers, entrepreneurs, teachers, writers…and of course we cannot forget the engineers. Many bloggers, including Rock of Gibralter and Juggler, are members of the tech world, and they represent the high volume in the applicant pool. Muskblog reported that 25% of his class had an engineering background. A quick look at some other schools:
Stern: 9% of the class of ’08 worked in Technology
Haas: 13% of the class of ’08 worked in Technology, 29% majored in engineering
Tuck: 16% of the class of ’08 worked in Technology, 18% majored in Engineering
Fuqua: 28% of the class of ’08 majored in Engneering
Translating engineering experience and lingo into a language that is both understood by and relevant to the admissions committee can be a challenge. This is an important hurdle to overcome, as it will touch most aspects of your application. Here is a look at how to rethink a basic business document – your resume.
On a typical engineering resume, you might find a line such as this one: “Synthesized an 8-bit ALU chip which could perform logic operations such as AND, OR and XOR.” Although I do not doubt that this is an interesting and impressive accomplishment in the engineering world, I have no idea what this means and am guessing that many admissions committee members do not either. When I see something like this, I will ask an applicant to translate it into MBA speak – what does this mean? What did you really do when “synthesizing”?
Often, on a second draft, I see a line that I can more easily understand. “Led the design and development of X.” Now this is something that I can understand. Led, design, development…the technical jargion has been translated. However, this resume still has a long way to go. It’s interesting how difficult it can be to really break down and describe the work that you do every single day. Yet this is what you need to do.
I ask, “when you are developing X, what are the steps you take, what are the skills you use?”
Think about the smaller steps:
Who did you manage, either directly or cross functionally?
What processes did you manage?
What kind of analysis did you run?
How did you structure communications?
Did you develop or improve upon any processes?
Developing X is a big accomplishment, and it took a lot of little steps to get there. To understand what you really did, you need to think about the smaller steps, and how they can be repurposed in a business role – how did you communicate, collaborate, manage, lead and more? Also important, think about your results. If you developed X, why is X so great? What was the impact of what you did? Did it save time, cut costs, increase revenue? Quantify results to the extent possible so a reviewer can understand the impact.
To appeal to an MBA audience, an applicant must think beyond technical tasks. He or she must identify what lies behind those tasks that might reveal an effective business leader. Going through this exercise can be painful, but it is a necessary step and something that will serve an applicant well throughout the entire application process.
If you are struggling with this important document, our consultants can help you think through how to translate your accomplishments into business lingo. Contact us to learn more.
This entry was posted in Uncategorized and tagged Dartmouth Tuck, Duke Fuqua, NYU Stern, Resumes, UC Berkeley Haas.
Bookmark this post..