RedGreenCode

If you want to get good at something, practice that thing. It sounds like you're asking how to get good at coding interviews. So practice coding interview questions, not logic problems or competitive programming. LeetCode is probably the best known coding interview practice platform right now, and it has hundreds of free problems. In the LeetCode discussions, you can find people reporting on their interview experience, and companies often ask identical problems to the ones on the site. It's exactly optimized for what it says it's for.

You could get better at logical problem solving by practicing on Khan Academy or Brilliant or Art of Problem Solving. If that's what you want, then do those things. But it's not an efficient way to get better at interview questions.

> the group that's unwilling to put up with this is unqualified

Companies that get a lot of applicants care more about false positives than false negatives. So they're fine not hiring a lot of qualified people, as long as there's a low chance of accidentally hiring an unqualified person. Apparently LeetCode-style problems work for that type of screening.

That has been done as well: https://codeforces.com/blog/entry/94353

This looks like a duplicate of https://news.ycombinator.com/item?id=21892189. I answered there.

Here's a curated list of resources that a lot of people refer to: https://github.com/lnishan/awesome-competitive-programming

But really, the way to get started is just to pick a site and start solving problems. If you're specifically interested in GCJ then it's best to practice using previous problems from that contest. But I wouldn't recommend getting too caught up in one contest. If you start with the Easy and Medium problems on HackerRank or LeetCode, there are tutorials, discussions, and editorials to help when you get stuck. And those sites are easy to use, so you can get a lot of practice time in with low friction. That will get you past the beginner stage.

Most people who are doing competitive programming aren't good at the harder problems. For example, there are >2500 people listed on the TopCoder Top Ranked Algorithm Competitors page (https://community.topcoder.com/tc?module=AlgoRank), but only the top 115 or so are Red, and only about 415 more are Yellow.

A programming contest, even if you just do the easy problems, can be a more enjoyable way to practice for interviews than reading a book or even going through online puzzles like those on LeetCode.

Solving programming puzzles (or competitive programming) is a good basis for a deliberate practice plan. There are a lot of sites that provide puzzles of increasing difficulty. So you can work on problems slightly above your current level, which is one of the tenets of DP.

I wrote a blog post on this topic with more details on a specific process: http://www.redgreencode.com/deliberate-practice-for-software...

Khan Academy is a reasonable way to start learning programming, but like other learning sites (Codecademy and others) they focus on learning things the first time, and not as much on getting better. CodingBat (http://codingbat.com/) takes a more drill-oriented approach, which is more effective for learning the basics well. But there's not a lot of content there, in comparison with a puzzle site like SPOJ (http://www.spoj.com/).

Gayle Laakmann McDowell has a good Quora answer on the pros and cons of tech inteviews:

http://www.quora.com/Why-are-programmers-in-the-software-eng...

It's worth reading the whole thing, but here's a summary of why alternative interview techniques have their own problems:

* Testing for specific technology knowledge excludes good programmers who don’t happen to know that technology.

* Asking someone to explain their past projects is biased towards people who can explain effectively, not necessarily people who can do the work.

* Giving candidates a homework problem has several drawbacks: they may have someone else do the work for them; it is biased towards candidates with more free time; and because it requires negligible time for a company to send off a canned assignment, but potentially a lot of time for the candidate to complete it, it can be unfair to candidates.

* Having candidates work on a real project for one day makes it difficult to focus on characteristics that distinguish great programmers from good or mediocre ones, since real projects have a lot of simple tasks that almost any programmer can handle.

* Letting candidates use a computer during the interview can cause them to focus on syntax rather than problem-solving.

Basically, although many people hate the coding interview, there's no good alternative.

You need a certain amount of programming puzzle skill to get past the interview process at most tech companies. Competitive programming is a good way to practice this skill, but you don't have to do it at the exclusion of other types of programming. You may want to take a break from side projects for a few weeks or months while you work on your coding interview/competitive programming skills. After a certain point, there are diminishing returns unless you get interested in the competitive programming world and want to keep competing.

If you want more information on this topic, it is often discussed on Quora. Here are a few relevant posts:

* Why tech interviews are the way they are: http://www.quora.com/What-do-you-think-about-the-current-tec...

* Preparing for a coding interview: http://www.quora.com/How-do-I-prepare-for-a-software-enginee...

* Possible reasons for getting rejected after an interview: http://www.quora.com/What-are-possible-reasons-for-getting-r...