This week's book giveaways are in the Jython/Python and Object-Oriented programming forums. We're giving away four copies each of Machine Learning for Business: Using Amazon SageMaker and Jupyter and Object Design Style Guide and have the authors on-line! See this thread and this one for details.
I am at a point in my career where I am thinking of a job change. Your book comes handy at this time . I want to know how many years of Java/JEE experience has this book been written for? Is it only for developers who have around 4-7 years of experience or it covers stuff for technical architects (11-12+ years) or Senior Lead developers (8-10) also ?
I think it's a fair and very interesting question.
Interviews for senior developers have heavier emphasis on soft skills. For example, a lead developer is expected to have some management responsibilities. An architect is expected to have some mentoring capability. You wouldn't interview a developer with 1 year experience on all those things. So, how someone with 10+ years of experience interviews is qualitatively different from how someone with 1 year interviews.
In fact, I would go so far to say that a lot of people who get stagnated in their career after 15 years do so because they are in this mind-set where they expect interviews to be technical, and they are unprepared for a "soft" interview. If you are going to prepare for interviews like a developer with 5 years experience, expect to get a job where you compete with developers 10 years younger than you. If you want to get to the next level, stop thinking of yourself as a developer, and start thinking of yourself as someone who is more than a software developer.
Cheers for the question Pallavi!
With regards to the book, it's suitable for all experience levels, but it's particularly focused on the technical aspect. It's not going to cover dev lead type things, and it's structured around someone who's going to be interviewed based on their developer ability.
I'm strictly avoiding the discussion of years of experience. Jayesh points out that that more experienced interviewees would get hit for more soft skills. However, I think this is unrelated to years of experience. I went into dev management for a couple of years and then intentionally dropped out of it and went back to being "just a dev". This was a conscious choice because I hate management and I love programming. But, this means when I'm interviewing for roles I'm going for developer roles, which means I'm less likely to get asked stuff about dev management and more about code java.
All depends what you want for your career though . The first half of the book is dedicated to soft skills and covers some more senior questions like "design this system for me".
Yes it covers both of those things. There's a full chapter on "tell me about your system", one of my favourite questions, which deep dives on how to explain the design of a system. There's also a large chapter on collections.
Sam Atkinson wrote:Actually the T-rex chapter got cut; I tend to find most firms have stopped asking that question these days. Lincoln is obviously in there though.
Do you have any stories about crazy interview questions? I was talking to a guy one time and he mentioned really bizarre questions he'd heard stores of, I guess attempting to test creativity. I remember one that involved pulling out a paper bag for something... Next edition consider a final humorous chapter of crazy questions.
My cellmate was this tiny ad:
Sauce Labs - World's Largest Continuous Testing Cloud for Websites and Mobile Apps