About to get my Bachelor's in CS. Don't know how to program.

[Chesssbrah]

I don't like coding either but confused to see people struggling so much with fizz buzz lol

[barbecueyeah]

If this is a cry thread for soon to be graduates, let me join in.

tfw when you applying for jobs and they give you those 10 minute logical tests and you score below average. Breaks your spirit so fukkin hard. Not sure if I should dismiss these tests as bullchit or interpret it as I'm too stupid to be a programmer.

[Brad155]

If this is a cry thread for soon to be graduates, let me join in.

tfw when you applying for jobs and they give you those 10 minute logical tests and you score below average. Breaks your spirit so fukkin hard. Not sure if I should dismiss these tests as bullchit or interpret it as I'm too stupid to be a programmer.

I promise you that most programmers aren't getting those questions either. As I posted earlier, we have interviewed countless applicants, and if any one of them performed well on these questions we would have hired them on the spot.

I think some of it is nerves and some of it is unpreparedness for the interview format. We start by giving a roughly one hour aptitude test that is language independent (they gave it to me as an EE too even though I'm not a "programmer" because it is mostly a logic/reasoning/quickness test). Then we spend another hour with pretty much the whole R&D department giving bull**** google type questions (logical/mathematical puzzles). People fail really hard at both of these. They do okay for the actual interview parts that follow, until the practical test where we have them write (what should be) some simple programs, and I believe we have only had one applicant correctly solve the programming problem to completion (he spoke very little english though which was unfortunate, management wouldn't hire him because they were nervous they wouldn't be able to communicate... which is fair to be honest)

Anyway, don't feel bad for not doing well with some of these interview questions, you really are not alone. Interviewers do a very bad job of making the interviewee feel comfortable and I believe that is a big part of it.

[DatOneDood]

cout << "awe fuk bye" << endl;

[Rawp0wer1O1]

Why is there such a high demand for developers / programmers ?

Uh because you'd be hard pressed to find anything in the world that doesn't receive some sort involvement from a computer

[GhostRider111]

Im a senior too and about to graduate next spring and also dont know how to program

The way i got by is group projects and getting carried in group projects

Do you even need to know how to program anymore these days?

[yg7s7]

I read that many CS majors fail job interviews bc they don't know how to code to save their lives

[Rawp0wer1O1]

If this is a cry thread for soon to be graduates, let me join in.

tfw when you applying for jobs and they give you those 10 minute logical tests and you score below average. Breaks your spirit so fukkin hard. Not sure if I should dismiss these tests as bullchit or interpret it as I'm too stupid to be a programmer.

I'm a developer and would probably do poorly as well. Mainly due to the stress and being put on the spot. My best work comes when I have my head phones on, it's past 1am, and I have a nice cold monster energy drink in my hand.

I found this online and it gives a different point of view

"The problems I face at work are mostly of the type that take weeks or months to solve. They tend to involve understanding user needs, coming up with multiple designs and choosing the best one, prototyping, performance tuning, learning new technologies, and communicating technical issues to management, or brainstorming with a team. My day to day work is so far removed from memorizing Euclid's method for calculating the greatest common divisor that I'd almost certainly fail an interview question about it."

Our software is so complex it may take me a couple months to actually understand what it's doing let alone make any changes.

The absolute BEST advantage you could give your self is to have a project you did yourself to give to your prospective employers.

[Luc1fer]

I graduated Computer Science. I could have easily graduated without knowing how to program. But, that really is dumb as fcuk - companies will have you do technical questions on whiteboards etc. to assess your skill. So yes, I'm not even surprised that you graduated without that knowledge. It's why actual developers are so rare and in-demand.

[BigStewTheJew]

Double major in business but confident in Python and c++ abilities

Lol is there any reason to know this stuff as business major

[yabbayabba]

I promise you that most programmers aren't getting those questions either. As I posted earlier, we have interviewed countless applicants, and if any one of them performed well on these questions we would have hired them on the spot.

I think some of it is nerves and some of it is unpreparedness for the interview format. We start by giving a roughly one hour aptitude test that is language independent (they gave it to me as an EE too even though I'm not a "programmer" because it is mostly a logic/reasoning/quickness test). Then we spend another hour with pretty much the whole R&D department giving bull**** google type questions (logical/mathematical puzzles). People fail really hard at both of these. They do okay for the actual interview parts that follow, until the practical test where we have them write (what should be) some simple programs, and I believe we have only had one applicant correctly solve the programming problem to completion (he spoke very little english though which was unfortunate, management wouldn't hire him because they were nervous they wouldn't be able to communicate... which is fair to be honest)

Anyway, don't feel bad for not doing well with some of these interview questions, you really are not alone. Interviewers do a very bad job of making the interviewee feel comfortable and I believe that is a big part of it.

I really dislike this kind of interview process. On the job if you don't know something you Google it and almost always at least find a starting point on Stack Overflow or some random blog. Creating a memory pool allocator on a white board is something you will never do again (also probably never needed on the job since a team of much smarter true computer scientists have already created one for you). We started just having interviews where we talk about their work history, what they did, what they like doing outside of programming (very important), and any questions they have about us. This generally is an hour and half to two hours. If we like how that goes then we give them a take home programming test that is related to what we do and give them a couple of days to complete it. If that is good then we will hire them on a 60 day contract and if they are still kicking ass at 60 days they become full time. Our quality of hire has went up since doing this. We have not let anybody go with this process. We also make video games, it is a different type of skill set and personality type. Giving people their space to figure things out works much better then having to fill out five TPS reports for everything you do.

[whitepaper]

We started just having interviews where we talk about their work history, what they did, what they like doing outside of programming (very important), and any questions they have about us. This generally is an hour and half to two hours. If we like how that goes then we give them a take home programming test that is related to what we do and give them a couple of days to complete it.

This.

There's was an article about how some company moved to a similar model (I think they gave the problem to the interviewee after the initial phone interview, then had the in-person interview). The problem they gave was related to the work they do/or a similar problem they currently have. They said that the quality of hires they got was exactly what they were looking for, and everyone has been a great fit so far.

[Brad155]

Is the gaming company vicarious visions by any chance? Seems similar to their process.

[Brad155]

I really dislike this kind of interview process. On the job if you don't know something you Google it and almost always at least find a starting point on Stack Overflow or some random blog. Creating a memory pool allocator on a white board is something you will never do again (also probably never needed on the job since a team of much smarter true computer scientists have already created one for you). We started just having interviews where we talk about their work history, what they did, what they like doing outside of programming (very important), and any questions they have about us. This generally is an hour and half to two hours. If we like how that goes then we give them a take home programming test that is related to what we do and give them a couple of days to complete it. If that is good then we will hire them on a 60 day contract and if they are still kicking ass at 60 days they become full time. Our quality of hire has went up since doing this. We have not let anybody go with this process. We also make video games, it is a different type of skill set and personality type. Giving people their space to figure things out works much better then having to fill out five TPS reports for everything you do.

Is the gaming company vicarious visions by any chance? Seems similar to their process.

[Tywin]

Still a newbie programmer, did I do the Fizzbuzz right?


class fizzBuzzTest {
public static void main (String [] args) {
test(100);
}
public static void test(int num) {
for (int i = 1; i <=num; i++) {
if (i % 3 == 0 && i% 5 == 0) {
System.out.println("FizzBuzz.");
}
else if (i % 3 == 0) {
System.out.println("Fizz.");
}
else if (i % 5 == 0) {
System.out.println("Buzz.");
}
else {
System.out.println(i);
}
}
}
}

[Anothersloth]

We gotta learn to program in our engineering courses aswell, but it's not our major. I feel you OP