Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why I Don’t Talk to Google Recruiters

yegor256.com

Post reply on HN
Print view View original

511–520 of 674 posts

Re: Why I Don’t Talk to Google Recruiters

#511

Post by dsk139 »

mooreds wrote: post #468
dsk139 wrote: post #281

Earlier quoted context omitted.

Feel free to e-mail (in profile). Started by trying to build tools for recruiters and interviewing recruiters for customer feedback. Found a good fit with a recruiter who placed my whole NY team before our startup got acquired and he offered me a consultant gig. Really enjoying it so far. Great way to monetize a mix of engineering career consulting + staying on top of startup trends.

Interesting! Do you feel like as you get further and further from having done the actual work (that you're helping recruit for) that you'll still be as effective?

I'm still coding professionally (js eng) and stay on top of trends! But, I don't think coding in the trenches will make me more effective. I've had a few eng. jobs, most of my friends are engineers, and I'm really passionate about job trends, job satisfaction, and employee retention.

With that foundation I'm more effective as I see more career trajectory data points when I talk to candidates that specialize (data, security, devops, ml) or ladder up (vp, manager, cto). Then I can provide even more value to new candidates with the career counseling approach.

Re: Why I Don’t Talk to Google Recruiters

#512

Post by inkblot11 »

I've interviewed at the major software companies, including Google, Amazon, and Microsoft. In all interviews I was interviewed by the people and managers I would be working with. In many cases, I would also interview with members of other teams I would be expected to interact with. I now realize I must have taken that for granted and did not realize it was a privilege.

Re: Why I Don’t Talk to Google Recruiters

#513

Post by ryandrake »

sqeaky wrote: post #472
ryandrake wrote: post #423

Earlier quoted context omitted.

Have you ever actually got a job that you accepted through this method? Also, what wizardry did you use to get 200+ recruiter E-mails a month? Do you just have a highly optimized resume out there on all the job sites or something?

I get between 30 and 50 a month and all I really did was setup a linked in profile.

Incredible--would you mind sending me your LI profile (privately of course, email in my HN profile)? I'd love to see an example of a profile that generates that much interest, even if it's mostly low signal.

Re: Why I Don’t Talk to Google Recruiters

#514

Post by nulagrithom »

stcredzero wrote: post #496
nulagrithom wrote: post #437

Earlier quoted context omitted.

I tend to run in to more critical issues than performance, like shipping the product/feature at all, meeting deadlines, writing maintainable code, and writing documentation. In your highlighting example, instead of working with someone who will optimize, I'd much rather work with the guy who will realize we can just debounce the dialog, write a one line comment about the performance issue, and then move on to the nex…

We didn't ship in time and I had to find a new job when the project got scrapped. Damned if it wasn't fast though. Sounds more like a project management issue to me, than a problem with that coder.

Three man team and he was the lead. Yes, it was a project management issue.

I'd rather see basic project management skills than basic knowledge of algorithms. Unfortunately, the former is much more rare.

Re: Why I Don’t Talk to Google Recruiters

#517

Post by dba7dba »

ryandrake wrote: post #31

Unlike most of HN (it seems), I like hearing from recruiters, because despite the very low signal-to-noise ratio, there's always that remote chance that one of them could be able to set me up with a "dream job". It's zero cost to me to politely reply to a recruiter and ask for more info, and I try to at least respond to everyone. What I've found is that they must have a lot of candidates they're juggling because fall…

Many years I had sent out resumes looking for work as a MCSE. Never mentioned novell. Guess what? Recruiter emailed me looking for novell engineer... Hw fell out of my funnel real quick.

Re: Why I Don’t Talk to Google Recruiters

#518

Post by DonHopkins »

coldpie wrote: post #505
DonHopkins wrote: post #391

Earlier quoted context omitted.

Q: How many Google engineers does it take to screw in a lightbulb? A: Build great content. https://twitter.com/dr_pete/status/623981710003187712

I don't get it.

It's the standard Google answer to every question.

Re: Why I Don’t Talk to Google Recruiters

#519

Post by kirykl »

stcredzero wrote: post #148

There is no point in giving me binary-tree-traversing questions; I don't know those answers and will never be interested in learning them. Let's presume this is out of preference and not ability. It's a pretty basic concept. If your preference stops you from learning something as basic as this as a programmer, then it doesn't seem likely that you will be motivated to keep up with even more abstruse concepts. Nearly e…

could you explain what you mean by stream ?

Re: Why I Don’t Talk to Google Recruiters

#520

Post by coldpie »

hashseed wrote: post #433
enraged_camel wrote: post #331

Earlier quoted context omitted.

I'm not sure I buy that distinction. Do you believe that experimental physicists know every single formula and can recite it off the top of their head? Because unless they use those formulas constantly in their work, they end up having to look them up. Same thing with algorithms like tree traversal. You should know the theory behind them, but unless you regularly implement them, there is zero reason to commit their i…

But imagine Einstein having to look up how to derive x^2. I'd say that's a pretty close equivalent to knowing tree traversal in CS. It should just come naturally.

I've been working in the programming industry for ten years and have never had to implement tree traversal. I could probably scrape together a naive implementation in a relatively short amount of time, but it's certainly not something I've memorized. But then, I'm a programmer, not a computer scientist.
Post reply on HN