3 ms·

As a junior CS student - I haven't heard about these before... Kind of scared - Should I know about these kind of advanced things before I get out of school? I'

As a junior CS student - I haven't heard about these before... Kind of scared - Should I know about these kind of advanced things before I get out of school? I'm not attending a particularly 'rigorous' university for CS

redblacktree 11y ago
I wouldn't worry about it too much. You're expected to have some holes in your knowledge, especially as a fresh graduate. Be prepared to talk generally about different data structures, and it's good to know the big-O time complexity of the common operations/algorithms. But the bottom line is that developers are in such high demand that you'll get a job somewhere. After you work there a couple of years, your experience will be worth more than your degree. (Though the degree is still valuable, if you learned the theory/concepts well)
- ghrifter 11y ago
  I've already worked 2 years as a intern for a tech company (full stack programming, webmaster duties, etc), so I feel like I'm in a good place. I just want to get a good tech job in the Northwest US and as far as I understand it is competitive Edit: Thanks for the response - I'm enjoying learning about data structures and advanced things with data structs
- geebee 11y ago
  I wish that it were more like you've described here, but unfortunately, my experience is that the interviews will be very challenging, that you will need to know data structures very well, and that it really won't be enough to talk generally about these things. It might not even be enough to talk generally in a way that shows you understand how to use a data structure to solve a problem and sketch out a bit of code. It depends on the company, but to get an offer, you may need to write more or less accurate code at a whiteboard that solves a problem efficiently. Some minor syntax errors aren't a big deal, but overall, the code will need to be pretty tight and be close to working. Again, this is in my experience (I have interviewed at amazon and google, as well as smaller startups that seem to do the same thing). I'd highly recommend "cracking the coding interview", and make sure you can handle even the moderate to difficult problems in about an hour at a whiteboard. Before you go to that, though, go back to your data structures and algorithms book and make sure you can do basic list, stack, queue, binary tree, hash, and binary operations. In other words, you should be able to build and print a linked list or binary search tree without much thought - if you can't do this, there's no way you'll be able to solve unanticipated whiteboard problems that use linked lists, trees, or other core data structures in a more elaborate way. Your experience will be worth more than your degree, eventually, but you probably will still need to pass the technical interview/exams when you change jobs, even at more senior technical levels. I'm not saying this is good, just saying this is how it is.
  - redblacktree 11y ago
    My experience in the midwest is much different. I know of a number of folks who were hired as developers with no coding/whiteboarding required. That said, I would expect an interview at Google or Amazon to be tougher. Given their name recognition, they can afford to be choosy. The vast majority of companies cannot.
troels 11y ago
It seems rather ridiculous to ask graphics-programming questions of someone interviewing for a server side position. I don't think any kind of preparation would help you with that kind of questions.
- santaclaus 11y ago
  I asked the recruiter I had been working with about it, and her response was along the lines of: 'We only hire engineers who are capable of tackling any problem faced by the company.' ...
  - ghrifter 11y ago
    So in other words they want that mystical 10x engineer
- nitrogen 11y ago
  There is one kind of preparation: having graphics programming as a hobby, or failing that, an interest in everything under the sun and nonstop studying.
MichaelGG 11y ago
If you read an algorithms book, like Sedgwick's, you should be mostly set. Usually they're trying to figure out who actually understands how pointers, memory, and complexity work. (A lot of devs don't know basics at all, like binary search or even how to do am in place reversal of an array or something). I wouldn't expect a very genre specific question (like graphics) unless they provided enough info that you could figure it out from first principles. And sometimes they just wanna make sure you can think it through, even if you don't find the most optimal solution. A lot of devs simply give up with an "I don't know", without indicating that they have any ideas on how they'd figure it out.

redblacktree 11y ago

I wouldn't worry about it too much. You're expected to have some holes in your knowledge, especially as a fresh graduate. Be prepared to talk generally about different data structures, and it's good to know the big-O time complexity of the common operations/algorithms. But the bottom line is that developers are in such high demand that you'll get a job somewhere. After you work there a couple of years, your experience will be worth more than your degree. (Though the degree is still valuable, if you learned the theory/concepts well)

ghrifter 11y ago
I've already worked 2 years as a intern for a tech company (full stack programming, webmaster duties, etc), so I feel like I'm in a good place. I just want to get a good tech job in the Northwest US and as far as I understand it is competitive Edit: Thanks for the response - I'm enjoying learning about data structures and advanced things with data structs
geebee 11y ago
I wish that it were more like you've described here, but unfortunately, my experience is that the interviews will be very challenging, that you will need to know data structures very well, and that it really won't be enough to talk generally about these things. It might not even be enough to talk generally in a way that shows you understand how to use a data structure to solve a problem and sketch out a bit of code. It depends on the company, but to get an offer, you may need to write more or less accurate code at a whiteboard that solves a problem efficiently. Some minor syntax errors aren't a big deal, but overall, the code will need to be pretty tight and be close to working. Again, this is in my experience (I have interviewed at amazon and google, as well as smaller startups that seem to do the same thing). I'd highly recommend "cracking the coding interview", and make sure you can handle even the moderate to difficult problems in about an hour at a whiteboard. Before you go to that, though, go back to your data structures and algorithms book and make sure you can do basic list, stack, queue, binary tree, hash, and binary operations. In other words, you should be able to build and print a linked list or binary search tree without much thought - if you can't do this, there's no way you'll be able to solve unanticipated whiteboard problems that use linked lists, trees, or other core data structures in a more elaborate way. Your experience will be worth more than your degree, eventually, but you probably will still need to pass the technical interview/exams when you change jobs, even at more senior technical levels. I'm not saying this is good, just saying this is how it is.
- redblacktree 11y ago
  My experience in the midwest is much different. I know of a number of folks who were hired as developers with no coding/whiteboarding required. That said, I would expect an interview at Google or Amazon to be tougher. Given their name recognition, they can afford to be choosy. The vast majority of companies cannot.

troels 11y ago

It seems rather ridiculous to ask graphics-programming questions of someone interviewing for a server side position. I don't think any kind of preparation would help you with that kind of questions.

santaclaus 11y ago
I asked the recruiter I had been working with about it, and her response was along the lines of: 'We only hire engineers who are capable of tackling any problem faced by the company.' ...
- ghrifter 11y ago
  So in other words they want that mystical 10x engineer
nitrogen 11y ago
There is one kind of preparation: having graphics programming as a hobby, or failing that, an interest in everything under the sun and nonstop studying.

MichaelGG 11y ago

If you read an algorithms book, like Sedgwick's, you should be mostly set. Usually they're trying to figure out who actually understands how pointers, memory, and complexity work. (A lot of devs don't know basics at all, like binary search or even how to do am in place reversal of an array or something). I wouldn't expect a very genre specific question (like graphics) unless they provided enough info that you could figure it out from first principles. And sometimes they just wanna make sure you can think it through, even if you don't find the most optimal solution. A lot of devs simply give up with an "I don't know", without indicating that they have any ideas on how they'd figure it out.