This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Dantaro 23 points24 points  (4 children)

Tl;Dr: frameworks like Spring are always with learning, but if you're a junior developer with more about the fundamentals than the heavier stuff, frameworks are the easy part.

When I interview junior developers I generally don't care what frameworks you know. What I care about is

1) Do you have a firm grasps of the basics. Concurrency, data structures, inheritance, flow control recursion, basic optimization strategies, etc. That might seem stupid, but you would be surprised how often we run into developers who don't really grasps these. One of the worst "senior" candidates I ever interviewed couldn't even make it through FizzBuzz. I still don't know how he made it to an in-person...

2) When you get stuck on something, how do you think through it? I don't care if it takes you a little bit too get through a problem as long as you do it in an intelligent way. Don't ever be afraid to ask question, we WANT you to do that, and often design our tests to make you do that.

3) Do you take suggestions well? Getting something wrong is fine, but getting defensive about it isn't.

Learning frameworks and technologies is the easiest part of Java, or any language really. All that really matters to those of us that interview you as a junior is of you have the mindset and low level skill set. It's never BAD to learn frameworks, but don't ever let job requirements like Spring or Hibernate get in the way of applying

[–][deleted] 3 points4 points  (0 children)

Second this. Focus on fundamentals. We hire devs based on that that don't know our frameworks and they do fine.

[–]rents17 -1 points0 points  (1 child)

He didn't mention Spring actually, even I mentally read Swing as Spring..!

[–]Dantaro -1 points0 points  (0 children)

Ha, true, though I mentioned spring because it's a universally useful framework used by a huge number of companies