I was once asked your question regarding no software available.
My reply was to offer an inclusive rate for the job, i.e. my rate plus a rate for me supplying planning software - my offer was accepted and it was a nice little earner.
I must agree with the comment below regarding "Important".
The "Message Subject" description on this tread like a lot of others on this site is very poor. If people have a valid point / question to raise a little more time spent on the "Message Subject" would be well spent and hopefully get a better response.
A few things I remember being asked at various interview:
Technical Points on Planning:
- What is Total Float and how is it calculated.
- What is Free Float and how is it calculated.
- What is a Critical Path and how is it calculated
- Difference between Forward and Backward Pass
- What is PERT.
- How to produce SCurves
- What is a Gannt chart.
- Points related to Planning Levels.
- What are WBS structures.
(Just standard planning information)
Technical Points on Systems:
- Names of systems.
- What version used.
- What level of compentancy.
- Odd ball questions related to the system
- How to set up a project, update progress etc.
Projects Worked on:
- Project names, dates, duration, scope etc.
- Size of project i.e manhours, cost value
- Duration of projects
- Role you carried out.
- Did you supervise or where you supervised
- Numbers of persons you supervised
- Names of people from the projects
Trade Tests:
- Only once had to draw a simple hand drawn network
Original Qualifications / Certificate:
- Produce original qualifications
- Produce testimonials etc
Most of the above they should have been able to judge my knowledge and experience from my CV, but I suppose they need to go through the "motions".
One thing I always take of copies of my work from previous / recent jobs, that usually goes down well, I suppose it helps to brighten their day up a bit!
I always consider the interview a two way thing, i.e. they get to know you and you get to know them - perhaps at the end of the interview you may not fancy working for this client, never mind if they would like to employ you!
Lots of ideas, so here is another. Before the interview, see if the CV reflects the skills and experience youre looking for. If not, send a thank you letter and tell the applicant what he/she can do to become qualified for the position. If the CV appears to satisfy your needs, plan and schedule the interview. The interview should confirm alignment to your needs and the level of supervision you expect. For example, for a junior level position, a skills test of software, scheduling mechanics, and application of WBS may be most important. For a senior position, communication, problem solving, and creativity are likely critical. For this ask about what he/she considers to be their proudest moment in saving the day and what was your worst failure. Needless to say, you want a planner who is truthful even when ship is sinking!
Not sure I really agree with that the interview seems more like an exam. When I recruit I am more interested in the way the person thinks, I dont really care if he can find what I consider are mistakes in the programme. I want to know how he would put one together.
Programmes are the end product of an analytical thought process my interest is the thought process.
Oscar
Member for
19 years 2 months
Member for19 years2 months
Submitted by ashraf alawady on Thu, 2006-08-31 05:47
questions generally asked in interview regarding PLANNING ENGINEER...can not give proper judgement of the perfornance
and cleverness of the planning engineer.
In my opinion, the best practical way is to give him a programme and ask him to review that proramme and to write his comments then you can discuss with him all comments raised as well as not raised by him.
Many will go on about looking at milestones and key dates and production rates and all sorts of bull
My ideal answer would be look at the drawings and spec, develop your programme (requires mor explanation here) then see how close you were to the contract period.
Thats a pretty good start to see if the guy knows anything about planning
Oscar
Member for
19 years 5 months
Member for19 years6 months
Submitted by Nigel Winkley on Wed, 2006-06-07 12:13
Obviously experience, type of projects, etc., what software used - for comparison with your companys.
You can also try a what would you do for..., how would you start planning...,and one that my last company used "What is something that you are proud of doing" to try and find out something about that they are like.
From their CV see what other jobs they have worked on and have a look in the press to see how they went - may be nothing to do with them directly but may give you a hint.
Another goodie is why are you a planner? This might establish if he is a "failed engineer", logically minded, was pushed into or just plain likes planning.
Usual stuff like why do you want to work for...
If you really need to see what they can do, ask them some sort of technical questions - have you ever used a SF relationship, how do you structure your WBS, etc.
Member for
21 years 1 monthRE: Important
Hi Kym
I was once asked your question regarding no software available.
My reply was to offer an inclusive rate for the job, i.e. my rate plus a rate for me supplying planning software - my offer was accepted and it was a nice little earner.
I must agree with the comment below regarding "Important".
The "Message Subject" description on this tread like a lot of others on this site is very poor. If people have a valid point / question to raise a little more time spent on the "Message Subject" would be well spent and hopefully get a better response.
Regards
John
Member for
19 years 2 monthsRE: Important
agree with last post, planning and software are mutually exclusive - men plan, boys play with software...
By the way I do not think this tread is in any way important...
Member for
19 years 2 monthsRE: Important
I often ask the candidate how they would provide management support if we didnt have planning software. The responses are always pretty interesting.
Member for
21 years 1 monthRE: Important
Hi
A few things I remember being asked at various interview:
Technical Points on Planning:
- What is Total Float and how is it calculated.
- What is Free Float and how is it calculated.
- What is a Critical Path and how is it calculated
- Difference between Forward and Backward Pass
- What is PERT.
- How to produce SCurves
- What is a Gannt chart.
- Points related to Planning Levels.
- What are WBS structures.
(Just standard planning information)
Technical Points on Systems:
- Names of systems.
- What version used.
- What level of compentancy.
- Odd ball questions related to the system
- How to set up a project, update progress etc.
Projects Worked on:
- Project names, dates, duration, scope etc.
- Size of project i.e manhours, cost value
- Duration of projects
- Role you carried out.
- Did you supervise or where you supervised
- Numbers of persons you supervised
- Names of people from the projects
Trade Tests:
- Only once had to draw a simple hand drawn network
Original Qualifications / Certificate:
- Produce original qualifications
- Produce testimonials etc
Most of the above they should have been able to judge my knowledge and experience from my CV, but I suppose they need to go through the "motions".
One thing I always take of copies of my work from previous / recent jobs, that usually goes down well, I suppose it helps to brighten their day up a bit!
I always consider the interview a two way thing, i.e. they get to know you and you get to know them - perhaps at the end of the interview you may not fancy working for this client, never mind if they would like to employ you!
Regards
John
Member for
20 years 9 monthsRE: Important
Lots of ideas, so here is another. Before the interview, see if the CV reflects the skills and experience youre looking for. If not, send a thank you letter and tell the applicant what he/she can do to become qualified for the position. If the CV appears to satisfy your needs, plan and schedule the interview. The interview should confirm alignment to your needs and the level of supervision you expect. For example, for a junior level position, a skills test of software, scheduling mechanics, and application of WBS may be most important. For a senior position, communication, problem solving, and creativity are likely critical. For this ask about what he/she considers to be their proudest moment in saving the day and what was your worst failure. Needless to say, you want a planner who is truthful even when ship is sinking!
Member for
20 years 1 monthRE: Important
Not sure I really agree with that the interview seems more like an exam. When I recruit I am more interested in the way the person thinks, I dont really care if he can find what I consider are mistakes in the programme. I want to know how he would put one together.
Programmes are the end product of an analytical thought process my interest is the thought process.
Oscar
Member for
19 years 2 monthsRE: Important
questions generally asked in interview regarding PLANNING ENGINEER...can not give proper judgement of the perfornance
and cleverness of the planning engineer.
In my opinion, the best practical way is to give him a programme and ask him to review that proramme and to write his comments then you can discuss with him all comments raised as well as not raised by him.
Member for
20 years 1 monthRE: Important
I always ask how do you create a programme
Many will go on about looking at milestones and key dates and production rates and all sorts of bull
My ideal answer would be look at the drawings and spec, develop your programme (requires mor explanation here) then see how close you were to the contract period.
Thats a pretty good start to see if the guy knows anything about planning
Oscar
Member for
19 years 5 monthsRE: Important
Ritesh
Obviously experience, type of projects, etc., what software used - for comparison with your companys.
You can also try a what would you do for..., how would you start planning...,and one that my last company used "What is something that you are proud of doing" to try and find out something about that they are like.
From their CV see what other jobs they have worked on and have a look in the press to see how they went - may be nothing to do with them directly but may give you a hint.
Another goodie is why are you a planner? This might establish if he is a "failed engineer", logically minded, was pushed into or just plain likes planning.
Usual stuff like why do you want to work for...
If you really need to see what they can do, ask them some sort of technical questions - have you ever used a SF relationship, how do you structure your WBS, etc.
Good luck - interviewing is a real pain at times!
Nige