Book Image

The Complete Coding Interview Guide in Java

By : Anghel Leonard
Book Image

The Complete Coding Interview Guide in Java

By: Anghel Leonard

Overview of this book

Java is one of the most sought-after programming languages in the job market, but cracking the coding interview in this challenging economy might not be easy. This comprehensive guide will help you to tackle various challenges faced in a coding job interview and avoid common interview mistakes, and will ultimately guide you toward landing your job as a Java developer. This book contains two crucial elements of coding interviews - a brief section that will take you through non-technical interview questions, while the more comprehensive part covers over 200 coding interview problems along with their hands-on solutions. This book will help you to develop skills in data structures and algorithms, which technical interviewers look for in a candidate, by solving various problems based on these topics covering a wide range of concepts such as arrays, strings, maps, linked lists, sorting, and searching. You'll find out how to approach a coding interview problem in a structured way that produces faster results. Toward the final chapters, you'll learn to solve tricky questions about concurrency, functional programming, and system scalability. By the end of this book, you'll have learned how to solve Java coding problems commonly used in interviews, and will have developed the confidence to secure your Java-centric dream job.
Table of Contents (25 chapters)
1
Section 1: The Non-Technical Part of an Interview
7
Section 2: Concepts
12
Section 3: Algorithms and Data Structures
19
Section 4: Bonus – Concurrency and Functional Programming

A company can reject you for a lot of reasons

Well, maybe the problem starts exactly with this powerful word: reject. Is it correct to say or think that company X rejected you? I would say that this formulation is toxic and sounds like the company has something personal against you. This formulation of thoughts should be cut off right from the start. Instead, you should try to find out what went wrong.

How about saying or thinking that between you and the company, there are mismatches in skills and/or expectations? Most probably, this is much closer to reality. There are two parties in an interview (you and the interviewer), and both parties try to identify the matches or compatibilities that allow them to collaborate with a subjective approach. Once you think like this, you will not blame yourself and you’ll try to find out what went wrong.

Getting feedback after the interview

If you’ve been informed by the company that you didn’t make the cut, it is...