You're reading from The Complete Coding Interview Guide in Java An effective guide for aspiring Java developers to ace their programming interviews

Product type Paperback

Published in Aug 2020

Publisher Packt

ISBN-13 9781839212062

Length 788 pages

Edition 1st Edition

Languages

Java

Concepts

Programming Language

Author (1):

Anghel Leonard

View More author details

Table of Contents (25) Chapters

Preface

1. Section 1: The Non-Technical Part of an Interview

2. Chapter 1: Where to Start and How to Prepare for the Interview FREE CHAPTER

3. Chapter 2: What Interviews at Big Companies Look Like

4. Chapter 3: Common Non-Technical Questions and How To Answer Them

5. Chapter 4: How to Handle Failures

6. Chapter 5: How to Approach a Coding Challenge

7. Section 2: Concepts

8. Chapter 6: Object-Oriented Programming

9. Chapter 7: Big O Analysis of Algorithms

10. Chapter 8: Recursion and Dynamic Programming

11. Chapter 9: Bit Manipulation

12. Section 3: Algorithms and Data Structures

13. Chapter 10: Arrays and Strings

14. Chapter 11: Linked Lists and Maps

15. Chapter 12: Stacks and Queues

16. Chapter 13: Trees and Graphs

17. Chapter 14: Sorting and Searching

18. Chapter 15: Mathematics and Puzzles

19. Section 4: Bonus – Concurrency and Functional Programming

20. Chapter 16: Concurrency

21. Chapter 17: Functional-Style Programming

22. Chapter 18: Unit Testing

23. Chapter 19: System Scalability

24. Other Books You May Enjoy

Leave a review - let other readers know what you think

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.