а как же!!!magda писал(а):Так а руководство нельзя написать? плиз
Кстати, а оно вам надо?
И если не секрет, то зачем?
так да не так.конь в пальто писал(а):хорошего работника всегда заметят и на следующий контракт позовут, а дятла, который через пень колоду пишет(или булки печет, крыши кроет или канавы капает), естественно никуда не пригласят. в любой проф. области по моему так так.polkov писал(а):Надо наверное написать руководство как стать любимым контрактником (на гавермент)
Там есть свои танцы с бубном.
Пример, хороший программер работал там на одном контракте.
Потом подался опять через год и его обновленное резуме не прошло даже первичный отбор в ХР.
Если бы он попал на интервью то у него были бы 99% шансы получить контракт.
И начальник ничего не мог сделать.
И там "танцев" на каждом етапе хватает.
Вот хороших советов (если пригласили на интервью)
Below is general Ontario Government Interview preparation information that you can share with your candidates.
Interviews are always conducted by a panel of people...usually full-time people, usually a total of 3 people.
Dress is Smart Casual (Collared shirt, slacks, maybe a tie for men, a business suit or skirt and blouse for women).
The questions will be in 3 to 4 sections...ALL based on the requirements in the RFS. Please re-read the RFS (Background Information, Deliverables, Mandatory/Desireable Skills) to get a good understanding of the requirements. Some people go into an interview without even reading the RFP...this is a mistake as it shows a lack of preparation.
It would be good if you could jot down an association between each Requirement/deliverable with something in your resume. Write this down beside the requirement and bring the sheet with you. This will allow you to refer them to your resume during the interview. All interviewers will already have a copy of your resume, so you don't have to go print fancy ones or anything like that. Only if you have a change, should you need to re-give out your resume. You should have a copy for yourself to refer to.
All questions will be asked of all candidates, the same way, in the same order. They will grade each response according to a strict and pre-set marking scheme. At no time should you say "NO" to any questions as this automatically gives you "0" points.
When asked if you have a certain experience or knowledge, ALWAYS try to relate it to something similar if you do not have direct experience in it. You may at least get partial marks.
Here's an general example (not directly related to this role), if asked if you have IBM AIX OS experience, and you don't have any, draw a parallel to BSD and try to refer to any experience you have with BSD as IBM AIX is based on BSD. In the same way, if they ask about Solaris, and you only know HP-UX, refer to any experience you have with System V based OS's (as both Solaris and HP-UX are based on System V). Please note: Never fabricate any experience or knowledge, so in some cases you may have to say "No".
As you go through the requirements/deliverables, pin-point the ones you may not have any experience in and pre-plan some parallels you can make. If you get stuck...give me a call. The requirements that you do have, make sure you know where in your resume reflects that experience so you can direct the interviewers to that section as you elaborate and discuss the issue/question.
Please be ready to "White board" your responses (pen and board will be provided, but you can bring your own pen if you wish - that displays good preparation and initiative). If given the opportunity, please use it to display your experience graphically on the white board as this always ensures you get the maximum points possible for your response.
You may also be asked some situational questions dealing with "Team" issues and possibly "conflict resolution". Please prepare something for that (i.e. According to PMI - Project Management Institute, the best conflict resolution method is "Confrontation".
Confrontation is defined as confronting the issue (not arguing), finding the facts, and objectively agreeing on a solution together based on the facts. The worst method is "smoothing" or "withdrawl" as these methods only hide the issue, only to have them resurface at a greater level, and at the wrong time). Your answer to any "Project or Team issues" should always start with "I would notify the Manager/Project Manager, and ...". Most work is "projectized", so the Project Manager must be involved in all issues. Always bring problems to the table WITH SOLUTIONS IN HAND.
At the end of the interview, you will be given the opportunity to ask any questions. Please generate a Question from the RFP "Background" material to show your knowledge and understanding of the project. Try never to ask questions that "Stump" the interviewers or make them look bad. Do not ask questions about work hours, dress code, billing issues, work space, lunch hours, smoke breaks, etc.
, люди еще работают из-за лени и страха. Лени поднять попу и делать, и страха к переменам, так что наверное не в том дело кто здесь "все" 