[OT] Re: As an employer what type of project (Engineering) you would like to see ?
Oleg Goldshmidt
pub at goldshmidt.org
Thu Jun 11 00:56:46 IDT 2009
Boris shtrasman <borissh1983 at gmail.com> writes:
> Since i don't really see a pool of project that i can choose from i
> come to ask here .
What exactly are you asking on a technical Linux list??? If I
understand your intent correctly, you are asking what area to choose
for your final project to increase your chances to get gainfully
employed after graduation.
I'll bite, but add [OT] to the subject line... ;-)
First you need to ask yourself what area you want to work in... Do you
have a preference? If yes, you are done. I'll assume that you don't.
If you are thinking in terms of "what area has the most employment
opportunities or biggest starting salaries this year (or this decade)"
then I would urge you to reconsider. It is much more important to
figure out what you'll enjoy, as opposed to hate, doing. The salaries
don't vary from gazillions to starvation, anyway. I suspect that
neither does the candidates-to-vacancies ratio.
> As an employer would you prefer Bioinformatics / Cryptography /
> Networking / HighSpeed Networks / Robotics project ?
Depends on what I do for a living, I suppose... ;-) Someone recruiting
for a high speed networking company or project is likely to give some
extra bonus points for any experience in the field, compared to
something unrelated, e.g., cryptography. However, if the potential
employer has half a brain this is going to be a minor consideration
only.
One does not expect world class expertise in XYZ from a recent
university graduate. Instead, things that would impress me at an
interview would be *something* along the following lines:
* Your ability to present what you have done, what you have learned,
what you enjoyed in the process. Telling the story clearly and
logically - and excitedly - conveys that you actually know what you
are talking about. Your understanding of the wider context will
indicate that you applied your brains and were not a mindless code
monkey merely implementing your advisor's detailed instructions.
* Your demonstrated drive and ability to learn new things (remember,
ready-to-wear experience is not the focus), adapt, contribute.
* Whom did you collaborate with? How? What the division of labor was?
Why? What was your personal contribution (as opposed to, say, your
advisor's)?
* Your experience apart from the final project: from what you wrote it
seems that you have quite a few things to sell - emphasize them;
Flashback: I recall the first person I personally made a decision to
hire, years ago. She came straight after university, no experience,
and much of the interview focused on her final project. For the life
of me I don't remember what the topic or the field was, but I do
remember how she was talking about it... I'd hire her again today,
even though I work in a totally different field now.
> What is more important the project theme or the guide (מנחה) ?
I am convinced that the topic has only minor importance.
The advisor's name might be important if he/she is a well-known expert
in the field and/or has lots of contacts in the industry. It is still
much more important that he/she gives you a very good recommendation
when asked. If the potential adviser indicates that he/she understands
that a big goal of the project is to be a part of your personal
"portfolio" (rather than *his/her* personal "portfolio"), it's a big
plus.
Most of all, pick a project that you'll get excited about. You will
not be able to effectively use - or present - experience that got you
bored.
Having said all that, CVs might be pre-screened by some secretary or
junior HR person or a placement company clerk by "vgrepping" for a
fixed set of keywords... Optimizing your chances to pass such
pre-screening will not necessarily help you to succeed at the actual
interview.
--
Oleg Goldshmidt | pub at goldshmidt.org
More information about the Linux-il
mailing list