Hacker News new | ask | show | jobs
by czbond 4014 days ago
Dude - we understand. We've been there, just maybe for other reasons. Are you applying for things too far above your pay grade, or too far below? Are you applying using technologies or a background that the companies you apply to aren't interested in? Or are you always making it to an interview and flubbing there? Can you see a pattern? Look for the stopping point - and optimize by focusing only on fixing that one point - forgetting everything else for now. Make it a game - make spreadsheets and test (as an engineer would).
1 comments

I don't know what my pay grade is, or how to feature the data I get. I do ask for feedback from interviewers; they usually don't response. When they do, I get conflicting answers.
Interviews have to be carefully constructed to avoid a bunch of bias. The interviews you go to probably aren't carefully constructed.

The interviewers just pick someone. They then post-rationalise and say things like "cultural fit". And then, when any other candidate asks the interviewers will post rationalise a reason those candidates didn't get the job. You get conflicting answers because they're all just making it up.

You frame not being sucessful as failure. Sure, it is. It might be useful to reframe things. Getting a job is an iterative process. You apply for jobs. If you don't get replies you tweak your resumé and cover letter until you get responses and requests to interview. You're getting interviews so that already some sucess! Now you just need to tweak your interview technique to get a job.

There are people who can help. There are probably recruiters that can help - although finding a non-scumbag recruiter may be difficult. Perhaps there is someone on HN who can help?