• Hey Guest. Check out your NeoGAF Wrapped 2025 results here!

My company is trying to hire competent developers

Status
Not open for further replies.
I have a question..Are Link-List questions ever asked? Like for optimization?
Don't go in expecting specific questions... repeating canned answers is silly. But if you find that you don't interview well without a lot of preparation, yes, you should definitely be prepared to be grilled on data structures like linked lists, trees, and graphs in addition to algorithmic questions like the ones we've been talking about for most of this thread and the more open-ended questions about how you work.
 
You know strings are arrays of characters right? Reversing a string is reversing an array. Your comment is quite the exaggeration.
I just want to come back to this one more time. I don't think I was exaggerating, because while your technical answer might be true, I view coding only in the practical sense. If for any reason you need to reverse an array, it would be in no relation to a situation where you need to reverse a string. The methods being used will also be different and the way you handle the end result. I'd like to put more emphasize to the why, why would you need to reverse an array? Why would you need to reverse a string? The answers would be completely different, so therefor the coding, the handling, the input, the output are all completely different.
 
I just want to come back to this one more time. I don't think I was exaggerating, because while your technical answer might be true, I view coding only in the practical sense. If for any reason you need to reverse an array, it would be in no relation to a situation where you need to reverse a string. The methods being used will also be different and the way you handle the end result. I'd like to put more emphasize to the why, why would you need to reverse an array? Why would you need to reverse a string? The answers would be completely different, so therefor the coding, the handling, the input, the output are all completely different.

I like how you already know every possible situation in the world where you might want to reverse an array, even before youve encountered the situation, and already know that its completely different than every situation where you might want to reverse a string.
 
Am I missing a level of complexity here? I could probably write a recursive function to produce the Fibonacci sequence in a handful of lines.

He's talking about large-scale algorithmic time complexity. The recursive version gets exponentially more taxing with each new call, whereas a simpler version may increase linearly, or something.

Edit: uh, I think I'm 13 pages late.
 
I just want to come back to this one more time. I don't think I was exaggerating, because while your technical answer might be true, I view coding only in the practical sense. If for any reason you need to reverse an array, it would be in no relation to a situation where you need to reverse a string. The methods being used will also be different and the way you handle the end result. I'd like to put more emphasize to the why, why would you need to reverse an array? Why would you need to reverse a string? The answers would be completely different, so therefor the coding, the handling, the input, the output are all completely different.

Just because you can't think of a real word scenario where you would need to reverse a string doesn't mean it doesn't happen.

What that guy said is absolutely true. Logically, reversing a string is the same as reversing an array. Doesn't matter at all if that array is of a different type.
 
I did not say that.

It doesn't matter, your argument is still bogus. The two operations are identical.

Soneet said:
I'd like to put more emphasize to the why, why would you need to reverse an array? Why would you need to reverse a string? The answers would be completely different, so therefor the coding, the handling, the input, the output are all completely different.
This makes no sense. Nothing would be different. The "coding" (what does that even mean?) would not be different. the "handling" would not be different. The inputs and outputs would not be different (the input would be an array, possibly of characters, the output would be an array, possibly of characters).

Here are some examples of what this code might look like.

Code:
string s = "abcde";
array a = {1, 2, 3, 4, 5};

s.reverse();
a.reverse();

reverse(s);
reverse(a);

You are lying to yourself if you think that these are different operations, it really is that simple.
 
My Java is a bit rusty, but reversing a string should be pretty straightforward:

Code:
import java.lang.string.enterprise.operations;

...

try {
	StringReverseFactoryUtility lpsrfuFactory = StringReverseFactoryUtilityFactoryUtility.CreateStringReverseFactoryUtility(StringFactoryUtilities.ReverseStringFactory);
	try {
		StringReverser lpsrStringReverser = lpsrfu.CreateStringReverser("".getClass(), ReverseType.NormalReverse | ReverseType.IgnoreCase | ReverseType.EncodingUTF8 );
		try
		{
			string lpszStr = "aaaa"; // set str to aaaa
			string lpszReversedString = lpsrStringReverser.ReverseString(lpszStr);
			assert lpszReversedString == "aaaa";
		}
		catch ( StringReverseException exc ) 
		{
		}
	} 
	catch ( StringReverseFactoryGenerationException exc )
	{
	}
} 
catch ( StringReverseFactoryUtilityFactoryGenerationException exc )
{
}

return 1;
 
@cpp_is_king:

I'm not sure if you're purposely on denial or not. What would you do with that reversed array you made and what would you do with that reversed string?

In a real life scenario, your input would be completely different, your output would be completely different, whatever code you write in between and before the input and after the input would be completely different.

My answer to your snippet of code: So, what's your point!?
I could show some code reversing an user input data string to match a captcha human check and an array of reversed alphabetical sorted recipe menu and they.would.look.nothing.alike.
 
What would you do with that reversed array you made and what would you do with that reversed string?

So your beef is real world application of reversing an array or string?

But when I suggested that, you said you're not saying that.

I'm absolutely confused by what you're trying to say here.
 
@cpp_is_king:

I'm not sure if you're purposely on denial or not. What would you do with that reversed array you made and what would you do with that reversed string?

I wish that posting things like the Picard facepalm ascii art weren't frowned upon / potentially bannable, because it certainly is appropriate here. Anyway, I'm done here. It's amazing that I missed this little gem from a previous page though.

Soneet said:
Wow, I hope I never have to pass interviews like the OP. I had to google what this fib was and I thought 'reverse string' was some super special function (realized afterwards you just meant reversing a string..)

I'm a super fast learner and I've been called a genius several times, been hired at every place I've done work practice, but I would totally fail the OP's test. And tbh, I don't think it would be my fault. Half of my knowledge is Googling something and learning it in 5 seconds (this splits up the good from the bad, the bad just copy and hope it works) and putting it in practical use, not remembering every snippet of code I've written. I rather have team coders be able to answer "can you make this before the deadline" and simply answer yes, no or in my case "with plenty of time left".

Don't misuse the word "talent", which doesn't stand for "having a huge database in your head".

lol.
 
So your beef is real world application of reversing an array or string?

But when I suggested that, you said you're not saying that.

I'm absolutely confused by what you're trying to say here.
What? You were saying that I couldn't think of real life scenarios where one would do that. I only came to my conclusions after thinking of several real life scenarios one would reverse a string and one would reverse an array. Hence why I said they were nothing alike.

"Just because you can't think of a real word scenario where you would need to reverse a string doesn't mean it doesn't happen."
Am I reading this wrong?



@cpp_is_king:

Yeah, F off. Now you're just resorting to insults. I should've known you weren't the type to reason with.
 
If you don't know how to do the problems in the OP, then you're not familiar with very basic (first year) programming concepts. You're not being hired for your Google skills, you're being hired for your experience and understanding of programming concepts.

Also, if you're asked a question during an interview, you don't ask why. You're being hired as a coder, not a business analyst.

Furthermore, going back to some of the answers given...if I were asked to reverse a string in an interview, I don't think I would give an answer that involved using an external method/library. Or, at the very least, I would ask the interviewer what kind of answer he's looking for.

Just because you can Google a solution to a problem and apply it doesn't mean that you're implying good coding practices. The code may work, sure, but it might contribute to your code being an unmaintainable mess. People hiring you should be interested in your ability to bring sound programming concepts and best practices to the table. That's why you hire an experienced developer. Otherwise, you're better off just hiring a college grad for less since they're a dime a dozen.
 
Also, if you're asked a question during an interview, you don't ask why. You're being hired as a coder, not a business analyst.
OP is asking for web coders, then you better have some skill in creating user scenarios than being a blind puppet coder.

Furthermore, going back to some of the answers given...if I were asked to reverse a string in an interview, I don't think I would give an answer that involved using an external method/library. Or, at the very least, I would ask the interviewer what kind of answer he's looking for.
That's kinda like asking "why"...
 
To stay on topic, I've always joked that whenever I feel depressed, I always ask to start interviewing new candidates so I can feel better about myself and superior just because of how horrible and incapable of answering the simplest questions they are.

While the economy itself is lagging, it hasn't really hit developers too hard, because strangely enough, many employers seem to respect how valuable a good one actually is. We're actually looking to hire a few more people where I work, and, contrary to our normal interview results, almost everybody has been very qualified and more than competent enough for our job offering. These were all people voluntarily looking for new employment rather than the bottom people just recovering from a layoff, too.

What? You were saying that I couldn't think of real life scenarios where one would do that. I only came to my conclusions after thinking of several real life scenarios one would reverse a string and one would reverse an array. Hence why I said they were nothing alike.

"Just because you can't think of a real word scenario where you would need to reverse a string doesn't mean it doesn't happen."
Am I reading this wrong?

I have to say I'm not really understanding what you're trying to say here. The act of reversing a string and reversing an array should be, in most cases, identical. After all, from a low-level standpoint, a string is literally an array of chars.

The reason for reversing either is irrelevant, nor should it be relevant in most cases. For the purposes of an interview question it's completely meaningless unless otherwise specified.

Code:
void Reverse(object[] o) {
  for(int i = 0, j=o.Length-1; i < o.Length/2; i++,j-- ) {
    object obj = o[i]; o[i]=o[j]; o[j]=obj;
  }
}
 
OP is asking for web coders, then you better have some skill in creating user scenarios than being a blind puppet coder.

That's kinda like asking "why"...

Follow this advice if you do not like upward mobility in your career.

I think it's fine to ask why given the right context, but people are implying they'd refuse to answer the question during an interview because it does not have an immediate application. If you ask "why?" and the interview says "because I am testing your programming ability", you do it.

I didn't mean it as a straight black/white thing.
 
Okay, I'm not getting this. Several people have said they don't get what I'm saying, but I myself don't see that whenever a string would be need to be reversed, then use that reversed string (and all the coding that does this), would look the same as an array that needs to be reversed, and being used in a reversed state (and all the coding that does this). Even in cases where I do not know if my variable is a string or array, I make sure I do know so I can handle them differently. I don't see how you would come across a piece of a code that reverses an array and a string in a practical sense. By piece of code, I obviously mean whatever comes before it and after it, in a real world application, not just the function that only reverses.
 
Listen, I think it's fine to ask why given the right context, but people are implying they'd refuse to answer the question because it does not have an immediate application. If you ask "why?" and the interview says "because I am testing your programming ability", you do it.

I didn't mean it as a straight black/white thing.

Yes, but there are quite a few young budding software developers coming to this thread looking for advice and will take your statement as black/white. I'd much more encourage them to be inquisitive in their approach to problem solving situations. I do understand where you are coming from though with all of this weirdness going on about reversing arrays.
 
Okay, I'm not getting this. Several people have said they don't get what I'm saying, but I myself don't see that whenever a string would be need to be reversed, then use that reversed string (and all the coding that does this), would look the same as an array that needs to be reversed, and being used in a reversed state (and all the coding that does this). Even in cases where I do not know if my variable is a string or object, I make sure I do know so I can handle them differently. I don't see how you would come across a piece of a code that reverses an array and a string in a practical sense. By piece of code, I obviously mean whatever comes before it and after it, in a real world application, not just the function that only reverses.

First off, they don't need to be handled differently. You're either looking at an array of Objects or an array of chars (who have the Object superclass). You could make a method that reversed an array of objects and it would be perfectly applicable to a String if you were to pass it as an array of characters. There's no reason to handle them differently...you'd just be producing duplicate code for no reason (which is a no-no).

Even so, it doesn't matter. He's simply testing your ability to produce a very simply algorithm to reverse an array. Can you write a for loop?

Yes, but there are quite a few young budding software developers coming to this thread looking for advice and will take your statement as black/white. I'd much more encourage them to be inquisitive in their approach to problem solving situations. I do understand where you are coming from though with all of this weirdness going on about reversing arrays.

Yeah, sorry, I was definitely too black/white in my statement.
 
Okay, I'm not getting this. Several people have said they don't get what I'm saying, but I myself don't see that whenever a string would be need to be reversed, then use that reversed string (and all the coding that does this), would look the same as an array that needs to be reversed, and being used in a reversed state (and all the coding that does this). Even in cases where I do not know if my variable is a string or array, I make sure I do know so I can handle them differently. I don't see how you would come across a piece of a code that reverses an array and a string in a practical sense. By piece of code, I obviously mean whatever comes before it and after it, in a real world application, not just the function that only reverses.

Maybe if you explicitly wrote out the code you're thinking of...
 
OP is asking for web coders, then you better have some skill in creating user scenarios than being a blind puppet coder.
You should be able to formulate basic algorithms. Reversing a string is a very basic one.

You need to be able to do more than just architect the system. If you cant't think of how to actually efficiently implement the system, your design might as well come from a managers notes on what the requirements are.
 
Okay, I'm not getting this. Several people have said they don't get what I'm saying, but I myself don't see that whenever a string would be need to be reversed, then use that reversed string (and all the coding that does this), would look the same as an array that needs to be reversed, and being used in a reversed state (and all the coding that does this). Even in cases where I do not know if my variable is a string or array, I make sure I do know so I can handle them differently. I don't see how you would come across a piece of a code that reverses an array and a string in a practical sense. By piece of code, I obviously mean whatever comes before it and after it, in a real world application, not just the function that only reverses.

Your original statement was that reversing an array is nothing like reversing a string. Now you're saying you only have to do certain things differently when reversing an array of a different type.
 
I should also add, that there's a very big difference on being a good problem solver and a good coder or software architect. Going through school, you learn how to solve some pretty complex things, but you don't really learn good practices for creating maintainable code. That simply takes experience.
 
Maybe if you explicitly wrote out the code you're thinking of...
Eh... I really was hoping not to resort to something like this... (since it's a waste of time T_T)


Code:
if ($_GET['user_captcha_text']) {

 $realtext = whatever::functiongetogetreversedcaptchatext();
 if ($realtext == strrev($_GET['user_captcha_text'])) {
	echo 'bla';
 } else {
	echo 'bla2';
 }

} else {

 die('no user captcha data');

}


Code:
$menu = array('Beef' => '2301', 'Chicken' => '2302', 'Fish' => '2401');
$reversed_menu = array_reverse($menu);

foreach ($reversed_menu as $title => $link) {
	echo '<h1><a href="http://website.com/menu/'.$link.'.html">'.$title.'</a></h1>';
}

Just a random untested nonsense code I've written just now based on examples I mentioned earlier. Working with a string and working with arrays, I don't think I ever had written code where I would share usage with those type of objects.


Your original statement was that reversing an array is nothing like reversing a string. Now you're saying you only have to do certain things differently when reversing an array of a different type.
Yes, I'm partially wrong in that regard (my original statement). I'm the type of guy who would first go with his gut instinct and say "What the hell are you smoking!?" if someone says a reversed string is the same as a reversed array, as my first line of thought isn't the object heritage but rather a top-down view starting with the user.
 
Eh... I really was hoping not to resort to something like this... (since it's a waste of time T_T)


Code:
if ($_GET['user_captcha_text']) {

 $realtext = whatever::functiongetogetreversedcaptchatext();
 if ($realtext == strrev($_GET['user_captcha_text'])) {
	echo 'bla';
 } else {
	echo 'bla2';
 }

} else {

 die('no user captcha data');

}


Code:
$menu = array('Beef' => '2301', 'Chicken' => '2302', 'Fish' => '2401');
$reversed_menu = array_reverse($menu);

foreach ($reversed_menu as $title => $link) {
	echo '<h1><a href="http://website.com/menu/'.$link.'.html">'.$title.'</a></h1>';
}

Just a random untested nonsense code I've written just now based on examples I mentioned earlier. Working with a string and working with arrays, I don't think I ever had written code where I would share usage with those type of objects.


Yes, I'm partially wrong in that regard (my original statement).

The relevant sections are only array_reverse($array) and strrev($string). The rest is just formatting and usage of input and output, which are irrelevant to the question.

In PHP, sure, they'll be different function calls. But from an algorithmic standpoint, they're the same operation.

Besides the function names, and parameter types, what is different between the two operations?
 
This thread makes me feel really good about my first year of my Software Engineering degree, I'll tell you that much.
 
Soneet, it looks to me like you are focused on when reversing a string might be used versus when a reversed array might be used. I'd say that you're focusing on the wrong thing. The discussion so far seems to have been about how the logic behind reversing a string is pretty much the same as reversing an array. We aren't talking about the end product itself. We're talking about the process behind getting to that end product.
 
You should be able to formulate basic algorithms. Reversing a string is a very basic one.

You need to be able to do more than just architect the system. If you cant't think of how to actually efficiently implement the system, your design might as well come from a managers notes on what the requirements are.

YES. Formulating real-life scenarios is one thing. Actually coming up with a solution is another.
 
Soneet, it looks to me like you are focused on when reversing a string might be used versus when a reversed array might be used. I'd say that you're focusing on the wrong thing. The discussion so far seems to have been about how the logic behind reversing a string is pretty much the same as reversing an array.
Then there's nothing to argue.


The relevant sections are only array_reverse($array) and strrev($string). The rest is just formatting and usage of input and output, which are irrelevant to the question.

In PHP, sure, they'll be different function calls. But from an algorithmic standpoint, they're the same operation.

Besides the function names, and parameter types, what is different between the two operations?
I'd just like to say I don't like this way of thinking. I really don't see the use of someone saying it's the same thing, period, when the entire practical use is different. This also means you can't make an extended, advanced, customized reverse function, since string usage and array usage are completely different. Yes, I can't argue the basic function is the same thing. If you think that's the end of the story, then so be it, but I respectfully disagree.
 
Reversing a string.

Do Fib recursively.

I don't think those are jerk questions.

I once had a Columbia Computer Science Master Students that couldn't reverse a string in a language of his choices.
This can't be true, even for a bad student ...

Code:
string reverseStr(string original) {
	string reversed;
	reversed = original; //Did this to initialize reversed with the same length
	int i = original.length() - 1;
	for (int j = 0; i >= 0; i--, j++) {
		reversed[j] = original[i];
	}
	return reversed;
}
I would iterate only through the first half of the string cause the reverse it's specular, so you switch the "opposite chars".
 
This can't be true, even for a bad student ...
It took me 3 seconds to find out the PHP reverse function. I mean, I know it exists, I've used it before, but I don't remember all the functions perfectly (especially if I have to deal with multiple languages). If I had to do such a type of interview, I would fail.
 
It took me 3 seconds to find out the PHP reverse function. I mean, I know it exists, I've used it before, but I don't remember all the functions perfectly (especially if I have to deal with multiple languages). If I had to do such a type of interview, I would fail.

I understand that plenty of programming languages these days have libraries that will handle these kinds of things, but the reason you ask a question like that is to see if that particular candidate can come up with a decent solution to a very easy problem.

If I were interviewing you and I asked:

"In pseudo-code, write me a function that can reverse the characters in a string"

You wouldn't be able to do so?
 
Don't go in expecting specific questions... repeating canned answers is silly. But if you find that you don't interview well without a lot of preparation, yes, you should definitely be prepared to be grilled on data structures like linked lists, trees, and graphs in addition to algorithmic questions like the ones we've been talking about for most of this thread and the more open-ended questions about how you work.

Thank you.
 
Reversing a string.

Do Fib recursively.

I don't think those are jerk questions.

I once had a Columbia Computer Science Master Students that couldn't reverse a string in a language of his choices.

Any competent developer knows that writing recursive code is dumb and evil (blows up the stack and is very slow). Recursive coding looks cool in text book but not in practice. In many cases writing the same code in a loop takes a lot more work and ingenuity.

These are not the type of questions I would ask when I interview for real talent.
 
It took me 3 seconds to find out the PHP reverse function. I mean, I know it exists, I've used it before, but I don't remember all the functions perfectly (especially if I have to deal with multiple languages). If I had to do such a type of interview, I would fail.
Not remembering a function name isn't a problem you can always search on internet and when you use it often enough you already remember its name.
Point is that you don't really need a pre-made function to reverse a string.
It should be a basic of every programmer to know how do themselves a function like that.

Same apply for the Fibonacci recursion.
You could not know what Fibonacci numbers are but how to do a recursive function to calculate them is very simple ( basically it's the definition of the sequence itself ).

Questions like that are used to understand if you have basic programming skills, not if you know how to resolve the specific task.
 
I understand that plenty of programming languages these days have libraries that will handle these kinds of things, but the reason you ask a question like that is to see if that particular candidate can come up with a decent solution to a very easy problem.

If I were interviewing you and I asked:

"In pseudo-code, write me a function that can reverse the characters in a string"

You wouldn't be able to do so?
Unless I'm 100% certain the code will work, I cannot lie and say that I could. I know what I need, like string position or how to check string length or whatnot, but without being behind a computer with internet access, I wouldn't be able to write it. And if by 'pseudo' you mean fake, then I really can't do it. My mind goes nuts trying to think of fake code. It reminds me of helping other people's coding, then I look at it, see what they try to do, but completely fail at it.


Not remembering a function name isn't a problem you can always search on internet and when you use it often enough you already remember its name.
Point is that you don't really need a pre-made function to reverse a string.
It should be a basic of every programmer to know how do themselves a function like that.

Same apply for the Fibonacci recursion.
You could not know what Fibonacci numbers are but how to do a recursive function to calculate them is very simple ( basically it's the definition of the sequence itself ).

Questions like that are used to understand if you have basic programming skills, not if you know how to resolve the specific task.
But that's kind of the problem. The OP would interview with those kind of questions. If you just happened to know there's a string reverse function, but don't recall the exact function name, then you would answer that you don't know. No one in their right mind would reverse a string manually if they know about a built-in one.

I can do a Fibonacci recursion... but not before this thread where I had to Google what the heck a Fibonacci is. You can't Google during an interview. These kind of questions would totally kill me. I rather have 1 week of a try out and prove myself, then have such weird questions. Fortunately people usually just look at portfolios.
 
Unless I'm 100% certain the code will work, I cannot lie and say that I could. I know what I need, like string position or how to check string length or whatnot, but without being behind a computer with internet access, I wouldn't be able to write it. And if by 'pseudo' you mean fake, then I really can't do it. My mind goes nuts trying to think of fake code. It reminds me of helping other people's coding, then I look at it, see what they try to do, but completely fail at it.

Sounds to me like you're really just able to emulate other people's solutions, not implement your own. You wouldn't be suited to a senior programming position as it stands.

I would highly suggest learning to work with pseudo code and basic design diagrams. It's knowledge and experience that is applicable and very valuable to software projects.
 
Unless I'm 100% certain the code will work, I cannot lie and say that I could. I know what I need, like string position or how to check string length or whatnot, but without being behind a computer with internet access, I wouldn't be able to write it. And if by 'pseudo' you mean fake, then I really can't do it. My mind goes nuts trying to think of fake code. It reminds me of helping other people's coding, then I look at it, see what they try to do, but completely fail at it.

I think that's the purpose of questions like this - to identify individuals who can't do something basic without looking it up.
 
Unless I'm 100% certain the code will work, I cannot lie and say that I could. I know what I need, like string position or how to check string length or whatnot, but without being behind a computer with internet access, I wouldn't be able to write it. And if by 'pseudo' you mean fake, then I really can't do it. My mind goes nuts trying to think of fake code. It reminds me of helping other people's coding, then I look at it, see what they try to do, but completely fail at it.

Are you self-taught? Pseudo-code and algorithmic thinking is literally the first thing they taught us at uni.
 
It took me 3 seconds to find out the PHP reverse function. I mean, I know it exists, I've used it before, but I don't remember all the functions perfectly (especially if I have to deal with multiple languages). If I had to do such a type of interview, I would fail.

...

...

...well, first of all, if you replied, "I'd use google to find the built-in function in PHP and just use that," you'd probably get some credit.

But more importantly, you're missing the point. The interviewer isn't expecting you to remember how to use the library function. The interviewer is asking you to perform an extremely basic array manipulation task.

If you can't reverse an array with a for loop, then yeah, you deserve to fail the interview.
 
I am a Web Developer in NYC working for a law publishing company... we just hired two senior web producers along with some project managers who are mildly efficient in coding.

Haven't noticed a drought too much, though I believe the second producer we hired took a little longer than expected to find. That being said, we weren't hiring Seniors or Project Leaders (just mid-line developers) so they may not be as qualified enough for what your company was looking for. I took the competency test though that was required of them and it was pretty complicated.
 
Are you self-taught? Pseudo-code and algorithmic thinking is literally the first thing they taught us at uni.
I'm in my last year of CS, aced all projects, most of the group code comes from me (heck, other groups were even copying shit from me), but my knowledge comes mostly from work practice or at home.

I'm Googling pseudo-code and algorithmic thinking: WTF is this xD?
I understand it but I never got this. I went dumped into coding, designing and even business related things straight away.


...

...

...well, first of all, if you replied, "I'd use google to find the built-in function in PHP and just use that," you'd probably get some credit.

But more importantly, you're missing the point. The interviewer isn't expecting you to remember how to use the library function. The interviewer is asking you to perform an extremely basic array manipulation task.

If you can't reverse an array with a for loop, then yeah, you deserve to fail the interview.
I've never been in an interview where I had to code on the spot. That's just weird.
 
Something is definitely wrong with your curriculum, in that case. That's not a knock against you, either.

Hell, I went to school as a Computer (Hardware) Engineer and they never taught me how to write a driver. =\

I've never been in an interview where I had to code on the spot. That's just weird.

Most software related interviews I've seen/heard about have a pre-screening test, where they'll bring a group of candidates in and have them complete a written test before making it to the verbal interview.

I don't have much interview experience myself...I only did a small handful of interviews during my first co-op term at school, and I stayed with the same employer after graduation.
 
Something is definitely wrong with your curriculum, in that case. That's not a knock against you, either.

Hell, I went to school as a Computer (Hardware) Engineer and they never taught me how to write a driver. =\
Well, I do always complain about it and how I learn close to nothing for my tuition, so that might be it. However, because of this you could say I would fail OP's interview miserably. But I'd argue that I would probably be a one of the better (or the best, which is what I always aim for) programmer if they hired me. My 1st post in this thread, I mentioned that the term 'talent' shouldn't be misunderstood. Questions like in the OP doesn't scout talent.


Most software related interviews I've seen/heard about have a pre-screening test, where they'll bring a group of candidates in and have them complete a written test before making it to the verbal interview.
That actually sounds nice. It's the combination of a real-time verbal interview + coding on the spot (without internet) that would completely freak me out.
 
As an engineer, I have been asked the following questions at an interview:

- design a state machine to decode morse code on the white board (success)
- What does "static" mean in C++ (failed - could remember that it had multiple definitions but couldn't think of one)
- Ohm's Law (lol success)
- Kirkov's Current Law (success)
- What is the Fourier transform of an impulse function (success)


But at none of those two separate interviews did I actually get the fucking job. I must be a terrible interviewee.
 
As an engineer, I have been asked the following questions at an interview:

- design a state machine to decode morse code on the white board (success)
- What does "static" mean in C++ (failed - could remember that it had multiple definitions but couldn't think of one)
- Ohm's Law (lol success)
- Kirkov's Current Law (success)
- What is the Fourier transform of an impulse function (success)


But at none of those two separate interviews did I actually get the fucking job. I must be a terrible interviewee.

Those sound like questions appropriate to an experienced position (well, other than Ohm's law, lol).

I have no clue what's up with the OP's interviewees...they must have a terrible pre-screening process. That's all I can summise.
 
Status
Not open for further replies.
Top Bottom