Similarly, quitting or moving around should be easy as well. If you are an employee of a very big company, it's kind of like that already--moving from one team to another is a lot easier than finding a new job, new bosses are cognizant of the fact that you might need some training or time to get up to speed, ect, etc.
Discussion: Job seekers can't find a job and Employers can't find an employees
151–160 of 381 posts
Re: Discussion: Job seekers can't find a job and Employers can't find an employees
#152I was laid off last year during the major tech layoffs and I had a few interim management jobs since. Nothing permanent yet though and I see myself as a missionary not a mercenary so 'just' contracting doesn't fulfill me.
What I've noticed that where there used to be just a few applicants there are now many. This is confirmed by other job seekers. Jobs posted are also sometimes fake. Just window dressing so to say. I've gotten offers from within my own domain of less than half I was earning. For a NGOs I could consider that but for high tech or finance that's stuff I cannot take seriously.
I noticed I need to work on my positioning and network harder. I did not have to apply for a job in 15 years so I am a but rusty in that respect.
What I think is happing in the industry is that the macro economic developments are still quite uncertain and companies haven't figured out their strategies yet. So they stick to what they know.
Re: Discussion: Job seekers can't find a job and Employers can't find an employees
#153It's not any kind of paradox. Structural unemployment happens when the skills of the work force don't match the needs of employers, so there is both unemployment and difficulty hiring. Structural unemployment is usually high when there's a rapid change in demand for skills, as of course there is in tech. It results in crazy high salaries too. People with machine learning experience are getting 7-figure offers, while…
Structural unemployment happens when the perceived skills of the workforce don't match the perceived needs of employers, so there is both unemployment and difficulty hiring. A lot of engineers will tell you that companies are often expecting both too much (precise types of experience) and the wrong things (leetcode-type challenges, unnecessarily specific knowledge...), which leads them to pass over perfectly qualifie…
I hate it, but I don’t see a better way that doesn’t have its own limitations. (Referral of known ex-colleagues is a good one, but that’s limited in scope and has diversity problems).
Re: Discussion: Job seekers can't find a job and Employers can't find an employees
#154What works is companies not demanding that their employee be the square peg that fits their square hole. The square peg doesn’t exist. You’re going to have to hire someone who doesn’t already have the specific skills you need and invest in training them and educating them. The interview process is just to evaluate if they are capable of succeeding in that process. Yes, it means companies have to take risk. It’s bette…
Unfortunately, the skill of being trainable/educable is very unevenly distributed in the population and very hard to assess from afar. Instead, companies hire based on whether you've already been trained/educated in how to do the thing, which amounts to letting someone else take on the risk associated with your failing to learn something. If I were tasked with solving this, I'd advocate for more frank discussion and…
Re: Discussion: Job seekers can't find a job and Employers can't find an employees
#155I don't understand the hiring people industry. The questions thrown at me are trivia, if I knew the answer, or not, it doesn't mean anything. People are looking for weird specifics for things that ... really don't need it. The job inevitably doesn't even rely on those specifics. I'll learn whatever anyone wants, I like doing that ... no honestly I do. Can I just talk to the folks I'll potentially be working with / fo…
I’m with you. It’s hilarious to think back on, but I got a “no” from my present employer after the first technical interview because I didn’t remember the options to one particular tool. Thankfully a somewhat distant inside connection was achieved, who managed to suggest “maybe that wasn’t actually the correct decision” and I got the chance to continue with the process. It’s all been good since then. I sure do have a…
But they also did give me what I thought was quite a good test, which was talking through some working code and suggesting how it could be improved.
Re: Discussion: Job seekers can't find a job and Employers can't find an employees
#156It's not any kind of paradox. Structural unemployment happens when the skills of the work force don't match the needs of employers, so there is both unemployment and difficulty hiring. Structural unemployment is usually high when there's a rapid change in demand for skills, as of course there is in tech. It results in crazy high salaries too. People with machine learning experience are getting 7-figure offers, while…
It is a paradox, because it is a market where people basically only do one salaried job at a time, meaning they have a fixed 40-60 hours to sell and it shouldn't take long to sell it if they want to move on to another job. (Here "selling" means you've been hired for your next job, since you just took the 40 hours you had available every week starting next month and sold it for money.)
Within reason, people can be retrained to adjacent jobs or basically could do exactly what an employer wants within a low number of weeks. People know what kind of jobs they're capable of or it can be tested for quickly.
Instead there are candidates who spend a year both training themselves and applying for jobs unsuccessfully, while employers spend MORE than the same amount of time on that, if you add up the amount of time recruiters are putting in on behalf of employers and HR puts in and employers put into interviews. It is a market failure for people to want to work, for employers to want to hire them, for them to be able to do the work, but for them not to actually be doing the work. It would be kind of like if people were desperate for any of either tomatoes, carrots, wheat, rice, potatoes, or really anything, whatever they get is fine for them since they can look up recipes for that and make it with a tiny investment of time (this is the demand side), so they are putting in ads for "Want any of: rice, carrots, wheat, potatoes, tomatoes" and willing to pay for it! Just put up a hundred ads, a hundred unfilled jobs. On the supply side meanwhile you have a farmer who owns all the necessary land (hours in the day) and has ALL the equipment (a computer, Internet, transportation, clothes, anything anyone needs to start working) and is really willing to produce anything and can do so on that arable land! There are no capital requirements. Great. So we have the demand side taken care of, people want quite a few different types of food and supply side taken care of, the farmer is willing to farm just about anything. But, for some reason, what ends up happening isn't that the fields are filled, it's that there are farmers spending all day every day selling and nobody is buying. And instead of saying, here try this sample, and it's fine, you have a weird request for "What exactly had grown on these fields since the beginning of time" (this is called a resume) and then you have buyers inundated with answers to their bizarre requests for "what has grown on these fields since the beginning of time" but the buyers still aren't getting the food and the fields are empty, the farmers are trying unsuccessfully to sell all day and the buyers are somehow inundated with sales pitches but aren't actually buying anything, while burning time on putting up advertisements of all the food they want to buy.
Why is this happening? How can people not be working but want to work, when they can train into being productive workers within a few weeks and are more than willing to do so?
It would be like if shoppers spent days at a time at farmer's markets going from stand to stand and buying nothing, and farmers spent days at a time standing at the farmer's market with buyer after buyer asking them questions about the history of their land and not buying any damn potatoes. It's a potato lady you want it or not? If not step aside so someone who actually wants it can see it.
p.s. half of the farmers are asking other farmers to endorse them on linkedin. Buyers ignore this noise completely.
The job market is highly dysfunctional.
Re: Discussion: Job seekers can't find a job and Employers can't find an employees
#157Earlier quoted context omitted.
Out of those quality candidates that apply: Some will find a job before they finish you interview process. Some will change their mind. Some will have a change on personal circumstances. Some (many?) will ask for more than you can offer. To hire one good person, you usually need many to apply.
> Some will find a job before they finish you interview process. "one quality candidate might be perfect, because then the hiring process can go very fast" > Some (many?) will ask for more than you can offer. This seems to ignore my point 1 about listing salary/compensation on the job posting.
Re: Discussion: Job seekers can't find a job and Employers can't find an employees
#158The goal isn't necessarily to hire the best candidate, but rather the least risky one. Often one gets a large set of resumes and most of them are clearly unqualified for the position and then upon interviewing many others are also unqualified.
The tools to mitigate that risk are things that qualified candidates are adverse to (see the "say no to take homes") and can often find a position through their networks of knowing who has a job open.
A person at the company attesting to "my friend John who I worked with before is looking for a job" which in turn drastically reduces the risk of hiring since this is a person who an employee has worked with before. It doesn't always mean a "hire right now" but if company policies allow for it, it can move a person to a short list.
With risky hires who turn out to not be qualified, the cost of the hire can be much worse than not hiring anyone in that spot. I have worked with people who have generated negative value and spent a good bit of the next year cleaning up things scattered through the codebase.
---
ROI
It often takes about a year for a new hire to become a positive contributor. The next year the balance of the slow down of work, training, etc... it then balances out.
There are few candidates who can hit the job running. Most people take that year to become productive.
When a candidate is hired and leaves within that time, this costs the company money. At some point the company is going to hire people who don't need training (see problem with testing and take home). Even then, it's often cheaper to not hire someone.
And so the "we want someone with all these skills since we're not going to train a random person on Oracle PL/SQL only to have them leave in 9 months."
---
Expectations
Most companies can't spend Big Tech money on salaries. And it is life changing amounts to move to it and furthermore, once you have a lifestyle associated with living in Big Tech compensation, it can be hard to leave - the golden handcuffs are real.
If you're working for a big tech company in the 10% of compensation, going somewhere else to work at the median is a big hit. This limits the pool where a person considers.
---
Shotgun resumes
If you get multiples of the number of people who can reasonably be considered, one of the first / easy passes is to remove resumes that haven't shown an indication that they've read the posting. This also means removing resumes from the candidate pool that appear to be technology packing their resume (more than 1 page per decade of experience, "worked with: list 20 technologies here" on each position.
This tends to remove people who are more risky to hire from the pool.
The part from the OP:
As first step, you start with the companies you like/know with being a bit more selective on the jobs but after some point you basically apply all somewhat related jobs and then want to see what happens after. (which only increase the complexity of the problem)
Once you start sending the same resume to everyone the rate of people looking at your resume drops off significantly since it doesn't resemble the position that is being applied for or have any reason why they are applying there... meaning that even if they do get hired, this is a position that they're looking to start searching for a new position on day one and as an employer, you're better off not hiring someone.Re: Discussion: Job seekers can't find a job and Employers can't find an employees
#159Earlier quoted context omitted.
Structural unemployment happens when the perceived skills of the workforce don't match the perceived needs of employers, so there is both unemployment and difficulty hiring. A lot of engineers will tell you that companies are often expecting both too much (precise types of experience) and the wrong things (leetcode-type challenges, unnecessarily specific knowledge...), which leads them to pass over perfectly qualifie…
Leetcode (or hacker rank or others) and other algorithmic qualification (have recruiter ask for years of experience in exactly X) is an understandable response to the automated firehose tools that allow applicants to deluge companies with applications with relatively low effort per app. Companies have to find some way to filter out the percentage that have very low likelihood of succeeding. I hate it, but I don’t see…
However, regardless of "who started it" in this round, ultimately, it is unquestionably a situation we can lay at the feed of industry, which abandoned decades ago the practice of actually training new hires for their positions. Sure, there are prerequisites they can expect (eg, in a programming position, you can expect some level of school learning or experience with programming in general, or particular categories of program/lanugauge), but the degree to which employers are willing to train people on the stuff they use has declined precipitously since the late 20th century. This is a well-known phenomenon, and it is substantially responsible for the modern arms race between job-seekers and prospective employers: if you know that whoever you bring on will get 3 months of well-designed training for the role they'll be filling, you don't need to spend 6 months vetting them over 10 rounds of interviews for an entry-level position.
Re: Discussion: Job seekers can't find a job and Employers can't find an employees
#160Earlier quoted context omitted.
Because on the other side, there are too many applicants who can't do the job but apply anyway. So the company needs some way to filter, otherwise they'll waste huge amounts of time and money interviewing people that can't do the job. They have no good way to filter, so they'll left with only bad ways.
> there are too many applicants who can't do the job but apply anyway. So the company needs some way to filter, If we take that as a given, and I don't disagree with you, what happens? The hiring pipeline becomes optimized to prevent unqualified people from getting through the process. It's focused on reducing false positives: hiring the wrong person. As a side effect, it eliminates more people who might be hired bef…
This isn’t a single round N-choose-1 game; the unqualified candidates don’t dematerialize, but rather keep applying and may even engage with automation tools to apply to hundreds of roles every day. So, they become wildly over-represented in the applicant pool for any given role.