• ben (unregistered) in reply to Lord Parity, Last Count of Register

    The chair of a high-school English department? Wow.

  • . (unregistered)

    "...if you’ve reviewed a whole crap ton of resumes..."

    I was under the impression that the SI unit was a "metric fuckton".

  • (cs) in reply to .

    He was using US Customary units, that's why it looks that way.

  • Minos (unregistered) in reply to Jay Levitt
    Jay Levitt:
    I want to know what a feather is.

    It's the suggested replacement his spell checker gave for "featcher". Say it out loud.

  • Jay (unregistered)

    My favorite Pennsylvania place name is Mars, zip code 16046. I have no idea if there are any IT jobs there, but I think it would be way cool to be able to say, "I am from Mars" and be telling the absolute truth.

  • no one (unregistered)

    In addition I have several courses to take now!

    All your base are belong to us!

  • Jay (unregistered)

    On the serious side: Every source of advice on interviewing I've ever seen says that you should research the company you're applying to. In the days before the Internet, I used to go to the library and search through directories and newspapers and I'd literally spend hours. And then when I went to the interview, in the first 5 minutes the interviewer would tell me everything I'd learned from my research. These days with the Internet it's easier. But still, I don't think doing such research has ever done me one iota of good. I've never had an interviewer ask me anything that required a knowledge of their company.

    Does anybody have any contrary experience? Any time that an interviewer actually quizzed you on what you knew about their company and rejected you because you didn't know, what?, the locations of all 129 branch offices and the part numbers of their best selling products? I suppose if you were applying for a computer job at a big computer company, like Oracle or IBM, and you had no idea what they did, that would say something about your computer knowledge. But if you don't know what Podunk Products makes? Who cares?

    My honest answer to "why didn't you apply to [company x]" would be "Because you had a want ad or job listing for a position that I am qualified for and they didn't, and while I suppose I could send applications to every company in the world in the hopes that they have a suitable opening, that seems like rather a waste of time." Are there a lot of people out there who really send out job applications to companies that they think might be a nice place to work without regard to advertised openings? Maybe that's a good way to find a job. I suppose there wouldn't be as much competition. Can't say I've ever tried it.

  • Bob (unregistered)

    The +4 part of the ZIP code probably should have been blacked out. From that part of of the ZIP code you can determine that the address is for a house on the odd-numbered side of the 300 section Park Avenue in Milton, PA. Fortunately, that doesn't narrow it down to a specific house.

    http://tinyurl.com/2ckvzw

  • (cs) in reply to Minos
    Minos:
    Jay Levitt:
    I want to know what a feather is.

    It's the suggested replacement his spell checker gave for "featcher". Say it out loud.

    Roffle-mayo! I love it!

  • Mackenzie (unregistered) in reply to whicker
    whicker:
    what is the wtf about the first one? So he has an atypical living situation, maybe his wife divorced him and took everything? Maybe he does have a house, and thinks the RV is going the "extra mile"?

    "I would like to work with a Company". What if instead he intended that to mean, "I would like a full time position".

    Reading the work history, the person did some interesting stuff and certainly had (at the time) some good related experience.

    However, he really sucks at Word formatting, but I don't entirely blame him.

    Or was the humor more like the "Live in a van down by the river" comedy sketch by Chris Farley?

    He has the writing abilities of a first grader. Every sentence is formatted almost exactly the same. They all either start with "I" followed by a verb and a noun or "It was" followed by an adjective or verb. It reminds me of a little kid reading "Tom is a boy. Spot is a dog. Spot is Tom's dog. Spot can run. Tom can run. Spot and Tom run." He capitalizes random words, and some of his sentences aren't even sentences. How about this gem? "I developed a package for them. It included an add/delete feather. An edit feather and a Monthy/Quarterly report." The last "sentence" has no predicate. That should have all been one sentence that sounds like maybe an 8th grader wrote it, "I developed an application which allowed records to be added or deleted and could generate monthly and quarterly reports."

    Based on his grasp of English, I'm thinking he'd write code that looks like this:

    int a = 0; a = 1; int b = 0; b = 2; int c = 0; c = a; c = c + b; c = c + 5;

    instead of...oh i don't know...

    int a,b,c; a=1; b=2; c=a+b+5;

  • (cs) in reply to yet another Matt
    yet another Matt:
    Please tell me King of Prussia is a real place, somewhere. I want to work there too.

    Yes it is, I used to live there. Not much there but a huge mall that was formed when two smaller malls grew into one another and merged.

  • (cs) in reply to Jay
    Jay:
    Does anybody have any contrary experience? Any time that an interviewer actually quizzed you on what you knew about their company and rejected you because you didn't know, what?, the locations of all 129 branch offices and the part numbers of their best selling products?

    Twice now I've had phone interviews where the recruiter sent me the wrong company name. In both cases it was due to a minor misspelling, and I was still offered the real jobs.

    The reality is that it really doesn't matter if the company makes airplane engines or pop tarts. The problems they need solved are basically the same. Also, because of a highly mobile workforce companies are used to having to at least somewhat sell themselves during the interview process.

  • Jimmy (unregistered) in reply to GalacticCowboy
    GalacticCowboy:
    Or the one that never gets old... :D You have to go through Intercourse to get to Paradise.

    Not necessarily, if you're coming from Bird in Hand, Unicorn, or Peach Bottom.

    If you're coming from Blue Ball or Pine Swamp, then maybe.

  • whicker (unregistered) in reply to Jay
    Jay:
    ...But still, I don't think doing such research has ever done me one iota of good. I've never had an interviewer ask me anything that required a knowledge of their company.

    Does anybody have any contrary experience? Any time that an interviewer actually quizzed you on what you knew about their company and rejected you because you didn't know, what?...

    Knowing what the company does or what skills and knowledge the position actually requires, so you can stress how you're the "right fit", is the point of doing research.

    One time I sat locked in a small room in a day-long interview, where the highlight was a two-hour lecture from the head project manager explaining the nuances of the relationships of the different internal departments and such with a grid on a big whiteboard. My stomach was growling fiercely because I had skipped breakfast because of a snowstorm.

    At the end of the day, I couldn't even remember what what I would be doing or what the initials were of the internal department I was to be working for. Something with P's and Q's. I know I messed up the thank-you letter by spelling it wrong. Hmph. Some candidate. Spent two hours explaining it and he can't even spell my department properly!

  • Robert Robbins (unregistered)

    Wow, this programmer was looking for work in my area. Living in a RV is not so unusual. I think my boss lives in a trailer home. He is well qualified for a job in my town. Seriously, you should outsource to PA. My rates are now lower than the typical hourly rate in India.

  • Franz Kafka (unregistered) in reply to FredSaw
    FredSaw:
    java.lang.Chris;:
    The thing that amazes me whenever we're recruiting is the amount of lies people put on their resume (or CV to a Brit). Time and time again I've had candidates come in, only to find out they have never used some of the programming languages, operating systems or other technology such relational databases that are mentioned on their CV. I'm not even talking about stuff that's irrelevant to the job they're applying for, or even listed as a I nice to have, this is the key skills the job demands them to have!
    Sometimes this isn't the candidate's fault. They talk to a headhunter and answer a series of questions and the headhunter draws up their resume based on that talk. The headhunter, of course, is simply looking to get the candidate hired so they can collect their fee. So they pad the resume. If you once created a web page with FrontPage, you're an expert in HTML. If you once converted a ColdFusion app to C#, you're a CF wizard.

    I once interviewed a guy whose resume said he had an Associate Degree from Sam Houston State University. Knowing better, I said, "Hmm... I didn't realize SHSU had a two year degree program," and he turned red and stammered an explanation that he had attended some classes there for a couple of semesters, and that the headhunter must have put that on the resume.

    This is why you bring a copy of your resume. No reason to ever let a headhunter write your resume.

  • Michael (unregistered)

    ...I looked over the .PDF resume, and noticed that on page 3, he lists one of the languages he worked with is Bobcad.

    ...is there such a thing, and is it just one of those custom-built language types that never hit the mainstream? Bobcad sounds like a WTF all on its own...but I'm no expert in Bobs or WTFs. My dad's name is Bob though.

  • Russ (unregistered) in reply to snoofle
    snoofle:
    Paul:
    I can't think what I'd have said if someone asked me for an example of 'out of the box' thinking.

    It's not something you deliberately remember (at least, I wouldn't), and in hindsight it might not seem to be 'out of the box'.

    In any case, thinking 'out of the box' isn't always a good idea for a developer - if it's too far out of the box it can be hard to maintain... "Good" thinking out of the box would probably be totally forgettable because the result is so elegant and 'obvious' (in hindsight).

    I suppose a good example of thinking "out of the box" would be the first person who came up with something like quick sort or radix sort instead of bubble sort (which is the most obvious sorting technique). If so, then if that's the sort of 'optimisation' the interviewee did, it would seem to be good to me.

    (See http://www.acm.org/ubiquity/interviews/v4i30_hargadon.html )

    re: an example of out-of-the-box thinking. The post from yesterday (re lock and timer verses win-98 pc's and tanning beds), or something analogous would be a great answer.

    Personally, my out-of-the-box story happened a couple of years ago. The company had a login policy of something-you-have and something-you-know (site-certificate and password). The rule was that the cert's couldn't be distributed by e-mail (yeah, I know, but whatever). Thus, they needed to be distributed in person to each Pc at each company site every 3 months. Since we have customers globally, it got really expensive really fast. The users who were paying for all of this wanted a cheaper alternative. The engineering group proposed something for 6 million dollars and 6-12 calendar months of effort. I laughed, took 2 hours to code up a couple of cold fusion pages with short-lived challenge-response passwords to limit access. Total cost: $1500 for the CF license and the (old) PC was free as it was collecting dust in a closet. The security folks approved it and a day later it was deployed.

    Yet another example of ColdFusion turning a $6 million dollar project into a $6000 project.

  • (cs)

    I suppose this ironic, coming from somebody who is repeatedly accused of being a "grammar nazi." (Whatever that is. I suspect I'm more of a "grammar peronista," if you want to get technical.)

    However, I see very little wrong with this resume at all.

    Granted, it's very sad, and it betrays an overarching reach beyond possibility of attainment.

    I have, however, been forced to manage a fifteen person team (it was scheduled to be four, but apparently corporate management have yet to learn of Brooke's Law) at the height of the .com bubble. Needless to say, there was variance.

    One of the important life lessons that this taught me is that anybody with the desire to work in a technical job has the possibility of qualifying for one. Not, obviously, the guy who froze like a rabbit in the headlights when I asked him to debug something. (I put him in QA. He's now a Business Analyst.) Not, obviously, the recent immigrant from India who had that irritating cultural habit of standing behind you and noisily swallowing his own phlegm. (I put him on writing contrived test cases for the vendor, even though I knew that there was nothing wrong with the vendor's software. Hell, we're paying for support. Eventually I recommended him for a support job, at which he's apparently a star.) Not, obviously, the 60 year old "programmer" who just got in the way. God solved that one for me with incurable brain cancer. Thank God for God.

    <obama>My point is that we here, all of us, my brethren, tend to find this stuff funny. It isn't, really. There's nothing funny about living in an RV; it might well be a plus point in a resume. There's nothing funny about listing every single podunk town in eastern Pennsylvania; that's a rational decision. (BTW, I love Pennsylvania.) And there's certainly nothing funny about the resume in general.</obama>

    Whatcha want? It's reasonably literate, by programmer standards. The man sets out his stall (and yes, I know he's asking for a rather peculiar progression). He's prepared to move (to a trailer park near you) just to get a job -- presumably any job. And, best of all, there are no (obvious) lies at all.

    No Paula.

    No quack.

    Me, I'd call the poor sod in for two reasons. One, he might be qualified for a job in QA or customer support (low bars, I'll agree), and two, if I fail him, I might be able to point him towards a better career.

    Charity, people, charity. (I would say caritas, but I suspect that Alex has nicked that for a captcha.)

  • (cs) in reply to Paulo
    Paulo:
    Work from an RV parked outside the company? That raises telecommuting to a whole new level.
    Gonzo? Is that you?
  • (cs) in reply to whicker
    whicker:
    Jay:
    ...But still, I don't think doing such research has ever done me one iota of good. I've never had an interviewer ask me anything that required a knowledge of their company.

    Does anybody have any contrary experience? Any time that an interviewer actually quizzed you on what you knew about their company and rejected you because you didn't know, what?...

    Knowing what the company does or what skills and knowledge the position actually requires, so you can stress how you're the "right fit", is the point of doing research.

    One time I sat locked in a small room in a day-long interview, where the highlight was a two-hour lecture from the head project manager explaining the nuances of the relationships of the different internal departments and such with a grid on a big whiteboard. My stomach was growling fiercely because I had skipped breakfast because of a snowstorm.

    At the end of the day, I couldn't even remember what what I would be doing or what the initials were of the internal department I was to be working for. Something with P's and Q's. I know I messed up the thank-you letter by spelling it wrong. Hmph. Some candidate. Spent two hours explaining it and he can't even spell my department properly!

    Generally there's no amount of research that can actually tell you what the internal structure of the company is like, or what particular job you'll end up in (except maybe for a very very small company). For big companies? Research is going to yield "We're an excellent competitor in the Enterprise Widgets business. We have clients in lots of countries, and are committed to diversity!"

    Sadly, the interviewers are hoping you'll recite exactly that. Haven't yet found out if they're douchebags, or if they're just checking to make sure you actually took time to visit their web page.

  • Vsm (unregistered) in reply to Jay
    Jay:
    On the serious side: Every source of advice on interviewing I've ever seen says that you should research the company you're applying to. In the days before the Internet, I used to go to the library and search through directories and newspapers and I'd literally spend hours. And then when I went to the interview, in the first 5 minutes the interviewer would tell me everything I'd learned from my research. These days with the Internet it's easier. But still, I don't think doing such research has ever done me one iota of good. I've never had an interviewer ask me anything that required a knowledge of their company.

    Does anybody have any contrary experience? Any time that an interviewer actually quizzed you on what you knew about their company and rejected you because you didn't know, what?, the locations of all 129 branch offices and the part numbers of their best selling products? I suppose if you were applying for a computer job at a big computer company, like Oracle or IBM, and you had no idea what they did, that would say something about your computer knowledge. But if you don't know what Podunk Products makes? Who cares?

    Researching the company probably wouldn't help you say something good in the interview, but I could see it saving you from accidentally putting your foot in your mouth...

  • El_oscuro (unregistered) in reply to Lars Vargas

    You just need a Wireless access point, a VPN, and you are in business. I have a small data center in my RV.

  • El_oscuro (unregistered) in reply to whicker
    whicker:
    Jay:
    ...But still, I don't think doing such research has ever done me one iota of good. I've never had an interviewer ask me anything that required a knowledge of their company.

    Does anybody have any contrary experience? Any time that an interviewer actually quizzed you on what you knew about their company and rejected you because you didn't know, what?...

    Knowing what the company does or what skills and knowledge the position actually requires, so you can stress how you're the "right fit", is the point of doing research.

    One time I sat locked in a small room in a day-long interview, where the highlight was a two-hour lecture from the head project manager explaining the nuances of the relationships of the different internal departments and such with a grid on a big whiteboard. My stomach was growling fiercely because I had skipped breakfast because of a snowstorm.

    At the end of the day, I couldn't even remember what what I would be doing or what the initials were of the internal department I was to be working for. Something with P's and Q's. I know I messed up the thank-you letter by spelling it wrong. Hmph. Some candidate. Spent two hours explaining it and he can't even spell my department properly!

    I once interviewed with a company, in which they readily agreed to an interview after hours (starting at 5:30pm I think). I should have been suspicious immediately. Anyway, by 9:30pm I was ready to say:

    "I really don't care if I get this job. Can I just go home now?"

    I did actually take the job, but got a rude awakening when on the 2nd day, another consultant called me into a meeting which lasted 4 hours. If it is possible to be literally bored to death, it would be here. I quit the job after about six months, just before I died of boredom.

  • (cs) in reply to Paul
    Paul:
    I can't think what I'd have said if someone asked me for an example of 'out of the box' thinking.
    First, the guy put "thinks outside the box" on his own resume... it might have occurred to him that someone would ask for some examples, and he should have memorized and practiced a couple of stories at least.

    Second, the reason why he should do this: because too many stupid interviewers are looking to hire excellent interviewees, rather than excellent developers, sysadmins, or whatever they advertised for. These interviewers should remember that they are trying to determine how valuable this person could be to the company. And unless you're hiring a saleman, their interview skills aren't likely to be all that relevant once they're hired.

  • (cs) in reply to sas
    sas:
    First, the guy put "thinks outside the box" on his own resume... it might have occurred to him that someone would ask for some examples, and he should have memorized and practiced a couple of stories at least.

    Wouldn't a memorized example be worse than nothing, in the context of an out-of-the-box thinker? Unless by "out of the box", he means he has a handful of solutions prepackaged in boxes, and he takes them out when he needs them...

  • Eric (unregistered) in reply to Neal

    I once took a phone screen for a job located in a nearby state. After the phone screen, I eagerly awaited the next step.... which appeared in my mailbox within the week: A job offer with moving package.

    Any company that would hire an employee sight-unseen and pay to move them hundreds of miles smells of desperation or just plain foolishness.

    I figure if they are so quick to hire, they may be just as quick to layoff (or burn you out?), etc...

  • Lester Burnham (unregistered)

    Incidentally, nine-digit ZIP codes can really narrow down a location. That specific ZIP code seems to correspond to Breon's Welding & Repair on 309 Park Ave, Milton, (570) 742-8149. Might want to black that out next time. Or not :)

  • mtu (unregistered) in reply to Neal
    Neal:
    Naturally, failing to grab this opportunity that was dropped into my lap is something I still regret to this day.
    And here I was, thinking you'd declined at least partly for the fact they were engineering weapons.

    Captcha: Latin for "who"

  • Chris (unregistered) in reply to Charlie

    Re: O RLY?

  • George Nacht (unregistered)

    Thinking out of the box....labelled ,,Sanity"?

  • Bosshog (unregistered) in reply to Tim

    This is the same for the large town of Reading in England. We also have a village called Penn Street in (wait for it) Buckinghamshire, which is where the Penn family came from before they upsized to Pennsylvania!

    We also have such gems as the hamlet of Jerusalem (Cumbria), Queen Camel (Somerset), Nomansland (Devon), Boston (Lincolnshire), and Westward Ho! (Devon, and yes, it does have the exclamation mark :).

    What fun - I wish I had a village to name!

  • (cs) in reply to gabba
    gabba:
    Why is he limited to Pennsylvania if he can just park his RV anywhere and work?

    High gas prices? :)

  • PC Paul (unregistered) in reply to Stupidumb
    Stupidumb:
    duckyd:
    If you can't think outside the box, build a bigger box!

    Now that's thinking outside the box.

    Surely that just makes it more difficult?

    Build a smaller box, then it'll be easier to think outside of it.

    Now that's thinking around the box. Or something.

  • (cs) in reply to real_aardvark
    real_aardvark:
    ...It's reasonably literate, by programmer standards...

    If that's true, then it's not this resume that's sad—it's the rest of the programming world.

  • (cs) in reply to Michael
    Michael:
    ...I looked over the .PDF resume, and noticed that on page 3, he lists one of the languages he worked with is Bobcad.

    ...is there such a thing, and is it just one of those custom-built language types that never hit the mainstream? Bobcad sounds like a WTF all on its own...but I'm no expert in Bobs or WTFs. My dad's name is Bob though.

    http://en.wikipedia.org/wiki/Computer-aided_manufacturing Look in the section entitled "Software providers today"

  • (cs) in reply to gabba

    That's as far as his RV will go with a half tank left of gas and coasting down hills. Didn't you read his letter?

    HE'LL WALK UP TO 20 MILES TO GO TO WORK. JERKS.

  • applebus (unregistered)

    If you can't even give one example of when you "thought outside of the box" then why would you put it on your resume?

    If you make a claim on your resume, ANY CLAIM, you should be able to give an example or back it up somehow.

  • (cs) in reply to Jay
    Does anybody have any contrary experience? Any time that an interviewer actually quizzed you on what you knew about their company and rejected you because you didn't know, what?, the locations of all 129 branch offices and the part numbers of their best selling products?

    Not exactly, but I did have an interview once where the interviewer asked what I knew about the company, which I actually knew rather well, having had two friends who worked there previously. After explaining what I knew of the company he told me that I was wrong, that what I had explained wasn't really what they did at all... and then proceeded to explain back to me exactly what I'd just told him but in a different way.

    Me: You make Widgets(tm). Him: No, that's not it at all. Me: ... Him: We manufacture a device that performs widget-like activity and is licensed to XYZ Corp as a "Widget".

    (Grossly anonymized)

  • (cs) in reply to GalacticCowboy
    GalacticCowboy:

    Not exactly, but I did have an interview once where the interviewer asked what I knew about the company, which I actually knew rather well, having had two friends who worked there previously. After explaining what I knew of the company he told me that I was wrong, that what I had explained wasn't really what they did at all... and then proceeded to explain back to me exactly what I'd just told him but in a different way.

    Me: You make Widgets(tm). Him: No, that's not it at all. Me: ... Him: We manufacture a device that performs widget-like activity and is licensed to XYZ Corp as a "Widget".

    (Grossly anonymized)

    Reminds me of one time I went to Jiffy Lube, and the guy came out to the car with his may-I-help-you bit.

    "I'd like an oil change."

    "Sorry, we don't do oil changes here." He paused after this, waiting for me to say something stupid, apparently. I didn't bite, and just looked at him. "Nope, we do a Signature Service(TM)!"

  • (cs) in reply to Smash
    Smash:
    AC:
    Ok, so the Sybase/Oracle database thing was really dumb.

    But what would have been a good answer to the Google/Microsoft/etc. question?

    Raja: "Why do you want to work for Sybase, and not at, say Google, Yahoo, Microsoft, or Oracle?"

    Candidate: "I actually applied for them too, but I can't just sit while I wait for their call. In fact, just supposing they might not have an opening right now is more than enough reason to keep spreading my resume to other companies."

    There you have it, this answer shows you're proactive and considers possibilities (which means you're used to plan ahead). On the plus side, if your resume is decent enough, they will think their competitors may take an interest on you and they may lose the opportunity to hire you if they take too long to make an offer.

    That sort of implies that as soon as the phone rings from Google or Microsoft you're out the door.

  • (cs) in reply to GalacticCowboy
    GalacticCowboy:
    Does anybody have any contrary experience? Any time that an interviewer actually quizzed you on what you knew about their company and rejected you because you didn't know, what?, the locations of all 129 branch offices and the part numbers of their best selling products?

    Not exactly, but I did have an interview once where the interviewer asked what I knew about the company, which I actually knew rather well, having had two friends who worked there previously. After explaining what I knew of the company he told me that I was wrong, that what I had explained wasn't really what they did at all... and then proceeded to explain back to me exactly what I'd just told him but in a different way.

    Me: You make Widgets(tm). Him: No, that's not it at all. Me: ... Him: We manufacture a device that performs widget-like activity and is licensed to XYZ Corp as a "Widget".

    (Grossly anonymized)

    I interviewed once for a new grad position in a very large consulting firm. Nevermind the fact that I was late and showed up for the interview, which was held in the Career Services building at my university, huffing and puffing and breathless (the interviewer actually paused and said "why don't you take a few minutes to cactch your breath"). I thought I'd show at least a token knowledge of the company, so the night before I did as much reading as I could about their various business divisions and alignments.

    When he asked if I had any questions I said something like "Yes, I realize how large and diverse your company is, so I just wanted to try and understand the 'big picture' -- my impression of your company is ..." and I drew out a nice matrix of business divisions, product lines, etc. on a piece of paper. I gave it to him, and asked "Does that seem about right?"

    He seemed impressed but something wasn't quite right, he was coughing nervously and said "That's a pretty good first guess" or something. Apparently I touched a nerve because I drew two business units as roughly equal in stature when in fact they were not, evidently very much not, and in some kind of deep rivalry with each other.

  • BinaryPhalanx (unregistered) in reply to Smash

    I often put add/delete feathers in my applications. Unfortunately, I never "discored" Visual Basic Guide To The Windows32 API, so I've never been able to figure out how to put any edit feathers in.

  • Henry Miller (unregistered)

    Many executives seem to have this idea that because they came up with a good idea and made it big, nearly everyone else is just as enthused about their buisness. Therefore why should they hire anyone who doesn't care exactly which widget the company makes.

    The rest of us know that an envelope and a gear are very different physically, but are just as willing to help build either one. I don't dream about envelopes at night, but if an envelope maker needs a programmer for something I'm willing to help them make the best envelopes. If they decide not to hire me, I'll just get a job with someone who makes rubber stamps and needs a programmer.

    Of course you never say this at the interview. You always research the company so you can give a creditable impression that you really want to work for them, but are willing to work for someone else if they don't hire you.

    The other reason to research a company is to see if there is a dark underside.

  • (cs) in reply to shadowman
    shadowman:
    "Sorry, we don't do oil changes here." He paused after this, waiting for me to say something stupid, apparently. I didn't bite, and just looked at him. "Nope, we do a Signature Service(TM)!"
    Sounds like something he was required to say. Like "You want fries with that?"
  • wingcommander (unregistered) in reply to Fizz

    There are some VERY strange names in PA, King of Prussia is almost normal.

    Try

    Blueball

    and my favorite

    Leather Corner Post

  • Bob (unregistered) in reply to Lester Burnham
    That specific ZIP code seems to correspond to Breon's Welding & Repair on 309 Park Ave, Milton
    Actually, it's any of the odd-numbered houses on the 300 section of the street.
  • (cs) in reply to Stupidumb
    Stupidumb:
    I would like to leave a comment. I am an expert at writing comments. I have a desk and would like to write comments from my desk.
    I have a wooden table. I would like to write comments from my wooden table. I would like to photograph comments on my wooden table and upload them heah.
  • Hognoxious (unregistered) in reply to FredSaw
    FredSaw:
    Anonymous:
    Is there any other type of a .NET developer than the "fresh out of school" one?
    Yes.
    It's true, most of them never even went.

    Don't forget to tip your waitress!

  • Adriaan (unregistered) in reply to gabba

    I'd say he's from Transylvania rather than Pennsylvania...

Leave a comment on “Never Quite Made the Interview”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article