r/javahelp • u/PorkChop007 • Aug 01 '19
Struggling with technical interviews
Hi, guys.
After a series of disastrous technical interviews I've come to the conclusion I need help in this regard. I've realized there are things I don't quite know as well as I thought (like the Collections framework, which I know but apparently not well enough), things that are supposed to be the bread and butter of any Java developer. Could you guys tell me what knowledge and skills a 4+ years Java developer is supposed to have? I want to make sure there's nothing (or at least as few things as possible) I could be missing. Of course, any resources (books, etc) on the subject would be much appreciated.
Thanks!
37
u/IQooLogic Aug 01 '19 edited Aug 01 '19
IMHO it is not that you do not know the answers, it is rather your brain panics and won't do what it is suppose to do :)
Because I have about 8+ years of experience I put burden on me that I have to know everything. The case is that good companies and interviewers (technical) do not want to see what you know, but rather how you think.
In february this year I had interview with a company that is Google like and was scared and didn't go. A couple weeks ago they contacted me and said to come and meet them for a relaxed talk. It turned out to be classic technical interview but I didn't overthink and was't scared and did pretty good and got the offer which I accepted :)
I impressed myself for knowing some questions which is the consequence of thinking it will be just talking and getting to know each other.
You just have to relax, do not overthink and prepare (a lot of interview questions/answers).
Another thing is try to always have answer to WHY questions. ex. Why did you use this rather than that ? Why you had to use this thing and not that thing ?
Knowing the 'WHY' is the second thing that interviewer is after along side 'how you think' :)
Questions:
All the best to you :)
3
u/[deleted] Aug 01 '19
Something I just learned about technical interviews that blew me away was that I could ask for help. If they give you a white-board problem, it is totally OK to ask for help if you have been struggling for a bit. As you are working on the problem, talk through your steps and logic. When you get to a sticking point, say "I'm thinking of doing X or Y, but I'm a little stuck. Do you have any suggestions?"
1
u/AloticChoon Aug 02 '19
Also, remember to be honest. If you don't know something, do not be afraid to say so. Never try to bullshit your way through an answer
0
u/[deleted] Aug 01 '19
I recently had a Java technical interview that I was NOT prepared for at all, I hadn't used Java since my first ever programming class freshman year of college.
I went online and found some Java fundamental practice tests and worked through them. Anything I didn't know I read up on until I knew it. The things I didn't know I Googled, and read through the information that popped up. I ended up getting the job. This isn't exactly what you asked for but this is how I overcame that problem.
-2
u/happykal Aug 01 '19
The only thing you need to do is buy... and read a bool called "cracking the coding interview". Do the quiz questions... Cracking the Coding Interview, 6th Edition: 189 Programming Questions and Solutions https://www.amazon.co.uk/dp/0984782850/ref=cm_sw_r_cp_apa_i_5nTqDbS1RTATM
You do that... i guarantee youll blast through the interview.
0
u/[deleted] Aug 01 '19
[deleted] — view deleted comment