Live data from Hacker News

I was asked to crack a program in a job interview

erenyagdiran.github.io

241–250 of 309 posts

Re: I was asked to crack a program in a job interview

#241
Dude?? Did you wait until you go to Spain to post this? Still, it is very fun to read this post and comments here. Actually, I prepared these two crackmes in order to arrange a small competition among universities at Turkey. But, they became very good interview questions also.

It's really good to read these responses. Cracking ability is really rare in CS student community in Turkey. Our intention was increase awareness. Reading these comments showed me it was a really good step.

Re: I was asked to crack a program in a job interview

#242
post #207

Earlier quoted context omitted.

> Real-life tests are THE best thing to send job candidates I agree, but only if you're allowed to use references/google/etc and given a reasonable amount of time to accomplish it. I've had a "real-life" test where I wasn't allowed to verify or look up information, or where I'm giving a very short time to execute, and I've always thought those were absurd. The idea that you would ever have to do something like this i…

For any person who claims to have years of Unix experience, they can easily do anything they want using man pages. Though I agree with you on the general premise though. One must be allowed to look up information they need to solve a problem. >>I've had a "real-life" test where I wasn't allowed to verify or look up information, or where I'm giving a very short time to execute, and I've always thought those were absur…

Do you still work at a major IT services firm ?

Re: I was asked to crack a program in a job interview

#243

Earlier quoted context omitted.

Technical support.

This. We may laugh, but starting in technical support gives you an idea of how your users are using your product, if your documentation is accurate and helpful, what the pain points for people not in the department you are destined for are, and gives you an idea of how the product works. It also quickly weeds out the people who can't effectively communicate before they get to the programming team.

We've been rotating the sysadmins through customer service. Not taking calls (our CS calls tend to be long and detailed, and a n00b isn't going to help), but being there for the CS people. It's been marvellously instructive. It also cheers the CS people that someone cares. Now we need to get the devs doing the same.

Re: I was asked to crack a program in a job interview

#244

Earlier quoted context omitted.

> In this case, Spanish The OP is Turkish. Ankara is the capital of Turkey. His name is Turkish. Punctuation is the same as in English.

Sorry, I saw the "Barcelona,Spain" on his about page and incorrectly assumed that is where he was originally from.

Barcelona, Spain would have implied Catalan, not Spanish.

Re: I was asked to crack a program in a job interview

#245

This reminds of this quora post. A nice one for beginners like me. The guy reverse engineered Sublime Text to remove the nagware of registration. https://ericjang.quora.com/Reverse-Engineering-Apps-a-Step-b... PS- You should buy ST, it is one of the best code editors out there in the market.

Thanks for this. A good read for those who have never used such tools.

Re: I was asked to crack a program in a job interview

#247
post #229

Earlier quoted context omitted.

>If this is a user-facing tech-support position, then it is a hard job requirement that the candidate be able to handle being lied to by the user. Yes, I agree. Are we supposed to also assume that our bosses and interviewers lie to us, too? At no point does he say that he is emulating a user that needs support help.

Well if not lying, you should always entertain the possibility they are mistaken. The best confirm and reaffirm constantly. You know what they say about assumptions.

You are going to think your boss is mistaken/wrong/lying in the first hour you meet her/him, during a job interview? Nah. You're not.

Re: I was asked to crack a program in a job interview

#248
post #131
post #9

> Here is the first thing i typed in the terminal root@lisa:~# ./CrackTheDoor Um. I see at least one security issue already.

Give it costs pennies to boot up new Linux instances, I wouldn't assume this was OP's own machine.

Given that he later shows screenshots of "eren@lisa:~$ gdb ./CrackTheDoor" that assumption is pretty shaky.

Re: I was asked to crack a program in a job interview

#249

Real-life tests are THE best thing to send job candidates. It scales well (you don't have to spend personal hours on them) and you get real information. This applies even to sysadmins. We have a favourite: set up a VM with a slightly-broken application in a slightly-broken Apache and Tomcat, and get them to ssh in and document the process of fixing it. Even people who aren't a full bottle on Tomcat will give useful i…

> Real-life tests are THE best thing to send job candidates I agree, but only if you're allowed to use references/google/etc and given a reasonable amount of time to accomplish it. I've had a "real-life" test where I wasn't allowed to verify or look up information, or where I'm giving a very short time to execute, and I've always thought those were absurd. The idea that you would ever have to do something like this i…

It's gets a bit complicated when your job candidates may find your test interesting enough that they post a complete walk-through of the solution online.

The candidate was kind enough to avoid posting the name of the company (to hopefully hide the walk-through from Google queries for "crack me hiring test company name", but an HN discussion might then arise around the walk-through, in which the company would be named, and well, there goes your test.

It's hard to accurately run "take home" tests when hiring because of just this.

Re: I was asked to crack a program in a job interview

#250

Real-life tests are THE best thing to send job candidates. It scales well (you don't have to spend personal hours on them) and you get real information. This applies even to sysadmins. We have a favourite: set up a VM with a slightly-broken application in a slightly-broken Apache and Tomcat, and get them to ssh in and document the process of fixing it. Even people who aren't a full bottle on Tomcat will give useful i…

I remember a website providing failing VMs for this purpose. I'm not even sure it wasn't just a suggestion .. but if someone knows such a site, feel free to leave the url.
Post reply on HN