Live data from Hacker News

Why the Job Search Sucks

thewebb.blog

81–90 of 128 posts

Re: Why the Job Search Sucks

#81
post #18

One thing about feedback: Too much feedback helps candidates game the system. This ultimately leads to bad hires, who end up getting fired. It hurts the process overall. When interviewing with a good interviewer, he (or she) knows that whiteboard sessions / tests / projects are just hypothetical situations. If I throw an unfamiliar API in front of you, and you ask certain wrong questions, I know you're not going to w…

> Regarding whiteboarding, if the candidate argues with me about why we're using a particular API, I pretty much reject the candidate. (No, we can't use the new threading API, I want to see how you can learn this API. No, we can't use an ORM, I want to make sure that you understand how to use a database.) YUCK. One of the first things I will do when presented with a technical scenario is start questioning the problem…

I've been forced to implement atoi and itoa functions in interviews, and albeit I agree with you that it's silly, I think they are just looking for a positive attitude.

I try to hype myself up with a "thank you sir may I have another" once I get through solving what I think is a silly question.

I remember being asked to solve a linked list problem with callbacks in JS where a service returned a Node and the API call to the next node in a list.

I had to just build a function to traverse the async list - I'd have wanted to just redesign that API, but instead I had to solve their silly problem.

I got the job, and it was all due to forcing myself to have a positive attitude and being happy to solve the problems vs questioning why one would ask it.

Re: Why the Job Search Sucks

#82
post #44
post #36

Earlier quoted context omitted.

I am actually wondering how many readers of the blog post rolled their eyes here. I am not saying that React is the best thing ever; there may be different arguments against using it, but man, this "CSS in JS" (or, alternatively, "HTML in JS") argument is not even funny anymore. I would have discarded this as a meaningless complaint coming from a hardcore backend developer who is repeating the principles of single re…

As a mostly back end developer, snazzy front end templates are either cheap or free.

Could you please provide some pointers to those? Thx.

Re: Why the Job Search Sucks

#83
post #64
post #54

Earlier quoted context omitted.

I seriously doubt that.

Thank you for the vote of confidence, but I'm a decent developer, not a $300k salary developer.

I mean, if you were paid market rates for interviews, you'd have to do a lot of interviews to net $300K.

I don't see how that is possible, ignoring the fact that doing that would be about as fun as gold farming on WoW circa 2007.

Re: Why the Job Search Sucks

#84

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.…

I've met some competent HR folks out there - I promise they exist.

I've only been around for like 15+ years though but been running in consulting circles for over 10. I'll admit that there are a fair number of crappy ones.

I generally avoid recruiters too - just against working with them on principle.

I wish there were an easy middle-person to use to find high quality project work. I think the tried and true referral system is all that has worked for me the entire time.

I've never applied cold to something and done it, and been happy about it.

Re: Why the Job Search Sucks

#85

Earlier quoted context omitted.

> Regarding whiteboarding, if the candidate argues with me about why we're using a particular API, I pretty much reject the candidate. (No, we can't use the new threading API, I want to see how you can learn this API. No, we can't use an ORM, I want to make sure that you understand how to use a database.) YUCK. One of the first things I will do when presented with a technical scenario is start questioning the problem…

I've been forced to implement atoi and itoa functions in interviews, and albeit I agree with you that it's silly, I think they are just looking for a positive attitude. I try to hype myself up with a "thank you sir may I have another" once I get through solving what I think is a silly question. I remember being asked to solve a linked list problem with callbacks in JS where a service returned a Node and the API call…

That...sounds absolutely dreadful. I'm happy for you but that doesn't sound like my cup of tea.

Re: Why the Job Search Sucks

#86
post #44

Earlier quoted context omitted.

As a mostly back end developer, snazzy front end templates are either cheap or free.

Could you please provide some pointers to those? Thx.

Google "free html5 templates" or replace html5 with your preferred framework. Here's one.

https://themewagon.com/theme_tag/free/

Re: Why the Job Search Sucks

#87
When looking through job postings I watch out for this type of statement: “Only short-listed candidates will be contacted.” which means that I can’t expect any reply if I am not selected for an interview. Dear recruiters, this is not OK, ever!

I put a day or two into a job application. (Which may be excessive, but it leads to a high conversion rate). Preparation includes researching the company, their products and projects, their history and my possible contribution – and tailoring my application package to their needs. If the company can’t be bothered to write me a short email “Nope, sorry. HR.” then that company is not worth my time.

In effect, “Only short-listed candidates will be contacted” tells me: “1) We are too lazy or incompetent to set up a mass email reply. 2) We don’t care about candidates enough to save them the time and stress of unnecessary follow-ups.” By extension, I will assume that company does not care about its employees either and has effectively disqualified itself from my becoming a part of their team.

Re: Why the Job Search Sucks

#88
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…

See? This! This would make the job search process a lil' less opaque.

One reason I've been given for not providing feedback is that it could open the company to lawsuits.

Re: Why the Job Search Sucks

#89
> Coding/design tests

Left tech years ago, but assumed that many/some of those tests and sample projects were employer attempts to procure free labor w/o any of the burdens (liability) of internships and employment.

> Rounds of interviews

Perhaps its helpful to look at the whole process from a different vantage point. Saw an article on CNBC a few days ago about the importance of, essentially, seeming desperate and wholly committed to whatever position it is one is applying/interviewing for. Seem too smart... too ambitious... have options for doing something else if this doesn't work out... etc? Don't expect to get hired. I can actually attest to that.

Anyway, the implication is that if you are still available and willing to go through rounds of interviews, you probably aren't 'all that desirable' in the first place. Yes, there is some irony there. But I know this having spoken w/ a # of HR people.

> Feedback:

-- Dear Paul, Hahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahahaha NO.--

Yeah, that would be, at a minimum, courteous, but... Workers are for the most part, commodities. As such, feedback isn't merited. Could say more here, but won't.

> How to deal

Obviously, each person's situation is different, but my experience tells me the best solution is to position oneself for independence (as much as is possible in a society). While in my last job, I pretty much decided that I'd focus on (hopefully) not needing another job. And while I didn't get everything right, I think that mindset and planning was instrumental in me pretty much being able to walk away from a job market that is pretty stacked against the typical applicant.

I know tech is supposedly immune to such stacking, but... Last year I listened to an applicant's conversation with a recruiter. The applicant was getting robbed, so much so that a guy, who I think was/is homeless, told the applicant as much. I mean are people really going through all this work to get paid $25/hr... in California???

Yikes!

Re: Why the Job Search Sucks

#90
post #74
post #66

Earlier quoted context omitted.

The interview process would certainly change as a result, so who knows if one could interview full time sustainably. But I don't think it's a special case. Good software developers are by nature great at hacking systems and plenty of them would find it more profitable to keep interviewing rather than work a regular job. If it does need a regulatory nudge, paying people to interview is the most naive way to do this.

“They say we offer naive answers to complex problems.” Just paraphrasing something from my sons leadership project ;)

Google tells me you're misquoting Hucci lyrics.
Post reply on HN