3 ms·
Just keep an eye out for your friends telling you that they have so and so position available. Then let them know you have someone good who'd be a good fit. Als
by vaksel 18y ago
Just keep an eye out for your friends telling you that they have so and so position available. Then let them know you have someone good who'd be a good fit. Also if you know a good recruiter pass their resume on.
But only do it, if you are 100% sure it won't come to bite you in the ass later.
3 stories:
1-Guy went into an interview. Told me he knew a language, when he didn't. I got a friend to get him an interview at his company...turned out he couldn't write a simple select statement. He knew the theory, but he didn't practice writing the actual code.
2-Guy went into an interview, got tired of interviewing after 4 different people, and walked out. And on the way out he called his last interviewer a bitch under his breath...which she heard.
3-Guy went into an interview...got an offer. Accepted it. Then 1 week later got fired for incompetence. Apparently he was a very slow coder.
In each case, the person I asked to help out got in trouble. And I got an earful for putting them in hot water.
- carterschonwald 18y agohow slow is slow? Its one thing to be slow implementing a precise spec where the algorithms are sketched (ie problemeatic), its another thing (ie reasonable) to be slow cooking up a nicely designed tool with good / nontrivial algorithimics and interface
- vaksel 18y agoI don't really know the details, but he got fired after something like 1 week, so I doubt it was in regards to something complicated.