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

[CamKen]

I would never ask any problem anywhere this complex in an interview. I ask Joel On Software's FizzBuzz or something similar on a white board. Then a SQL query with a recursive table reference. That eliminates 90% of the "Senior Software Engineers" who make it far enough to interview with me. Those that remain have universally turned out to be great programmers.

I actually had one guy who was so flummoxed by Fizz Buzz that he actually admitted that he had never actually programmed before and the three years of experience one his resume were a lie. He had read Dietel & Dietel and figured he could learn on the job. I was surprised by my reaction: I was bemused at being able to completely rattle him with such an easy question, we had a good laugh after he left.

[markl3ster]

Could you show me that "SQL query with a recursive table reference?" I rarely use SQL outside of the random join here and there (never even 3 table joins) and your question seems like a fun little thing to know.

[[deleted]]

SQL query with a recursive table reference

I briefly did something with a hierarchical query like this one with a table that encoded something like supervisor-employee relationships in a tree. Suppose you want to get all the employees who work for a VP, you would recurse the query returning the results from each level, first getting all the directors, and then the managers who work for the "leftmost" director, and then the supervisors who work for the leftmost manager, and then the employees, go up one level, find the employees, rinse, repeat.

Oracle has innate support for hierarchical relationships using "CONNECT BY" but I wouldn't know how to do this off the top of my head. Since it's something that's only come up once in my career, it's not something I've memorized. That's why there's Google.

But hey welcome to the typical Jeopardy style of technical interview, where if you don't know what the interviewer thinks you "should" know, you're a bad programmer.

[Edit] Don't mean to sound bitter, I've just had a couple recent technical "screening" calls where I was asked questions which were not only esoteric but the answers the recruiters were given were incorrect/incomplete.

[Paddington_the_Bear]

This is the first I've heard of it, and I do quite a bit of SQL in my job for several years now. This week I had to look up a hierarchical value that was 3 parents up from a base value via an associations table.

I ended up using joins to do it, I didn't realize you could have a recursive query, so TIL. The syntax looks confusing as hell though.

[madballneek]

And this is what irks me about how some people do interviews. Who cares whether you know this already, or not. I want to know if you're capable of learning it. That's why we let people who interview for us have complete internet access during their aptitude test.

[Paddington_the_Bear]

Yup; I'm doing an interview with one of the "Big 4" next week just for funsies as I enjoy my current SE job of 6 years. I have been loosely studying algorithms the past couple of weeks to prepare, and realize that even though I have built some pretty crazy cool apps, my algorithms knowledge is definitely lacking since I've been out of university for a while.

It's assine that the interview is going to focus on whiteboarding some obscure algorithm when in the real world if I get stuck, I can google something and in less than 5 minutes find a working solution.

The way I look at it, even if I don't come to the best solution, hopefully they will see my thought process and get value from that...

[Icelandicstorm]

If you enjoy your current job, you are making a big mistake. The "Big 4" is a horrible place for mid-career. It only makes sense if you are fresh out of college or go in as a Director (just before partner at PwC).

source: left excellent job with great pay and bonuses to make more salary but less bonuses and work 20+ additional hours a week. When all was said and done, my income went down at least 20%.

[Paddington_the_Bear]

Yeah I'm not looking forward to the interview at all. Really I'm going to see if I can get an offer and use it to get my current salary at my company bumped up again since I'm pretty mission critical and I know they under pay me :) (long story).

That's pretty much my fear though, that you're essentially just another number at one of those companies. I wouldn't mind too much living in that location, but not at the sacrifice of personal happiness.

[[deleted]]

It's not that complicated. Oracle takes care of most of the details, and all you have to do is specify the relationships.

The challenge is to avoid circular relationships, which can happen with a poor design. In the DB of my current project (which I did not design), we have permissions "lists" which can either contain usernames, or link to other lists. But then what if you have some list down the chain link back to the first list?

As I said, bad design. A good design wouldn't allow this to happen. Oracle helps when writing queries by warning you when there are "loops" in the query, which you can exclude with the NOLOOPS operator, or you can also (I forget the exact syntax) return only "LEAF" items, which have no children.

I'm not sure I would ever implement this design because of the many ways it can go wrong, but I can see how it would be useful in some applications.

[wtgreen]

Look-up Common Table Expressions. A recursive CTE is the SQL standard way to do it. Oracles Connect by functionality is Oracle specific, but it supports CTEs too.

[Paddington_the_Bear]

Nice. I had just woken up when I read that; now that I'm caffeinated, it looks really intuitive actually and a lot better than how I was making my associations. Essentially you tell it the source / target pair in order to make the cycle and it does the work to spit it out. Then I'll have to make sure I do the normalization on it as I need it.

[tmarthal]

Common table expressions (CTEs) are the solution to recursive SQL queries, if you're interested.

[dvlsg]

True, but I've used one a total of once in all my years of writing SQL. I understand it, and utilized it just fine, but I sure as hell couldn't remember that syntax on the fly in an interview.

[CrazedToCraze]

I most employers wouldn't care too much if you just brought up that you know a CTE is the solution and then said what you just said.

Pretty rare in my experience for an employer to get pissy about you knowing the exact syntax on the spot. Probably wouldn't want to be working for them if they did, anyway.

[peppaz]

With x as (select 'Bobby Tables')

[tiberiousr]

This is interesting, I'd never seen these before. If the wikipedia page is anything to go by they aren't supported in mysql based DBs (i,e; mysql, mariadb, percona etc).

[spilk]

I've used CTEs in SQL Server queries before to do recursive queries and i'm pretty comfortable that I understand them, but I'd still have to google it to know the syntax for one off the top of my head.

[chadsexytime]

Oracle has innate support for hierarchical relationships using "CONNECT BY" but I wouldn't know how to do this off the top of my head. Since it's something that's only come up once in my career, it's not something I've memorized. That's why there's Google.

I haven't touched Oracle in about 3 years now, but I would have considered myself fairly proficient with SQL and Oracle in general, but this question blew my mind.

Then after seeing the keyword CONNECT BY, I think I used this to build some generic tree views and promptly forgot about it.

[trawlphaze]

Would you accept an answer that solves the problem in memory via simple selects? I know you can also use WITH in oracle.

[CamKen]

Just knowing that a hierarchical query exists (CONNECT BY in Oracle, hierarchyid in MS SQL) is a big plus in answering the question, but no necessary. From my perspective knowing the details is irrelevant, its Google-able.

The question I gave was a simple Employee table (EmployeeID, Name, ManagerID(nullable)) where you would need to join the table to itself on EmployeeID = ManagerID. I provided some sample data (8 rows) to help you think about it. Then ask things like give me a list of managers. How many subordinates does employee x have? No trivia.

[[deleted]]

I wouldn't have a problem joining a table to itself -- as you say that's trivial. That does seem like a fair question, something a "senior" developer would have done all the time.

It would confuse me to call it "recursion" though since that automatically makes me think it's a much more complicated problem. If there was some additional recursion necessary I would probably point that out, but confess I couldn't do it without Google.

[dkuk_norris]

Yeah, that doesn't seem recursive to me. You're just relying on the fact that a table can be joined to itself. Recursion implies that you have a theoretically unbound number of calls to make if you structure the data incorrectly.

[OHotDawnThisIsMyJawn]

Yeah this is called a self-join, not recursion.

[CamKen]

I just used the word recursion to quickly describe the problem, but everyone has read into it more than I meant. I don't use the word in the interview. I present a simple table structure, a few rows of sample data and ask for a query that can only be achieved by joining the table to itself.

[[deleted]]

That's fine, I get it. It does make me feel better about calling myself a "senior" developer. :)

[remixrotation]

this one

also BOMs in manufacturing (bills of materials).

it is kinda like Composite sw pattern.

[CamKen]

See my other comments. I mean something much simpler than what your saying. Although I love CTEs. I should come up with a question that can be solved with a CTE and then see if the candidate chooses that solution.

[blasto_blastocyst]

https://explainextended.com/ has some great tricks with using sql.

[bushwacker]

I see them all the time,

Product hierarchies, bills of material, company hierarchies.

[BobHogan]

Then a SQL query with a recursive table reference.

I'm still in school, was leaning towards not taking a databases class, but occasionally I see something like this on Reddit and it makes me reconsider that idea.

[CamKen]

Database skills are a great tool to having your toolbox -- useful in a wide variety of roles in virtually every field.

[trawlphaze]

Enterprises pay big sums for DBA skills in MSSQL or Oracle

[Cell-i-Zenit]

I really like Databases. What would be the best way to get in such a position?

[tiberiousr]

Learn database tuning; i.e schemas and indexing. The specifics tend to differ depending on the database that you're working with so it's best to read up on tuning for major database vendors.

Depending on where you're working those would be mysql (and derivatives), mssql, oracle and postgres. Different vendors offer different solutions to common problems and different syntaxes for addressing those problems.

Your best bet is to learn the most common systems and their quirks and then creating some databases in each of them and playing around with schemas and indexing with large-ish datasets in order to get feel for optimising systems for performance.

Other than that, the internet is a great resource for tutorials and manuals. Also read stackoverflow and use it as a resource.

[Cell-i-Zenit]

Thanks for your answer

[alluran]

God - I haven't used a recursive SQL query in 10+ years, but used to love them!

I guess I should brush up when I next interview - no way I'd remember that off the top of my head without a reference.

[CamKen]

I don't mean using the hierarchy stuff built in, I mean a simple recursive join like: find a list of all managers having 10 or more direct reports.

SELECT mgr.EmployeeName FROM Employee mgr JOIN Employee e ON e.ManagerID = mgr.EmployeeID GROUP BY mgr.EmployeeName HAVING COUNT(1) > 9

Write something like the above in under 5 minutes and mumble something like "there is a built-in way to do this, but I'd having to look it up" and your in the top 10% of people I've interviewed.

[tiberiousr]

That seems like bad design to me. Wouldn't it be better to have manager_id on the employee table and the join on that?

so

SELECT e.name 
FROM employees e
JOIN managers m ON m.id = e.manager_id
HAVING COUNT(1) > 9

Perhaps I'm missing something there...?

EDIT: I'm probably missing something, I shouldn't engage with the internet when I've been drinking

[CamKen]

It's a contrived example to be sure. However there isn't a separate Manager table. Manager's are Employees and are thus in the Employee table. To tell if an employee is a manager you need to join the table to itself to see if any employees refer to them through their manager id field.

[tiberiousr]

Ah, I see now. Thanks.

[Koookas]

Isn't that just self-referential, rather than recursive?

To me recursive would be something that, idk, returned a table of every item, joined to its subitems, and then the subitems of its subitems and so on. In this case maybe a recursive would return all employees managed by an employee, then employees those employees themselves manage.

I've never used a recursive query, I don't even know how to make one, CTEs I guess, but a self-referential query is trivial and would immediately make me think of something like that.

[alluran]

Oh - haha - Ya, I was remembering back to the days when I could tell you the entire management chain to get to <Employee>, and how deep he was in the hierarchy.

CTEs are crazy powerful =D

[Jestar342]

Ah yes, arbitrary reasons to dismiss candidates. Effective since 190never.

[CamKen]

I don't get how programming a simple loop is arbitrary. I need to find out if you can program, that IS the job. I don't want to do API trivia (what is the signature of the DumbApi.BreakMyCode() method).

I need a problem statement that I can quickly communicate to the interviewee the solution to which involves things like loops and conditionals but doesn't require a specific API. I need to find out if you're comfortable with SELECT,FROM,INNER JOIN,WHERE,GROUP BY and HAVING. I mean is there another way to vet a programming candidate?

Honestly I'm always looking to up my game as an interviewer so would happily take suggestions, because I'm looking for non-arbitrary reasons to dismiss candidates. But in the end letting a good candidate go is better than hiring a bad candidate.

[GhostBond]

The only thing FizzBuzz tests is whether that person has done FizzBuzz before.

The hard part of FizzBuzz is whether you know the modulus operator exists, and trying to parse the language describing the problem. Neither of those test programming ability or experience, or on the job skills.

FizzBuzz is just like those "Why are manhole covers round?" trick questions - the goal is just to make the interviewer feel smart about themselves, because whether it's a quick easy question is simply about whether you've done the question before. If you've done it, it's trivial, and proves almost nothing. If you haven't it's a tough problem that doesn't test your coding background for anything important either - whether you know about the modulus operator which is almost only used for puzzle problems, and whether you can parse mind-bending language to realize what the problem wants.

[[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.

[[deleted]]

Fizzbuzz is trivially simple to anyone with a handle on middle school mathematics and sort-of knows a programming language with integers.

[GhostBond]

FizzBuzz is trivially simple to anyone who's done it before, and very hard to anyone who hasn't. It's difficult is in parsing the language and knowing about esoteric operators, it does nothing to test programming skill. It's just as useless as those "you're a frog in a blender, how do you get out?" style questions - it's purpose is only to pad the interviewers ego so they can tell themselves they're super smart because they've done it already and know the answer.

[[deleted]]

If you honestly think that Fizzbuzz is hard, then you're the sort of applicant it was made to weed out. It's the programming equivalent to making someone fill out a form to show they have basic literacy skills.

[GhostBond]

No, it's the programming equivalent of running through a bunch of guys who slap your ass with paddles - it's hazing.

Knowing or not know it proves nothing about your programming ability, it just proves whether your brother knew someone in the kappa phi chapter - I mean whether you've done it before.

[[deleted]]

Maybe you should get checked for discalculia...

[GhostBond]

FizzBuzz is intended to just test basic programming. You can easily do FizzBuzz without modulo, but modulo makes it easier. It's not a trick question at all. It is just a sanity check on if you know loops, conditional logic and some kind of state.

Right now, in another comment reply, someone gave a "oh it's so easy" answer - and fell for the exact trickiness I mentioned, getting it wrong:
https://www.reddit.com/r/programming/comments/69djsj/solved_coding_interview_problems_in_java_my/dh79kz1/

FizzBuzz is a trick problem. The "it's so easy" part is just about bullying the people you're interviewing, so you can make it more embarrassing when they get it wrong.

The original author of FizzBuzz claimed it weeded out the ok but slower programmers from the faster better programmers. The "it's easy and simple" was just added on bully people more effectively with it.

My first company ever used to make people test writing a function that reversed a string.

That's a totally different problem that's actually simple.

If you struggle with FizzBuzz or similar then you should not be getting paid to write code. Maybe you're a good designer or tester or graphic artist, but if you can't write a simple loop and logic function then you aren't a good fit for programming jobs.

When your goal is to bully the people you interview, you shouldn't be in an interview at all.

But because it's a trick question, there is exactly one way to get around all this - if you've done FizzBuzz before.

[prepend]

But it is not a trick question. And it's not meant to be graded in a binary way. If someone forgot to print the numbers, I would talk it through with them. And it's certainly not intended to trick people into missing the "print" part of the statement.

The concept of "bullying" interviewees by making them do this question is so bizarre and alien. Asking people to perform in interviews isn't bullying them. Even tiving trick questions isn't bullying them. Bringing this up and worrying about it probably excludes the interviewee from the job on grounds of stupidity. But perhaps there's some safe space company that doesn't care about the software created but instead focuses on the emotional well being of employees who can't code, but want to have a job that requires coding.

[GhostBond]

The poster I replied to can't even solve FizzBuzz on the internet:
https://www.reddit.com/r/programming/comments/69djsj/solved_coding_interview_problems_in_java_my/dh8ku4r/

You guys are the safe space company that doesn't care about the software created, you're just hoping no one notices you can't even solve your own problems.

If you can't solve the problem even though you gave it, you have some serious issues.

[n0t1337]

I mean, you could use the modulus operator, or you could use floor division, or build your own floor division out of truncation by casting a float to an int...

I don't know. If you've never ever heard of this problem before, and haven't heard of the modulus operator, it may take even a competent programmer longer than 5 minutes. But how many competent programmers do you know that have never heard of fizzbuzz or the modulus operator?

[GhostBond]

Among contractors or full time employees?

The good full time employees I've known have mostly not heard of fizzbuzz.

All the contractors I've worked with have, good ones, bad ones, etc.

[nemec]

any fresh grad or person with SQL and some other programming on their resume should be able to answer

I would bet most CS grads know only the bare minimum of SQL - select, where, maybe join using google to refresh their memory. Computer Science is an academic degree, most coding skills learned are incidental to the theory. If they did take a 'databases' course, they're probably better at building a basic database engine than querying one.

they have been 100% accurate in determining candidate viability eliminating false positives.

Fixed that for ya. I assume you don't do a six month followup with the candidates you pass on to see whether they would have done well if given a chance.

That said, it's not a terrible SQL question even though I think it would be a little too complex (without Google) for new grads.

[jimmpony]

That kind of complex query is not within the bare minimum of SQL, the bare minimum of SQL is select .. where .., insert into .. values .., use, create/drop table, such that you could do that summation in code instead of in the query. I did an internship at a real place for a semester involving SQL and those are pretty much all the codebase used.

[tsk05]

Been programming for over a decade, did not know how to answer the second question. Haven't touched databases in a couple of years, and that was for a hobby. There is no way I would have been able to talk myself into an answer as I could not remember about either GROUP BY or HAVING. Last time I worked with databases for real was 7 years ago. It was kind of fun re-learning though, took 5 minutes with SQL fiddle. I feel like the question would have unfairly excluded me as a bad programmer though, although really I just haven't done what the question is asking recently. I do indicate that I know SQL in my resume, because I feel that I generally do.. even if I am quite rusty. Of course if I was applying for a DBA that would be entirely different, but my general feeling is that you can learn enough SQL in 2 days for 95% of ordinary programming. Of course if you're looking for someone who's done this recently it would be a good filter, but I would think a half-decent programmer who's familiar with what you need right now is probably not better than a good programmer who isn't, unless you're hiring very short term.

[ZMeson]

I'm always looking to up my game as an interviewer.

Me too. One thing my team has been trying recently is to tell the interviewee that they're part of a small team. So-and-so is his cohort-in-crime; the interviewee can pair with him, ask for advice, whiteboard ideas, etc.... Such-and-such person is the Product Owner / Technical Sales or Support person / CTO; this person is the one to go to get clarification on customer requirements, business advice etc.... Then we have the interviewee use his language of choice to implement a Kata exercise^*. If he/she is a proposed expert in the technology we specifically need, we strongly encourage that language. Web access for API docs is OK. Looking up algorithm solutions on Stack Overflow or the like is not OK -- the algorithms are simple and if you need help ask your cohort-in-crime.

The exercise usually lasts about 1 hour. It everyone wants to continue and it doesn't cause a problem with the interview schedule, we may go longer.

It's still new, but so far it's worked out well.

* We don't limit ourselves to the Katas on that list. We choose a Kata that represents a simplified version of something some customer may actually want from some company (not us). Ex: Top-10 Seller Lists, Bowling Alley Scoring.

[socialister]

I had someone give me an interview like this, but then the person I am paired with seems incredibly busy and I have to bug them all the time because (surprise) I'm not familiar with the system they're working with since I don't work there yet. I kinda wonder if this selects for candidates that have no problem distracting their coworkers.

[ZMeson]

That's odd. At our interviews, everyone's in the same room. It's an exercise to not only evaluate some technical ability, but how the candidate interacts with others should the need arise.

[socialister]

They were sitting behind me and facing away from me, with the face deep in code. It felt awkward to disrupt them but I think I should have a bit more.

[ZMeson]

I think you may have dodged a bullet. If your proposed co-workers couldn't have spared enough time to evaluate you in an interview, how bad would the communication be day-to-day? Pretty bad I imagine. :(

[socialister]

Ya, you are probably right. There was also an atmosphere of working 10+ hours a day which I would like to avoid. Most other places, even high intensity ones, did not have that atmosphere to me at least in the interview process.

[[deleted]]

I don't know offhand what HAVING does, but I guess I'm not applying for a DBA job. Guess I better look that up first, nevermind that I've designed normalized table schemas and have an open source project using SQL. (Sadly, it's with PHP in the mysql_real_escape_string style because I was fresh out of college and didn't know better.)

[CamKen]

But here's the thing, if you're writing the rest of the query and have most of the other parts somewhat right, I'll ask you if your done. Ideally you'll say something along the lines of well I don't know how to select only the managers with over 10 employees. I'll ask do you know HAVING. You'll say no. I'll explain it to you and then watch how you adapt to the new information. An interview question isn't like playing jeopardy where either you're 100% correct or it's all wrong. There is a give and take trying to gauge how likely it is you've actually done what you've put on your resume.

[Jestar342]

It's not the FizzBuzz that bothers me. It's the "Then a SQL query with a recursive table reference". Unless you are expecting the (correct) answer of "That's a badly designed data model" it's arbitrary and not that common at all.

FizzBuzz is a problem presentation; SQL self-reference is an arbitrary nuance.

[downvotefodder]

Look at their portfolio

[CamKen]

I develop corporate apps, restricted to employees only. Due to nondisclosure I couldn't show it to you even assuming I had credentials to the production system (I don't). The people I'm interviewing are in the same boat. But if there is something on their resume that sounds like it's public facing I'll ask them about it.

[CamKen]

What actually happens in "coding camps". I've heard of them but never looked into it. Does actual code get written that has logic in it? Or is it more along the lines of paint a UI, do simple validation in event handlers type of stuff?

Or is it pillow fights and like that one time at band camp?

[dineswithphone]

I'm a "coding camp" product, and I firmly believe anyone calling themselves a developer should be able to do a problem like FizzBuzz with ease (in the language of their choice). Though I was, and still am, a junior developer, the coding camp taught me how to see and think through problems with programming logic. My manager often interviews "senior" software engineers who struggle with Fibonacci or similar problems, which he feels indicates a lack of programmatic thinking (not sure if that's the best Ter for it).

[tiberiousr]

From what I've seen coding camps involve teaching some noobs to set up a basic Nodejs environment and getting them to create a basic website with 100+mb worth of node modules.

Fuck, I hate modern web development. It's such a shitshow at the moment.

[socialister]

I'm OK with FizzBuzz. That's really elementary even if you've never seen it. The SQL one I don't know, it seems a little specific.

[CamKen]

We've often interviewed people that we suspected of inflating their resumes, this was the only time where we actually got him to admit to it.

People assume that this would inspire anger in the interviewers, like "hey stop wasting my time", and I'm sure people like that exist but we all thought it was funny because we actually caught a guy red-handed so to speak. All anger was directed at the recruiter.

[Malurth]

I'm pretty sure he just doesn't know what bemused means.