[154639] in North American Network Operators' Group
Re: job screening question
daemon@ATHENA.MIT.EDU (jim deleskie)
Fri Jul 6 18:27:52 2012
In-Reply-To: <25808.1341613518@turing-police.cc.vt.edu>
Date: Fri, 6 Jul 2012 19:27:16 -0300
From: jim deleskie <deleskie@gmail.com>
To: valdis.kletnieks@vt.edu
Cc: goemon@anime.net, nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Pascal's wager.. almost :)
On Fri, Jul 6, 2012 at 7:25 PM, <valdis.kletnieks@vt.edu> wrote:
> On Fri, 06 Jul 2012 15:07:51 -0700, goemon@anime.net said:
>
>> This is what baffles me. People keep putting stuff on their resume that
>> they simply don't know anything about. TCP/IP expert, yet they don't know
>> SYN/SYNACK/ACK or subnetting. HTTP expert but they don't know what a 200
>> response is.
>
> The Friday afternoon cynic in me says it's because it's a move with positive
> paybacks. There's 3 basic possibilities:
>
> 1) You send the puffed resume to a company with clue, it gets recognized
> as puffed, and you don't get the job. Zero loss, you weren't going to get
> that job anyhow.
>
> 2) You send a boring unpuffed resume to a company sans clue. They recognize it
> as boring because there's only 3 buzzwords on 2 pages, and you don't get the
> job. Loss.
>
> 3) You send a puffed resume, and the guy doing the hiring doesn't know what
> the 3-packet mating call of the Internet is *either*. Win.
>
