Live data from Hacker News

Why the Job Search Sucks

thewebb.blog

111–120 of 128 posts

Re: Why the Job Search Sucks

#111
post #43

A candidate we passed on reached out and asked for more specific feedback about why we passed. I happened to have some time over the holidays and agreed to provide him with some additional information personally and to meet up for coffee. > It's not you: The first thing I told him was that 80% of whether you get hired at a company is nothing you can do anything about. It depends on the company, your skills, their nee…

I once had an interview where I was told they did a bit of functional programming, but experience with FP wasn't a requirement. They flew me out and interviewed me. A few days later, they rejected me. I asked them if they had any feedback for me and, surprisingly, they answered! They said I was rejected because I didn't have enough FP experience.

This is just to illustrate that "It's not you" may sound trite, but it's true.

Re: Why the Job Search Sucks

#112

> At least I know not to waste my time waiting on you. So don't. If they don't meet your communication expectations, then it isn't a good match anyway. So don't wait. Move along. > These tests and whiteboarding are not indicative of your skill level No, they indicate your ability to work and talk through problems. I'm not sure where this idea that whiteboarding is about skill level came from. You can cram/study algor…

> I'd save these rants for AFTER you get a job.

I write my rants on physical paper. Then I burn it. You feel better and you don't accidentally make yourself unemployable. Well, as long as you don't accidentally burn down your house.

Re: Why the Job Search Sucks

#113

The level of pure bullshit that is part of the hiring process these days is mind-boggling. An recent example: I interviewed for company X, where I spent an entire day with more than a dozen engineers, answering the same types of questions over and over again: "Here's our platform, how would you fix it". At every turn, I would speak about X,Y,Z issues that would need to be solved and how this or that technology might…

Now THAT is some straight up bullshit.

For the downvoters, I was talking about how fucked up the company was for tricking bitcrusher into doing consulting for free.

Re: Why the Job Search Sucks

#114
post #38

I've been unemployed for ~4 months now (by choice) and it's been the best time of my life. Yeah, I'm burning through my savings, but I can focus on projects that make me happy, I can focus on honing skills I actually care about, and I don't have to partake in endless meetings that serve no purpose whatsoever. What I realized as I entered my 30s is that some people are okay with that. Some people are okay with endless…

Upvote x 1000.

Re: Why the Job Search Sucks

#115

The reference point for gaining employment is that dude who wrote Homebrew and got rejected by Google for being unable to "invert a binary tree on a whiteboard" [1] Unfortunately with this and many other articles I've read on HN over the years, the common theme is that decent/good programmers are not making it past HR. Everyone that wants to work in tech should instead navigate through the meetup/social space and bui…

[deleted]

Re: Why the Job Search Sucks

#116

Earlier quoted context omitted.

> I have zero experience in writing applications with it but I do know of it. I investigate it every now and then to see what's going on with it. Even I started writing a React app the day I became unemployed, I still wouldn't have the years of experience a lot of these companies are asking for. Don't get hung up on what job listings say verbatim/literally. Most people are reasonably flexible about it, they just have…

Yeah I've gotten about dismissive comments about tone, which is understandable. In interviews I've had, I get questioned about frameworks so I figured stating my experience upfront would be one less question. I haven't thought about it possibly being perceived as dismissive before.

tbh I'd be reluctant to hire somebody who's head's going to explode if they have to deal with some JSX, it's been mainstream for long enough now that if somebody has no clue about it, they've got their head in the sand. It's not about the experience so much as what can come across as a dismissive/know-it-all attitude.

Re: Why the Job Search Sucks

#117

Filling out 7000 fields on taleo is comical. It's why I use the hated recruiters now. I get to skip the BS of applying online. (At the employer's expense too!) I miss the old days, you submitted your resume, then they called you for an interview. You interviewed and either got hired or didn't (they'd typically call and say if you didn't). Why we need 80 layers of BS between the job seekers and employers is beyond me.…

> hated recruiters

My impression is "recruiters" has become a sink term for anyone one is facing during the recruitment process (various recruiters, agencies, POs, PMs, HR, CTOs, teasing puzzle smartasses, whatnot). In fact my personal experience with HR departments is rather good, and my attitude towards real recruiters is neutral at worst.

Re: Why the Job Search Sucks

#118

Filling out 7000 fields on taleo is comical. It's why I use the hated recruiters now. I get to skip the BS of applying online. (At the employer's expense too!) I miss the old days, you submitted your resume, then they called you for an interview. You interviewed and either got hired or didn't (they'd typically call and say if you didn't). Why we need 80 layers of BS between the job seekers and employers is beyond me.…

Why the "hated" recruiters. Only once in the past 20 years have I even thought about getting a job without a recruiter. I applied for 17 jobs through recruiters in my last job search and I knew the technology stack and the salary they were willing to pay before ever starting the process. Out of the 17, only one wasn't interested in starting the process, I got three offers within a month and none of the other 12 rejec…

I concur.

1) Every time I talk with a recruiter, salary is the first thing brought up. It saves so much time to go through an interview process only to find out they're going to pay you 30% below market value.

2) A recruiter brings you an job position that you did not know about in the first place usually. There are thousands of companies in an area, and not all of them post to the job boards you're looking at.

3) Using the recruiter means the company is motivated to filling that position. They need someone now and the usual means of getting people in to interview in that company is broken.

4) Developing a relationship with a recruiter is valuable, because they know what's hot, and what companies are willing to pay.

Re: Why the Job Search Sucks

#119

The level of pure bullshit that is part of the hiring process these days is mind-boggling. An recent example: I interviewed for company X, where I spent an entire day with more than a dozen engineers, answering the same types of questions over and over again: "Here's our platform, how would you fix it". At every turn, I would speak about X,Y,Z issues that would need to be solved and how this or that technology might…

Encountered such situation couple of times. Pokerface interviewers asking in-depth questions (e.g. domain knowledge, not necessarily data structures or algorithm smartassery), with minimal feedback. Learning basically. Quite cynical because it's good to talk basically, exchange knowledge and experience - I've always taken it as a common sense. Once I detect pokerface jokers I answer "no clue" for the simplest questions.

Re: Why the Job Search Sucks

#120

Earlier quoted context omitted.

Totally different type of pressure. You're assuming timeline pressure and social pressure is the same thing. It is not. If I'm applying for a senior developer/architect position, I should be able to think of a high level solution on the spot. When I was looking for a job a year or so ago, I thought I was interviewing for a regular developer position. I didn't realize I was interviewing for a lead position and they we…

>The first thing my now manager asked me was what steps I would take in the next 3-6 months to create the department. Thinking and describing it is a lot easier than coding it on a whiteboard. I explain ideas to problems all day. I don't code it on a piece of paper and hand it to the board. If it's an important problem, I actually take some time to roll it over, as should anyone solving any important problem. White b…

Hear hear!
Post reply on HN