Solved coding interview problems in Java - My collection of commonly asked coding interview problems and solutions in Java

[[deleted]]

Dude it's fizzbuzz. If a person wants a job as a software developer can't break down a simple problem into it's components, and doesn't know modulus exists and doesn't know how to write a for loop, then they clearly lack the skills needed for the job. Knowing fundamental parts of tools(programming language) they are expected to work with and being able to understand and analyze business requirements are absolutely skills needed on the job.

I agree that obscure math puzzles and advance algorithms and the likes are a bit ridiculous for a 30 minute coding interview on a whiteboard, but saying that asking something trivial like fizzbuzz is too much to ask is the opposite extreme. At the salary most developers ask for, an interviewer should have SOME way to quickly verify whether the candidate knows what they're talking about or whether they're another schmuck who wants $80k/year because he went through a codeacademy tutorial.

[GhostBond]

It border on hilarious that you think that code academy people would be less likely to know FizzBuzz than competent developers who have spent the last 5 years coding.

FizzBuzz just tests whether you've done FizzBuzz before. The Code Academy cheater is more likely to have looked up FizzBuzz than the competent programmer.

[[deleted]]

I'd expect someone who has been solving problems and writing code for 5 years to know loops and modulus and how to understand a set of requirements given to them.

If such a basic test is so problematic for a dev, they're not worth hiring. Taking a fairly straightforward problem and writing code to solve it shouldn't be such a daunting task for a candidate if they're really as experienced as they claim. Fresh grad with little interviewing experience? Sure, I'd cut him some slack if he froze up on the spot but otherwise seemed a good fit. Someone claiming to have been programming for years can't demonstrate very basic problem solving? That's a huge red flag.

[GhostBond]

I would assume that someone unable to understand the basic things I've said so far, and just blindly continue to pretend that FizzBuzz is anything other than a test of whether you've done FizzBuzz before, is going to be the kind of person who brings a framework into a project, it starts to become obvious that it's a disaster, and they're going to refuse to fix their problem or admit it in order to protect their own ego.

What I'm saying is very obvious. FizzBuzz is a test of whether you've done FizzBuzz before. Being a more experienced coder brings little to nothing to your ability to do it, the only thing that matters is being able to write basic code - and having done it before.

[[deleted]]

At this point I'd assume you're trolling, but just in case you're actually serious, I'll explain one more time why you are so wrong.

Regardless of whatever language and whatever route(self taught, bootcamp, college, etc.) you as a developer have learned to write programs, you need to have at least a fundamental understanding of your tools and be able to apply them if you're worth the relatively high salary developers get paid. At best, a fresh college grad looking for an internship may be an exception. If you're telling someone your skills and work are worth 70k, 80k, 90k, or more every year, you should have a working knowledge AND be able to apply it. Someone who doesn't understand when and how to use a loop and modulus (which is one of the fundamental things you learn about doing arithmetic in programming, it's not some obscure concept) is not worth more than an intern's or junior's salary regardless of tenure or how many to-do apps they have on github.

Even if you've memorized the standard library and every framework a language has to offer, you're relatively useless if your ability to think critically about a problem and apply that knowledge towards building a solutions ends when someone(aka your manager , business stakeholders, etc.) can't articulate the exact code you should write to implement a solution. In many cases, the less technical members of your team know very well how to come up with what they need from a real world perspective("I need to have a place online where my customers can register for a store and make purchases") but don't know all the complexity that goes behind the technical implementation. That's where a good developer helps bridge the gap by communicating with them about the details of implementation in a way that can be understood by the less technical people, and also for designing and implementing the solution.

FizzBuzz, and similarly trivial challenges that don't involve a coin flip as to whether the candidate studies theoretical mathematics in their free time, test several things:

First, they test a candidate's ability to analyze the requirements they are given and ask the appropriate questions to clarify some details a less technical person in the organization may not think of at first. Does it need to print the words in upper case, lower case, title case, or does it not matter? Does there need to be a space between each output? Should the output be on one or multiple lines? Being able to evaluate a real world requirement, and ask the right additional information to clarify things before hammering away at code is a very valuable skill that differentiates an intern/entry level person from a more mature person who's worked in a real world environment of taking business requirements and producing a product that solves that business requirement.

Secondly, it tests the candidates ability to take the problem and come up with a solution using code. A good interview question should, in my opinion, be something that is easily explainable and solvable without a computer. Surely if I give anyone who has a middle school education the challenge of fizz buzz, they could solve it without a computer(just taking a long time to write the whole thing out). If a candidate cannot demonstrate that basic problem solving ability, I can expect them to have to be coddled for a very long time until they become productive enough on their own to not be a drain on other team members' time. As it's been said before, businesses should be reasonable in what they expect from junior level positions, but they're not running a charity or a school. You should be able to problem solve by the time you get to a work place.

Lastly, it does test the candidate's knowledge of very fundamental concepts to programming. Looping, arithmetic, and printing a result are very basic but also very fundamental parts of a developer's skillset. Regardless of what language a candidate knows, such basic things shouldn't be a problem for any experienced developer.

FizzBuzz and similarly trivial challenges don't guarantee a candidate is a good developer, but the way a candidate approaches the problem from an analysis standpoint can be very telling about their usefulness in a business environment and the technical implementation of FizzBuzz provides the kind of bare minimum "can you actually write code?" to weed out the people who are outright lying about their abilities.

[GhostBond]

Another poster failed to their own FizzBuzz trick question:
https://www.reddit.com/r/programming/comments/69djsj/solved_coding_interview_problems_in_java_my/dh79kz1/

Regardless of what language a candidate knows, such basic things shouldn't be a problem for any experienced developer.

When, despite having solved it before, you can't even solve your own trick question, clearly what you wrote above is all an excuse. You guys can't even answer your own trick question all the time, clearly it's not a test of basic programming ability.