Ask HN: Replacement for Stack Overflow jobs section?
41–50 of 98 posts
Re: Ask HN: Replacement for Stack Overflow jobs section?
#42Applying on places like angellist/SO jobs etc gave me little in the way of success.
Re: Ask HN: Replacement for Stack Overflow jobs section?
#43Somebody please make OkCupid for Jobs. Both employers and applicants fill out questions that the community curates (so they can be job-specific, industry-specific, etc). Both employers and employees get matches via algorithm rather than receiving 100 random resumes or 100 random job suggestions that have nothing to do with you. Existing sites do this, but very poorly, because they only try to detect information out o…
Re: Ask HN: Replacement for Stack Overflow jobs section?
#44Somebody please make OkCupid for Jobs. Both employers and applicants fill out questions that the community curates (so they can be job-specific, industry-specific, etc). Both employers and employees get matches via algorithm rather than receiving 100 random resumes or 100 random job suggestions that have nothing to do with you. Existing sites do this, but very poorly, because they only try to detect information out o…
https://www.recurse.com/manual (citation using this exact term)
Re: Ask HN: Replacement for Stack Overflow jobs section?
#45Somebody please make OkCupid for Jobs. Both employers and applicants fill out questions that the community curates (so they can be job-specific, industry-specific, etc). Both employers and employees get matches via algorithm rather than receiving 100 random resumes or 100 random job suggestions that have nothing to do with you. Existing sites do this, but very poorly, because they only try to detect information out o…
I'd also like to see cover letters replaced by something more useful for both parties, like a small set of direct questions to answer.
When an applicant applies for a job, she's left to make her best guess as to what information the company might find useful, and has to find a way to cram that into an awkward, stiff, rather bullshitty epistolary format. The hirer is then left to try to parse and interpret that to arrive at some guesswork notion of whether the applicant might be a fit.
If the hiring company were to instead come up with a list of guided questions, they'd communicate and request up front what information they need to determine whether a candidate is worth meeting (and thereby would be forced to figure this out themselves before beginning interviews—an important step often skipped). Seeing these questions, the applicant would first make a quick judgment on whether she's interested in a company or role that wants to know these things, and then if she is, proceed to answer them, demonstrating her ability to communicate in a much more contextual, engaged fashion, versus modifying her own cover letter template or laboring over the blindfire of a custom one.
I see only advantages to this approach. It helps companies avoid an inbox full of inappropriate applicants who didn't even read the job description, and it enables applicants to learn more about the company and role up front while breaking the monotony of the application grind and having a greater opportunity to put their best feet forward by applying their personality, knowledge, and experience contextually, rather than packing it into a shotgun shell and blasting the job board with buckshot.
This may ask for more of an applicant's time than the current approach, especially in an era where every job site is trying to make applying into a one-click process, but as someone who has spent a truly unbelievable amount of time and effort looking for jobs (and a fair amount of time hiring), I can confidently say the dragnet application approach is ineffective, inefficient, and demoralizing compared to preparing fewer, better applications for jobs that actually interest you.
Re: Ask HN: Replacement for Stack Overflow jobs section?
#46- https://4dayweek.io/ (Disclaimer, I'm the founder)
Re: Ask HN: Replacement for Stack Overflow jobs section?
#47Re: Ask HN: Replacement for Stack Overflow jobs section?
#48Somebody please make OkCupid for Jobs. Both employers and applicants fill out questions that the community curates (so they can be job-specific, industry-specific, etc). Both employers and employees get matches via algorithm rather than receiving 100 random resumes or 100 random job suggestions that have nothing to do with you. Existing sites do this, but very poorly, because they only try to detect information out o…
OkCupid succumbed to the swiping apps, and I think a similar thing would happen except instead of swiping based on photos you would swipe based on salary.
You use Tinder when you don't know what you want or your wants are superficial, you use OKC when you know what you want/don't want.
Job searches would be similar. For those who don't know what they want, the salary is the pretty face. For those who have suffered from bad relationships, they have a checklist.
Re: Ask HN: Replacement for Stack Overflow jobs section?
#49Somebody please make OkCupid for Jobs. Both employers and applicants fill out questions that the community curates (so they can be job-specific, industry-specific, etc). Both employers and employees get matches via algorithm rather than receiving 100 random resumes or 100 random job suggestions that have nothing to do with you. Existing sites do this, but very poorly, because they only try to detect information out o…
KeyValues does just this: https://keyvalues.com "Find engineering teams that share your values" (No affiliation, just a fan)
Re: Ask HN: Replacement for Stack Overflow jobs section?
#50Earlier quoted context omitted.
What I'd really love to see is a way to find candidates via their former employers. As a CTO who recruits in a specific industry, I need to find employees who used to work at companies A, B, C.
Doesn't LinkedIn search more-or-less accomplish this? Look for people who have worked for J, Q, and U companies?