Qfyilyi

I have applied for a Junior Product Manager position at a mobile gaming company (in Germany). After a standard phone screening, I was sent a test by email to complete in order to go further with the process.

The tasks consists in creating a roadmap for one of their mobile games with "at least 3 new features and a bunch of improvements to the current features in the game". It also asks to make estimations for the features/suggestions, and create a diagram to split up the work over the different teams. All suggestions should be well explained and motivated.
There is no set deadline, guidelines on the time to spend on the test or on the length of the deliverable.

Now, I have nothing against interview tests. I am actually very in favour of them, and try to stay away from companies that hire fast without really checking a candidate's abilities. I came from a developer background, so I have often been asked to do coding tests for interviews.

However, this test took me by surprise because:

• The scope seems huge. Even cutting it short, I don't see how it would take me less than a week to do this properly.




• It is real work for the company. I can't even be sure the company isn't doing this just to get lots of ideas out of people. Why not have the same test but regarding a competitor's game, or an hypothetical one?

I'd like to hear other opinions regarding this. Is this kind of test common practice? Is it reasonable? Are they trying to exploit me with free work? And if not, how do I approach the company? Should I suck it up and do the test, just drop this and not go further with the process (I'm actually pretty interested in working for them), or try to communicate my doubts to them? How?

Thank you!

Unfortunately, companies using "interviews" as free work is not something new, it's been going on for over a decade that I know of.

It's not just small shops that pull it either. A friend of mine was being "interviewed" by one of the big financial companies, and they kept trying to get details from him on a previous project. He kept on pushing back until he finally said

Hire me, and I'll tell you everything you want to know.

Then they had the nerve to report back to the recruiter that he was rude.

IF something doesn't feel right, don't do it. This might not be a scam, but if it doesn't pass the smell test, then it wouldn't be a company you'd want to work with anyway.

If you estimate the work would take a week to properly do, and suspect they're looking for free labor, then you basically have one of three choices.

1. Do the work, but make it lack value. This shows you can do the work, but doesn't further the goals of the company. For example, you could take a different game, one that has nearly no value, and show how you'd add three features to it. (I'm thinking tic-tac-toe, or something so saturated it's not a money maker anymore, like Tetris) The risks are they might not accept the work as a proper response to what they requested, and such feedback (while expensive to you) is pretty indicative of their intent.




2. Describe the work that would be done, instead of performing it, indicating how long each phase of the work you would have performed would have taken, detailing the resulting products, with mock (incorrect) output. The positives of this is that it clearly demonstrates you know the "process to plan and manage" such items. Again, this is a lot of work, and the cost / benefit might not be there for you.




3. Describe the estimated effort of the work, and suggest that they send something that can be accomplished in under some-number-you-can-bear hours. Indicate that if you attempted to perform the work in the number of hours you'd be willing to do for free, the work would be sloppy, rushed, or incomplete, and that wouldn't reflect your skills or ability in a professional manner.




4. Just move on, and don't give the work a second thought.

It is all a matter of how much you are willing to put into the hiring process. I fully agree, this request seems to weigh far too heavily on your time, and after it is performed, there is no guarantee any job is waiting. That said, every hiring process demands some effort, and it is a very personal choice how much effort a person will tolerate, especially if the job seems to be better than most.

Yes, I agree, they're probably looking for free labor; but, you can still present yourself as capable without contributing to their success for free. It's just not clear whether it makes sense for you.

Now there are some details missing, but to me this doesn't seem like necessarily a huge task. And less a question of how well you can plan down to all the details but more on how you manage tasks with limited time.
I'd invest just as much as you'd be normally willing to invest in an interview task and along with the result give them the time spent.

The result could be very coarse, but I'd think that is okay. They might not be interested in the details but might want to see that you know how a development cycle roughly looks, what components it has (development, testing, bugfixing etc), how you can maximise the value generated, e.g. by having departments work in different stages of each feature in parallel (developers can write the next feature while the first is tested, etc.). And the "real" interview might be asking questions based on your plan and how to get from the rough concept to all the nasty details.

Seeing it at that level, I'd also consider it so generic that it wouldn't be working for free.

If you do this and that's not enough for them, then fair enough, you only invested what you would be investing for a task you considered "reasonable". If you get the job, well invested time.

Some companies usually send big tests to filter candidates who will not be willing to do the task just because it's big and will take more time than usually it does.

This way the company will have less candidates to evaluate, and each candidate will have some degree of perseverance, and it'll show the candidate is really interested in the position.

But, the test can't have business value. It can't look like free work. It must be a task designed to the only purpose of test the candidate skills. Nothing more. Also, it must respect the candidate's free time.

A 6-to-12 hour task is ok. Candidate can take about 2 or 3 days to do it on his/her free time.