Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

bulldoze

macrumors regular
Original poster
Mar 15, 2011
229
51
So I applied for a Test engineer job last week and the company insisted I do a online Codility programming test. I have just completed this and feel fairly sure I submitted reasonably good solutions for 2 of the 3 tests but I ran out of time on the third one and had to submit a solution that did not work.

Now this is the first time I have ever heard of these tests and it was a bit of a shock to have to do one as although I do a bit of basic scripting I don't really touch any programming in day to day work.

A few questions for next time:

I did all three tests in Python, would it have been advisable to do each test in a different language to show flexibility?

I did not write or submit any test cases for the code that I wrote. I simply tested the code in another IDE with variable prints and then copy and pasted the solution into the Codility web interface - would I be marked down for this? the Codility FAQ seemed to suggest that this was fine but as the test time line is recorded I am not so sure.

Once submitted I did not receive any feedback on my code - is this usual?

Thanks.
 
I did all three tests in Python, would it have been advisable to do each test in a different language to show flexibility?

It really depends on the job you are going for and what they asked for - if the only language they are interested in is Python then its probably fine. If the job ad said something about other languages being required then maybe it would be different. As some languages lend themselves to certain problems and with the time constraints inherent in the system, I, personally, would expect someone to use a high level language more often than not.

I did not write or submit any test cases for the code that I wrote. I simply tested the code in another IDE with variable prints and then copy and pasted the solution into the Codility web interface - would I be marked down for this? the Codility FAQ seemed to suggest that this was fine but as the test time line is recorded I am not so sure.

Again it depends on the job and what the interviewers are looking for. Presumably you get to speak to them as well as having done the test, either by attaching notes or in person and I expect they will ask you how you found the test. That will give you an opportunity to explain your methodology. I would be suspicious of someone who didn't test but unless specified that you should attach test cases in Codility I don't think there is any problem in having done them separately.

Once submitted I did not receive any feedback on my code - is this usual?

Yes, I don't think Codility give you any - you need to wait for your interviewers.

HTH,

Andrew
 
  • Like
Reactions: Garsun and bulldoze
When I was interviewed for my current job, I just said: I don't do tests. You wanted me, sign the dotted line, if not, stop wasting my time.
 
That's your right and privilege. As a person who regularly recruits technical people, I would decline your offer.
 
That's your right and privilege. As a person who regularly recruits technical people, I would decline your offer.

There is a big difference between an potential employee applying for a job, and a recruiter contacting a candidate for a job offer. For the first case, I guess testing is in its place, but not in the second. If the recruiter needs to test a candidate, then my claim is that there has not been adequate research. Most recruiters are just sending emails to StackOverflow users, as well as contributors on GitHub, without actually analyzing the contributions or the answers. It looks like they are casting a pretty narrow meshed net in a wide arch, and then sifting out the talent by testing them. Thats just lazy, disrespectful and a waste of time for all the involved parties.
 
There is a big difference between an potential employee applying for a job, and a recruiter contacting a candidate for a job offer. For the first case, I guess testing is in its place, but not in the second.
Fair enough, but the OP said they applied for a job, not that they were head-hunted.
 
Mostly from watching my partner do endless tests while looking for work I have an objection to these kinds of tests. They usually take an undue amount of time from the candidate and are required too early in the process. The tests often seem irrelevant to the job in question as well.

In my career I think I have only done such a test once. Perhaps not entirely coincidently the company that required it were so disorganised that by the time they offered me the job I had already taken another. Every other job has relied purely on interviews, technical or otherwise.

If you are using tests to screen candidates you are pushing the costs onto the unpaid party of the transaction and maybe you should look at improving your interview technique so the costs are born by those being paid.

That said my current employer has a custom programming task. I argue against its administration and I don't think its been that great at determining how good an employee ends up being - just how much free time they have (i.e. how many hours they currently work, how old their children are, are they (temporarily or otherwise) a single parent etc).
 
  • Like
Reactions: spiffers
We do tests as a companion to the face-to-face interview, so you are already at the second and final stage if we ask you to take one.
 
Just to clarify:

My situation was a bit odd as I had already sat a face-face interview with the test manager and a head of department. The week after was when I was asked to do the online coding test. At no point during the face to face interview was I asked about coding skills.

My guess is that as my CV states that I had a working knowledge of Python and Java they exercised due diligence and set out to find if I was being truthful. There was a follow up telephone interview with the test manager and the software development head but again no mention of the coding test and I forgot to bring it up.

I was offered the role and should start in the next couple of weeks.
 
I heard that even with correct program, one could get only 50% unless the code is highly optimized. Even professional programmers could fail the test. Is this really true? I have been asked to take a 3-hour codility test that is not really related to the job I applied for. Seems to be a waste of my time.
 
Last edited:
I heard that even with correct program, one could get only 50% unless the code is highly optimized. Even professional programmers could fail the test. Is this really true? I have been asked to take a 3-hour codility test that is not really related to the job I applied for. Seems to be a waste of my time.
i hate test.. it nothing related with job scope anyway. programming is flexible. and time consuming.. Unless you don't have proper plan and money.. Don't waste other people time...

A lot i see wannabe like facebook and argue thinking it was cheap cost.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.