The company I work for has prospective developers write something that parses Java property files, and sample files are given to them to examine. It is amazing how many are unable to write something to do this. Additional small-grained programmer behaviors are also discovered besides if they can code the answer: do they comment their code, do they structure it, name it in a thought out manner or use X,Y, and Z as variable and function names? Do they use exception handling? It is a pretty useful test and filters out people who have head knowledge but inability to do a simple task, or have impressive resumes that mean nothing.

Atlassian isn't hiring people solely on the strength of their screener. They just want to be able to more objectively screen out people who have no business applying. Most companies do this by reviewing resumes and getting rid of everyone who, say, doesn't have X years experience with Y language, or didn't have Z GPA in college.

You should give it a try, see what they send you! The stuff we did when I was still there was definitely more advanced. But again, pre-screening is never a test for competence, it is a test for lack of competence. The real test for great skill comes in the form of a 90m+ coding test and a 2h technical interview.

Tests taken remotely do not work to screen out the incompetent who routinely take them to the internet for solutions or pay someone else to solve. Nor do they screen in the competent who realize their day off work is much better spent making some phone calls or networking if they are really looking to switch jobs rather than spend it doing things like learning a new web framework to solve some canned problem.

And yes, he actually mentions in the article this is an actual thing he does: have applicants learn new frameworks in order to apply. Sheesh. Who has time for that except the very desperate.