Are there any software engineers in here? Need advice on day-to-day tasks

[cypher_soundz]

I'm currently applying for jobs in the software engineering field. I keep getting hit with questions like "why do you want to work for Sony?" the question that looks easy to answer at first glance is actually asking for information on what I know about the job and what I think it involves on a day to day basis. So if any one if this area would like to either PM me or post some areas / jargon here, it would be a very nice starting point for me.:)
Regards
cyph

[Guest]

Here are some general talking points:

1. You've always been impressed by the quality of Sony products and you feel more comfortable in an environment where quality is important.

2. Sony is at the forefront of new developments and you not only feel that you would be stimulated by such an environment, but also you would be enabled to reach your maximum creative potential.

[cypher_soundz]

Great, thanks for the reply! This is what I was looking for :) I can build from this to hopefully fulfil their requirements. I like the way you have worded these, it sounds very professional. I think it’s time for me to be a little more creative in my answers.
Although I try and put across the same points it would never sound as good as the way you have put it. Could you give me any other pointers?
I greatly appreciate the replies.
Regards
cyph

[Guest]

Well. I've always had a way with words. I can't tell you how to do that. But I'll give you some more advice:

1. Always think of things from the interviewer's perspective. You know what she/he wants. They want a bright, diligent, responsible, creative person that is interested in the work and a good team player. So keep finding ways to suggest that these things are true about yourself. Don't say anything that indicates that you are in it just for you, or money. It's all about spin! For example, you don't say the environment will be good for me because I love stimulation. Instead you say, the environment will be good for me because it enables me to give my best to the job and go the extra mile. It's subtle but it plays to what is important to the interviewer.

2. Be sincere. Interviewers can smell fakirs from a mile away.

3. Don't beat your chest or dwell *too* long on these personal selling points. But don't omit them either! Don't worry, they won't be missed and they will sound more convincing if you don't overplay them. Be matter of fact about it, as if that's just the way you are.

4. Always say things like: "That's an interesting question, I never thought about it from that perspective." That's a big subtle prop to the interviewer, who will be impressed by your perceptiveness!

[Guest]

Here's another good one for software people. Say something like this: "I find that so many people are unwilling or unable to go that last 5% on a project, but I find that 5% is often what determines whether a project succeeds or fails. And I like to succeed."

[sysKin]

I suspect things like "I know how to use braces in javascript so you won't have to block non-IE browsers at your musicstore anymore" is a bad example?...

[fccHandler]

I have no girlfriend, and no social life, so I can easily give 100% of myself unto the greater glory of Sony. ;)

[nFury8]

Originally posted by fccHandler
I have no girlfriend, and no social life, so I can easily give 100% of myself unto the greater glory of Sony. ;)
Excellent! You're hired.
Report to our office at once. :D

[Guest]

You guys are getting close to a rule 11 strike. Don't ruin people's threads. This is not Comedy Central. Thank you.

[cypher_soundz]

@fccHandler & nFury8: On the contrary, I don’t think big companies are really looking for the “zombie nerd” employee.
Regards
cyph

[fccHandler]

Sorry for being foolish. I hope you get the job you want. :)

[shevegen]

but the greater glory of sony is not necessarily the greater glory for you tehehe

[Nic]

Neuron2's advice is excellent...and you're right they really aren't looking for super geeks. Being enthusiastic, playing to your strengths and researching as much about the company and/or job are all important.

And if you get asked a question and you really don't know the answer. Say so, don't try and come up with something flimsy because it will show. Sometimes saying "I don't know" isn't a bad thing.

And be confident, even if you don't feel it. I.e. Smile :)

Good luck mate,
-Nic

[cypher_soundz]

Thanks Nic & neuron2, hopefully i will be able to show them the best bits about me :). I guess only time will tell. :thanks:
Regards
cyph

[b0b0b0b]

good luck with the job interview. I've interviewed a bunch of people, and as it turns out the people with the best attitude were also the smartest and best hires. I've also interviewed at a bunch of places too. I can give examples of typical technical interview (software engineer) questions if you like.

[LordRPI]

When I graduated from university, I was told to get used to saying, "Would you like fries with that?"

And then I moved 3k miles from home.

[sugarmonster]

Originally posted by Nic

And if you get asked a question and you really don't know the answer. Say so, don't try and come up with something flimsy because it will show. Sometimes saying "I don't know" isn't a bad thing.


I can second this one. I've spoken to numerous technical interviewers over the years (including ones who've interviewed me!) and a recurring theme is that they hate BS. No-one can be expected to know everything, and in software engineering roles it's often attitude and the ability to think that are as important as knowledge.

[cypher_soundz]

Great these are exactly the tips I need, that would be really helpful b0b0b0b if you could post some examples thanks.
Regards
cyph

[b0b0b0b]

Some rules of thumb are:
For a programming problem you are supposed to write code for, leave plenty of blank space between lines in case you need to insert code.

For any kind of question, it helps to talk through your thinking.
The interviewer has a lot more to work with than if you were to say "hmmmmm."

Some questions I've come across:
1) code to reverse a linked list. MSFT
2) code to compare two strings. handle boundary cases. MSFT
3) ways to implement a hash table. how often can you expect collisions? (birthday problem) GOOG
4) how would you determine if a web page was "family safe" GOOG
5) how would you implement malloc GOOG
6) come up with ways to count the number of bits set to '1' in a 32 bit integer. fancy answer involves subtraction. there are practical answers along the way. MSFT
7) walk through java code example and demonstrate understanding of overloading and overriding methods. GOOG

That's waht I can remmeber right now. Hope this helps.