[MacsHeadroom]

Changed enormously. Both resumes and interviews are effectively useless now. If our AI agents can't find a portfolio of original work nearly exactly what we want to hire you for then you aren't ever going to hear from us. If you are one of the 1 in 4000 applications who gets an interview then you're already 70% likely to get an offer and the interview is mostly a formality.

[Gigachad]

What worked for me is just ignoring the job listing websites, and calling recruiters directly on the phone. Don’t bother hitting “easy apply” just scroll to the bottom and call the number.

I’ve also been asked for the first time in ages to come to the companies office to do interviews.

[andrewflnr]

What do you tell them on the phone? Are they prepared for just "Hi I want to apply for the $job position"? And do they have an answer besides "cool, use the website"?

[Gigachad]

They put their phone number there because they want you to call it. I say "I saw this position <position name> advertised on LinkedIn and I'm interested, is this still available?"

Last time I did this they told me it is but that they are at late stages of interviewing so I shouldn't bother applying for that one, but they got down my details and had other jobs that matched what I was looking for. Recruiters are sales people and you just reversed cold called them making their job easier. The majority of applications are AI bots and people who don't live in the country the job is listed in. By making a phone call you are up the top of the list of "most likely to be a legitimate applicant".

[johnnyanmac]

And when was this? I can't remember the last time anyone had their phone number publicly displayed on LinkedIn. And now messaging recruiters is a paid feature. The market's only making it more difficult to reach a human.

[Gigachad]

This was last week. Perhaps the Australian market is different, but I often but not always see the option to physically call.

[andrewflnr]

US here. When I've tried similar tactics in other contexts, I tend to get an answer along the lines of "cool, use the website", and politely trying to get me off the phone. But maybe it's worth a shot. :)

[johnnyanmac]

Yeah, it may be a cultural difference. The US has a huge fear of doxxing in the modern world. Can be traced back to decades when a crazed fan murdered a celebrity in their home. Easily accessible firearms definitely doesn't help.

This even applies to businesses in some cases. You trying to walk in and talk to someone is a security threat compared to the times where you could do that and walk out with a job offer. US companies absolutely hate unsolicited calls from non-businesses.

[tmpz22]

If the interview is mostly a formality is it still multiple hours of leet code?

[MacsHeadroom]

No, there are AI's specifically for solving leet code. It's a waste of time.

https://leetcodewizard.io/

[johnnyanmac]

>If our AI agents can't find a portfolio of original work nearly exactly what we want to hire you for

that'd be a huge issue for most candidates (and basically all top candidates) because "exactly what you want to hire you for" is probably not open source code to begin with.

>If you are one of the 1 in 4000 applications who gets an interview then you're already 70% likely to get an offer and the interview is mostly a formality.

That has not been my experience at all in 2023/2024.

[fifilura]

Does that mean you will not hire anyone without a public portfolio?

[Pooge]

I thought that meant what you typically write in the "Experience" section. GP, am I wrong?

Is everyone writing a "Projects" section by rewording what they wrote in "Experience"?! For me, "Projects" should strictly be personal projects. If not, maybe that's what I'm missing.

[sshine]

Projects are personal projects, or at least projects in which you did a distinguishable effort.

They don't have to be public to the whole world, you can have links that are only in your resume.

But if they're on GitHub, they have to be public, since there aren't unlisted repositories.

[mdaniel]

I actually believe that it would be possible to provide a read only clone url in a resume link but I don't know if a way to make a link to a browsable version (short of having a proxy server type setup, or, of course, a slim server protected by http basic)

[Dwedit]

Github does allow private repositories.

[sshine]

Yes, but you'd have to invite each interviewer by their GitHub handle.

An unlisted repository would be one that is public to those who know the URL.

[MacsHeadroom]

I'm saying the sections of the resume don't matter at all. The resume is basically ignored. You either have public code you can point to on Github or you aren't ever hearing from us.

[joshdavham]

I’m curious to hear a bit more about your rationale for this. Is it because trust is otherwise hard to establish between you and the candidate? Is it like “if we can’t see the candidate’s code then we have no evidence they can code”?

[MacsHeadroom]

Essentially, yes. Public portfolios come in different flavors though. Most often it's code. But sometimes it's research, a blog, transcripts of talks ripped from YouTube.

[crooked-v]

> a portfolio of original work

I'm too busy doing actual paid work for companies for that.

[lnsru]

That’s the reality for most people. Creating many things under NDA with tools watching for IP theft. So no single line of code can leave the company. I know a guy who has a portfolio, but he’s freelance web designer.

[MacsHeadroom]

IP secrecy isn't a moat in the age of AI. Open Source is the only way.

[lnsru]

Tell this to the army of lawyers at my ex-ex-workplace. Every document I printed was reviewed by our security officer (I met him months after I left by accident and we had a chat).