Live data from Hacker News

Next dream job can be in an HTTP header

frenxi.com

121–130 of 178 posts

Re: Next dream job can be in an HTTP header

#121
post #96

Earlier quoted context omitted.

>I was so disappointed, once I got it running I was hoping to hear helicopters or a knock on the door! They probably need a lot of people with some tech knowledge. This way they can probably gain the widest audience that is still useful. If it's too hard to crack, it's unlikely your investment of time in this recruitment measure will actually yield results.

The point is that if you crack it, they should send you to some unique link. Even if it's not super hard, it at least proved some level of technical competency and do should allow you to prioritised interview access (maybe at least skipping initial screening).

I assume the solutions to these can be found publicly pretty quickly. So your secret bypass first filter loses utility after the first couple of people.

Re: Next dream job can be in an HTTP header

#122
post #48

Just telling people to apply to domain.com/jobs is pretty lame. So, basically the same door that anyone else goes through when they click the "Careers" link in your site's footer? Reminds me of when I solved one of the CTF challenges for a website only for my reward to be "We're hiring! Apply at jobs.example.com!" Real "be sure to drink your Ovaltine" moment.

A perfect "be sure to drink your Ovaltine" moment! If anyone is unfamiliar, it refers to the movie "A Christmas Story". The moment here: https://www.youtube.com/watch?v=zdA__2tKoIU I first saw that movie a only a couple years ago and quickly realized how many pop culture references come from it. It does such a good job of capturing a period of time in North America. Even before I saw the movie, eating out at a Chines…

Growing up in the 90's my family would make it a point to watch this every year around the holidays, good times. If you are ever in Cleveland, OH, you can actually tour the house they filmed most of it in.

Re: Next dream job can be in an HTTP header

#123

Earlier quoted context omitted.

The point is that if you crack it, they should send you to some unique link. Even if it's not super hard, it at least proved some level of technical competency and do should allow you to prioritised interview access (maybe at least skipping initial screening).

I assume the solutions to these can be found publicly pretty quickly. So your secret bypass first filter loses utility after the first couple of people.

The person that knows how to Google for solutions may be the right person for the job.

Re: Next dream job can be in an HTTP header

#124
post #96

Earlier quoted context omitted.

>I was so disappointed, once I got it running I was hoping to hear helicopters or a knock on the door! They probably need a lot of people with some tech knowledge. This way they can probably gain the widest audience that is still useful. If it's too hard to crack, it's unlikely your investment of time in this recruitment measure will actually yield results.

The point is that if you crack it, they should send you to some unique link. Even if it's not super hard, it at least proved some level of technical competency and do should allow you to prioritised interview access (maybe at least skipping initial screening).

It works in reverse - you probably wouldn't want to work in such an environment with frustrating practices towards developers.

Re: Next dream job can be in an HTTP header

#125
post #106

So no one has heard of RFC6648 ? https://tools.ietf.org/html/rfc6648

> "…in practice the benefits [of the "X-" convention] have been outweighed by the costs associated with the leakage of unstandardized parameters into the standards space."

Honestly, prefixing silly, fun or extra headers with X- like in this scenario seems pretty harmless.

Re: Next dream job can be in an HTTP header

#127

Earlier quoted context omitted.

The point is that if you crack it, they should send you to some unique link. Even if it's not super hard, it at least proved some level of technical competency and do should allow you to prioritised interview access (maybe at least skipping initial screening).

I assume the solutions to these can be found publicly pretty quickly. So your secret bypass first filter loses utility after the first couple of people.

The reason you put this riddles online is to get to know people who love this kind of challenge. This is still the case if the solutions are available online, even though I would include a plead into my job ad not to post solutions online for fairness with respect to other potential applicants who mananged to solve the riddle.

When in a job interview, it should be very easy to find out whether the person found the solution online or he "cheated"; simple ask some detailed questions how the person came up with this and that part of the approach.

Re: Next dream job can be in an HTTP header

#128

Earlier quoted context omitted.

The point is that if you crack it, they should send you to some unique link. Even if it's not super hard, it at least proved some level of technical competency and do should allow you to prioritised interview access (maybe at least skipping initial screening).

I assume the solutions to these can be found publicly pretty quickly. So your secret bypass first filter loses utility after the first couple of people.

Perhaps filtering out the people who can neither solve it nor Google it is enough of a filter by itself. Not suggesting it should bypass more than initial screening, naturally.

Re: Next dream job can be in an HTTP header

#129
post #76

Earlier quoted context omitted.

Inside the community, a hacker (as opposed to "cracker" or "security hacker") is someone who uses technology in a creative way.

so what do we call undesirables like anonymous and so on?

"crackers" or "security hackers". I'm sure most people on this site would consider themselves to be some form of "hacker", after all, this is "Hacker News".

Re: Next dream job can be in an HTTP header

#130
post #38

For a while we had a recruiting message in the reddit headers. We also had this for many years: x-Bender: Bite my shiny metal ass We also had this for a long time: Server: '; DROP TABLE servertypes; -- Sadly, it looks like it was removed when they switched from haproxy to varnish. They did put this in though: x-moose: majestic So that's something I guess.

Maybe custom response header would be the ideal place to insert output from something like Emacs spook: http://www.cypherspace.org/adam/shirt/spook.html

Well, now I'm on a bunch of lists. Thanks for that link.
Post reply on HN