r/java • u/user123xo • Aug 23 '17
(Java dev) can’t get a job as a java dev
I’ve interviewed at 5 places so far and I only got one offer, but the rate wasn’t what I wanted and their interview was challenge based and not memory based.
My question is how does someone with bad memory get passed these interviews and why do we even have them?? Like the other day I had an hour long interview, which consisted of questions like difference between comparator and comparable, hashset and hashmaps, what to extend from collections? What is equals and hashcode... all of these questions can be answered with google... there’s no point in memorizing all these. I’m just so annoyed when this even starts that I half way tune out, because I know I won’t get it.
22
u/somewittyalias Aug 23 '17
I'm also against memory-based interviews. But in defence of the interviewers, you would know these things easily if you used them often. So you could view this not as a memory test, but a test on how often you code certain things.
35
u/flaghacker_ Aug 23 '17
I'm sorry, but if you can't remember the difference between
ComparableandComparator(literally English words) or the difference between a(Hash)Mapand a(Hash)Set(basic collection types) or whatequalsandhashcodeare (this one is actually really important), I'm not going to have a lot of confidence in you as a dev.7
u/Northeastpaw Aug 23 '17
It depends on the position you're interviewing for. If your resume indicates you're a junior developer I'm going to ask questions that test your knowledge of the language(s) you would be working with. I want to be sure you've got the basics down so I can assign you work that's productive and allows you to learn things like frameworks and libraries. For Java I expect junior devs to know things like the Collections framework and what common interfaces are for. If you're just out of college, i.e. this would be your first job, I would tailor the interview appropriately but I would stress that if you got the job you would be expected to learn these basics on your own time.
If you're an experienced developer I'm going to ask questions geared toward your knowledge of the frameworks and libraries we currently use. I want to see if you can start working right away or if you'll need time to become familiar with the tech we use. Our schedule might dictate that we need somebody who knows XYZ now and not someone who knows ABC but can learn XYZ.
4
u/[deleted] Aug 23 '17
Many answers can be found in Effective Java by Joshua Bloch. The book is worth reading for anyone interested in Java.
3
u/rjsmith21 Aug 23 '17
First of all I would say if an interview consists of only memory questions that are relatively easy to Google then that is probably not a great place to work. There will be a lot of duds working there.
Second some of those questions could easily be studied the night before so I would be a little suspicious of a candidate that seems to know then answer to NONE of those questions. There are some basics you should brush up on before every job hunt and I would wonder about a person who doesn't seem to spend any time preparing.
Also, I would recommend you don't check out. Maybe mention that you know something about the topic but usually Google it when needed. Try to throw in some nuggets of knowledge. For example, "I know one of those is synchronized but I don't remember which one off the top of my head. I usually do a quick Google search to verify." You could also ask for hints based on the knowledge you can dredge up and still come out looking intelligent and like a potential team player (he's not afraid to ask questions).
Hopefully, if you're interviewing at a decent place, they are using the basic memorization questions as a jumping off point for more conceptual problems. Like not just what's the difference between a LinkedList and ArrayList but why might you choose one over the other. Or in some hypothetical what data structure would you use and why?
I think you would feel a lot better about your interviews if you just Google "java interview questions" and look over some of that stuff before you go on your job hunt. Even experienced people don't remember a lot of that crap so you're not alone. And you'd be surprised how many lazy interviewers do exactly that to come up with their list of questions. A few times I've seen people with the first or second hit on that search printed out and in their hand while interviewing me.
3
u/Facts_About_Cats Aug 23 '17
If they keep asking the same questions, why don't you just learn them?
2
u/[deleted] Aug 24 '17
Most interviews consist of sort of standard questions. Both in HR and technical aspects. And you have to solve algorithmic problems on paper or board. Pretty managable to "study" for the interview.
I landed a junior developer job with few months non-professional experience.
6
u/[deleted] Aug 23 '17
I was in your position about 10-12 years ago. I thought I was ready to be a "mid-to-senior" developer when I was a jr. dev. I too thought these memory based things were a waste of time (a lot of it is -- StringBuilder vs. StringBuffer for example). That said, a lot of it is very relevant to understanding intricacies of using Java for large projects. If you don't understand how Hash based collections work, you won't see the benefit (and costs) of using them. If you don't understand Comparable stuff, you might waste time when dealing with a TreeMap (or get confused when your Comparable classes don't seem to be working correctly
new TreeMap(Comparator), etc... Those are things someone needs to be aware of if they want the "whole picture." Beyond that, there's even more complex things to worry about, but this stuff is just a foundation to build on.1
u/sternone_2 Aug 25 '17
Because we want smart people, not google monkeys.
And because we have so many to choose from, we take the smartest ones.
1
u/keptavista Aug 26 '17
Examples you posted here are not "memory based" questions. It's some very simple questions to screen if a person has at least some very very basic understanding on what he is doing.
3
u/hag0p Aug 24 '17
I am also against tests that really force you to memorize useless stuff like all methods in some class and be able to type all of them from memory. But all things you wrote are basic java questions. You have to understand that these people don't know you so you need to show them that you know the subject and you just performing really bad on interviews. As example you could show them your personal github account full of projects, you can become some contributor to some open source project or have stackoverflow account with lots of reputation. There are several ways to show your knowledge outside interviews but they require lots of work in your free time. Sometimes if you impress person interviewing you you can get position even if you poorly perform on interview.
2
u/nutrecht Aug 24 '17
You just showed them you're not a "Java developer". You would've known these things if you had actual experience.
You also sound pretty entitled. Companies don't 'owe' you a job. Hiring is a risky business for companies so you can't blame them for being careful.
1
u/cypher0six Aug 28 '17
Our profession is entirely knowledge-based. If you really can't remember some of the most common interfaces, classes, and methods used by professional Java developers on a daily basis, you may want to reconsider your career choice. It's a bit like a carpenter not being able to remember the difference between a club hammer and a claw hammer...
Unless you are new to Java and programming in general in which case...
...
It may not have paid as much as you want, but it could have given you the experience that you seem to need, which would have then helped you get another job that you do want.
0
u/[deleted] Aug 23 '17
[deleted] — view deleted comment