Employment - New Company
-
I'm applying for a new company as a software developer and they say they are going to make a small exam to see my qualification. Should I be worry and how to be prepared for such exam theoretical part and practical?
-
I'm applying for a new company as a software developer and they say they are going to make a small exam to see my qualification. Should I be worry and how to be prepared for such exam theoretical part and practical?
Unless they gave you some idea of the questions, or at least the technologies/frameworks etc. they use, it is very difficult to prepare in any meaningful way. You could try searching for any information about the company to see if you can find any clues. For example "The Super Widget Corporation is currently making a large investment in Hadoop", or similar. Failing that a search on interview coding questions c# (obviously change c# as applicable) will get you lots of practice stuff.
Henry Minute Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.” I wouldn't let CG touch my Abacus! When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is. Cogito ergo thumb - Sucking my thumb helps me to think.
-
I'm applying for a new company as a software developer and they say they are going to make a small exam to see my qualification. Should I be worry and how to be prepared for such exam theoretical part and practical?
The more you prepare, the less it will test your actual qualifications and the more it will start testing your short-term memory. That is not advice, just something to keep in mind. Personally, I never prepare for anything, but I'm one of those crazy people who learn by understanding instead of by brute-force remembering as much stuff as possible.
-
I'm applying for a new company as a software developer and they say they are going to make a small exam to see my qualification. Should I be worry and how to be prepared for such exam theoretical part and practical?
-
Member 8317792 wrote:
Should I be worry
No, don't worry. Be honest, and for questions you can't answer, mention the way you would use to get the problem solved/question answered in your daily job life.
That is right :-D and as I always say "Google is my best friend"
-
That is right :-D and as I always say "Google is my best friend"
-
The more you prepare, the less it will test your actual qualifications and the more it will start testing your short-term memory. That is not advice, just something to keep in mind. Personally, I never prepare for anything, but I'm one of those crazy people who learn by understanding instead of by brute-force remembering as much stuff as possible.
Excellent point! I remember for my finals at University seeing many people with study notes frantically reading them just before the exam. I had read up on study techniques and discovered that if I used a mnemonic anagram method I could remember vast amounts of information which I could then tie to my understanding - so the exam day was relaxed and relatively stress free - I learnt previously that the worst thing you can do, in the day before an exam, is look at your study notes as you will discover what you don't know and then probably panic....
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
-
I'm applying for a new company as a software developer and they say they are going to make a small exam to see my qualification. Should I be worry and how to be prepared for such exam theoretical part and practical?
I am always more interested in how someone goes about finding out about or solving something they cannot fix at the moment - rather than what they know now. Because work is about learning, not just regurgitating... Have confidence in yourself and be honest - if you are the right person for the job you will get the job ;)
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
-
I'm applying for a new company as a software developer and they say they are going to make a small exam to see my qualification. Should I be worry and how to be prepared for such exam theoretical part and practical?
Depends on how deep they go. Some will ask basic questions, others will go really deep into the core (which are more used to show their own knowledge then to test yours I think). Most basic questions contain: * Database, normalisation, usage of keys, use of indexes, that sort of stuff * logging, how, why, when * performance * usage of basic objects like StringBuilder, writing/reading from files, ... * sometimes framework specific questions like flavours of LINQ, Meaning of a function in Oracle, ... The best test I find is to ask to write a simple application based on some specs with google and msdn enabled, but with a time limit. Incredible how much info you can gather after a monkey typed in random letters on a keyboard in 30 minutes time :-) The more you know about the company the better you can prepare, but preparation remains a wild guess in any case.
V.
-
Depends on how deep they go. Some will ask basic questions, others will go really deep into the core (which are more used to show their own knowledge then to test yours I think). Most basic questions contain: * Database, normalisation, usage of keys, use of indexes, that sort of stuff * logging, how, why, when * performance * usage of basic objects like StringBuilder, writing/reading from files, ... * sometimes framework specific questions like flavours of LINQ, Meaning of a function in Oracle, ... The best test I find is to ask to write a simple application based on some specs with google and msdn enabled, but with a time limit. Incredible how much info you can gather after a monkey typed in random letters on a keyboard in 30 minutes time :-) The more you know about the company the better you can prepare, but preparation remains a wild guess in any case.
V.
Do not say what you don't know. Do answer concisely and to the point. If open ended go into relevant details. If personal you know yourself better than anyone. Agree with almost all previous replies, the more you know about the company, their customers, the position being seek/offered, their benefits, their market share... the better you can answer. Above all, if you are the type that get nervous, try to get a solid sleep and avoid stimulants (coffee,tea...) and if face to face, look straight at the person asking. Don't sweat it, you probably know more than you "think" you know. :)
-
Do not say what you don't know. Do answer concisely and to the point. If open ended go into relevant details. If personal you know yourself better than anyone. Agree with almost all previous replies, the more you know about the company, their customers, the position being seek/offered, their benefits, their market share... the better you can answer. Above all, if you are the type that get nervous, try to get a solid sleep and avoid stimulants (coffee,tea...) and if face to face, look straight at the person asking. Don't sweat it, you probably know more than you "think" you know. :)
-
The more you prepare, the less it will test your actual qualifications and the more it will start testing your short-term memory. That is not advice, just something to keep in mind. Personally, I never prepare for anything, but I'm one of those crazy people who learn by understanding instead of by brute-force remembering as much stuff as possible.
That's why I am so opposed to exams in general! Ever since elementary school I always felt that tests and exams were just a test of your short-term memory. Especially in the case of "I want you all to know the countries and capital cities in Europe next week". One evening before the test (which became hours when I got older): stamp it all in your head and score an A. One hour after the test: "Paris? I only know Paris Hilton..." ;p I've seen some certified programmers that didn't know what the hell they were doing. I'm betting my head on it all of them had a good short-term memory though.
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
}
