Technical interviews are mostly owned technology leads, if project managers are part of the interview times. When I mean the technology, it could be for SAP functional status, ABAP, Basis or other technical positions. Not all types of interviews have all of the following stages. For eg., Full time position or contract to lease will take more general questions / tasks her / his achievements know activities etc while negotiating position will include targeted information about modules / uniqueness that he is engaged for.1.
1. Warm Up
This is just immediately after the first meet-and-greet and offers coffee. You will be asked questions mostly on project history. This phase is just assess your strength zone. Do not panic if you are asked questions that are much unrelated to what you might have done in the past or are out-of-the-blue in terms of technology. The interviewer is just making initial assessment of where the strengths are and how you might fit the requirements. Sometimes resume could not be touched either just yet. You must explain the project scenario, what short term and long term goals are. Again, the idea is to let you know the back ground and to prepare you generally spate of questions that are going to come your way. Most of the time people interview you would be either technical lead or project or both. If you are interviewing consulting company, sometimes managers from the client side was present as well. For non-native English speakers, speak slowly and clearly. The process of the interview almost always ways to speed up your words. This needs to be carefully and consciously avoided.
- Come early interview site or by telephone conference (if telephonic interview). Try to follow the general directions and smile a lot. Try to go to the rest room (interviews can last for an hour after the second round with you sipping coffee / water between) required before the interview so you can concentrate well in the interview without interference.
- Project actual strength
- Having a positive attitude and be very safe even if you are not 100% sure of the technicalities involved.
- ask questions about the project / company that you are sure will project your knowledge in a positive light.
- Speak slowly and clearly
- After meeting your contact / interviewer outside, do not be on the phone with someone else at any point before the interview has begun.
- do not stand fake skills in this phase and get into trouble. They might not need them.
- Do not try to steer the interviewer in the direction you want the interview to go just yet.
- not lose confidence, even if you hear or questions are terms that you might not have heard of.
- Do not get into an argument to ask questions or answer them. Just nod or say “I do” and smile when you find what is wrong with the project being discussed.
Examples of the questions
1. How do you think you XXX (An area of SAP modules, SAP SAP pricing)? 2. Have you worked XXX (An area of SAP modules) or YYY (specific business scenario, says data migration live purchase orders)? 3. Give a brief about your experience? (First and most asked question)
2. Technical questions
This is the hardest round and what you’ve been preparing for all along. This round may last quite a long time and if you are interviewing for a large company that phase could be done by many teams for many hours. Usually you will not be asked to bring in technical traffic the next day, but on the same day, it could be a ring with A and another round of team B. 80% of the time the focus was on the new phone and the achievements you mention in your resume. The questions would not go out much in the first and second projects unless they find something interesting or something they could relate to the 5 or 6 project. Also making technical questions would depend on if you are applying Jr., Mid-level or Sr Consultant position.
1. Prepare a new well. You are what your resume is. If you can reflect new interview you’re all set. That exactly what the interviewer is looking for. Resume preparation is an art in itself. Spend a considerable amount of time tweaking it
2. Prepare a new job. This applies mainly to contract work. This could actually sound so bad, but works well. Do not place the same again for all jobs. Change it to suit the requirements job.You do not go over board with it. See if a few changes here and there may be an asset. For example, if the job requires you to know “SAP Credit Management” and if you have done credit management (not your strength) try to expand on it. Try to do some reading if required or brush up your skills in the system. If possible, try to dig out the old documents or notes you might have. This type of flexibility on your part can go pretty far to get you the right job.
3. How to project yourself –
a. If you are applying Jr. horizontal, project yourself as a happy enthusiastic and quick to learn. Show your aptitude with SAP expertise. They already know that you do not have much skill – they are just looking for someone who is willing to learn and be flexible enough
b .. If you are applying for mid-level SAP consultant position, task himself as the go-to guy for specifics. You need to solve specific problems. Technical experience is what is sought. Specialization is the key.
c. If you are applying Sr. horizontal, show broad exposure and tell them about the project experience, methodology, (not just about specific fields). Broad-based exposure is the key
questions may vary depending on the style of the interviewer
Style 1 – .. Based on your resume – This is how most of the interviews conducted. As you would have already sent back to the team there (they have pre-screened and you said YES interview), they already know that you have the skills needed for the job. So mostly a matter of convincing them that you actually have it in you. If you have prepared a new well, this interview style will really catch you
Style 2 -. Given the current backlog of projects – some focus on the current task of the claims or what they have been doing over the past 1 year. These are in fact the most difficult questions to answer. It is actually a very bad interview style, but you just have to take it into account. These people are the most difficult to impress. But remember, everyone who comes for an interview will face the same task as you do. It rarely happens that a candidate interviewed is very well versed with the specific issues that the interviewer is asking questions about (without referring to your resume
Style 3 -. Management style Technical questions – Sometimes project managers ask technical questions. This could be a tough call. You would have to build answers first judge the type of questions he is asked. Some project managers come from a technical background and ask very relevant technical questions which test specific skills as a general understanding. These people not to be fooled easily and if you have the right skills, are easy (the key to impress them easily these interviews is to explain certain tasks related to the incident and how you resolved them, both from a project management perspective and a technical perspective. These folks looking mostly for the go-getter attitude). Some project managers come from a non-technical background and still do a technical interview. They ask questions that are mostly related to the administration (Landscape, moving), the current situation and business QA. All they look for is all confidence. You just have to say “yes I do” (in other words, sound knowledgeable even the things you might not know) to all their questions because they do not know the answers themselves.
- Collect 60% of the technical preparation of the first and 20% in the second project.
- Prepare a new well and prepare well for it.
- Be aware of each line of the first two pages of your resume.
- Explain special cases where you have faced or solved problems.
- In short, the task is to try to count specific customization scenario. Not only list standard customization scenario too much.
- Try not to say “I do not remember” atleast questions on the first project.
- not always talk too much about the standard functionality. This gives the impression that you are a student and have not done much customization.
Examples of the questions
1. Technical Questions in the subject area of expertise (Functional / Technical / Administration / PM). 2. How do you resolve this situation? (They will give you a specific scenario and ask for your approach to problem solving) 3. Special customizaion example (How to Install seasonality of the credit limit or how to enable line-item overview in G / L master etc)
This phase should really be a breeze. The key is to understand that the interviewer at this stage wants to take you. It is yours to lose. This phase could be done by any of the following group of people
- project / program managers
- Project sponsor
- User Community
- Customers (If you are interviewing for consulting)
The interview could happen on the same day or the next. This stage might or might not happen for contract jobs and even if it happens is more a formality. But for full-time employment, traffic management is almost mandatory. This round as you might have guessed it’s just a matter of showing soft skills. If you take out all the fluff, it boils down to the following.
1. A medium / long-term goals align with what the team / executive / company assume the person in this role?
2. Do you have what it takes to work with team / user? 3. Are accomodative?
This round only to full-time employees (where contending racing business a background contractor). The HR primarily plays two roles here
Investigator -. History employer verification background, criminal history verification etc. Bargain Master – Salary negotiations, transport allowance, bonus, etc. There is a ton of information online about how to tackle HR rounds and caveats involved.