Showing posts with label recruiter. Show all posts
Showing posts with label recruiter. Show all posts

Thursday, November 19, 2015

Cold Calling "Recruiters"

Every so often, I get a burst of cold calling recruiters. I don't know if it is a season or what, but for whatever reason, I always get 5-6 cold callers within a 3-5 day span then radio silence for about a month. I always like to listen to them discuss the last activity on my resume. Because I switch somewhat frequently, I can tell how old the resume the resume they have. And, it is quite fascinating how old some of them are... then at the same time, how old my phone number is............ then how old I am...................... (sigh)

Although kind of annoying, I will admit that I did get a couple jobs through the cold callers and the jobs ended-up not bad. Respectfully, I usually just start the conversation by asking what their rates are. If they tell me, usually the numbers are pretty low, and I tell them the minimum amount it would take me to leave my current job which typically higher than (what I think is) the normal rates. "I think" because I am still figuring out how what that is.

My first couple contracting jobs, the recruiters were more than happy to meet my rate. Then I was suckered into that I already signed up for those rates when I bring up the topic after the interviews. I still worked hard and got some experience eventually leaving for something better. Odd that the same recruiter cannot find a new job for candidates they already have.

Most of the time the recruiter does not give the rate first by asking what I am looking for. So I give a much higher rate than if they gave me their client's range. What I found interesting is that no matter what I give, they always say they cannot meet the range, pick the lower ranged number, and subtract $5 / hr. So if I say that I am look for $50 - 55, they will respond, "I don't think our client can pay that but I can probably get them to do $45." I can double this amount, and they'll say $95. (The values are made up although it would be nice to make $100 / hr.)

Of course, I get fewer call backs when I give higher numbers but it is surprising (at least to me) how they won't reject any value that I provide. Although it sounds like a game, I actually give them real numbers that I can live with because if they ever do say that they can work with it, I do not want to be stuck with something I didn't mean for... even if the number is much higher than the market. Why would I leave a job that I already have good standing at to an unknown place for the similar amount?

Worst is when they ask what I do make... sometimes I give it and sometimes I do not. Why does it matter what I make? If I am going to do more, I should be paid more. If I got a job as a cashier, I am sure they will not be matching my current rate.

One of the many double standards on why everyone just hates the HR industry. Don't hate the recruiters, hate the game =P

Wednesday, December 10, 2014

I am a Release (noun) Manager, not Release (verb) Manager

I've been getting several calls from cold-calling recruiters for positions seeking a release manager. After a couple questions, I end up correcting most callers that they are looking for a release engineer. I rather call them deployment managers because most of them understand that rather than release engineer.

This site provides a good explanation of the difference between the two.

I am a release manager (release as a noun), not a release manager (release as a verb). In my line of work/responsibility, I do not actually release any code or compile any code or touch any code (except maybe to forward the package to the operations team which I really should not be doing).

Another way to look at it is that I am like a project manager who are managers on the project level while I am a manager on the release level. If a problem is on the project level (something wrong with project requirements) then it is managed via the project manager. If that same problem cannot be remedied within the release schedule, then it becomes a release level problem thus requiring a release manager to review the impacts.

A release (in my world) is a set of projects to be deployed within the same window. The projects may have weak or strong correlations with other projects within the same release. Not all companies require a release manager as most companies deal with only single project releases. There may be several projects but none are dependent on the other so can always be deployed independently, or small enough to be easily managed by the development teams or existing project managers.

Our releases typically have 2-4 large projects, several small projects, and other production issue patches. For us, releases require quite a bit of coordination due to limited resources including both human resource and hardware resources. Our environments are hardware dependent costing tens to hundreds of millions of dollars so we cannot just simply "spin" up another test environment.

The release manager does not (in my opinion) have the authority to make a final decision on how the new issue should be resolved. The release manager has to be capable of providing the different options and the recommended course. The product, customer, or client should make the ultimate decision.

Typical choices could be:
  1. delaying all phases to accommodate the new timeline
  2. removing the project from the release (there still exists risk that this still delay the deployment if there are issues removing the project)
  3. do not fix and deploy with a known defect (adds risk to customer satisfaction and/or data integrety)
  4. shorten the timeline of a future phase if possible (typically requiring a group to work overtime)
  5. use the buffer time if one was implemented (typically adds risk to a shortened quiet period)
These terms are not set in stone as the position (to me) seems relatively new (within the last decade) as can be seen by all the recruiters that does not know the differences either. The terms have been around long enough for some stability in their usages. Truthfully, I did not know about this type of position until I was hired here, and didn't know about release engineers until the recruiters started giving me job descriptions that did not match my roles.


Reference

http://www.plutora.com/insights/2014/release-management-vs-release-engineering/

Monday, June 9, 2014

Work Life: LinkedIn, More Recruiters than Professional Contacts?

I occasionally log into LinkedIn to read some of their articles. Although somewhat amateurish, they are rather insightful in getting me to think although no always in agreement (at least not 100%) with the article. Every so often, I get a new request from someone that wants to be added to my contacts list.

If this keeps up (although would take a rather long time), I may eventually end up with more recruiters than business professional contacts. This got me thinking that LinkedIn really needs a new feature to separate recruiters from my regular contacts.

First, recruiters really know nothing about me. Personally, I think they are just poaching my contacts list. I have added one or two that I have worked closely with in the past but have since removed them from my list. I may consider keeping recruiters that really are professional contacts. I may consider adding them if my contact list was not shared with them.

Second, they do not care about my work. They do not provide any value to my professional portfolio except maybe to make my contact list look larger. But, I know plenty of excellent people with very few contacts. Do they really look at my list for referrals? How would they know who I actually work with?

Third, I do not want to be adding recruiters while being employed. I do not this it looks good when your managers or coworkers (who are also on LinkedIn), suddenly see an influx of recruiters on your new contacts news. I do not wish to risk my boss to think that I am a liability to the team.

But, I am curious what they have to offer. Although I am not interested in leaving, I still need to do my due diligence as a professional. LinkedIn would provide an excellent portal for me to see what other opportunities are out there. Somehow I am meeting more people who are also looking for work, and reference would be a much better way to introduce someone to an opening. I think there are some good benefits LinkedIn should look into for these types of avenues. It will grow higher quality candidates, as opposed to candidates from the masses (i.e. Monster, Dice, etc.).

Sunday, August 11, 2013

Interview: Dear Interviewer, Would you Answer Your Own Questions Honestly?

Dear Interviewer, Would you Answer Your Own Questions Honestly?

If you are new to interviewing, these are good starting points (or see link below).

What I have thought interesting since I started interviewing is how "textbook" some of the answers are to the interview questions. All questions are structured to get some sort of information about the interviewee, but do interviewers ever think about what the interviewee thinks about the company on certain questions?

One of the questions, "Tell me about the worst boss you ever had," the interviewer is "trying" to see if you are going to talk smack about your older bosses. Almost everyone will recommend that you try to redirect the question to something positive, but why not say bad things about a bad boss (unless you've only had 1-2 bosses then I would also recommend you avoid answering this directly)?

Is the new boss expecting to be bad? If he is not bad, then why would he worry about what I say about bad bosses? Who has not had a bad boss? I mean this is like asking, "have you ever lied?" We all know the real answer, and we know that is not the answer the questioner wants to hear. Basically, you want us to lie. Is that how you want to start someone's career at your company?

If going the route of "yes, I do lie," I would also suggest that you add what you did about it. Like when my boss hired someone that was weak, I wrote a report trying to avoid any personal bias. I told her that this is my opinion and that I respect her choice because there are usually other factors that they have to consider that I am not privy to. Another example was a poor process. I recommended a better process with analytic on how it is a better business strategy. I want to show that I will go to my boss with my experience and my knowledge. I do not jump levels and report to his boss about my thoughts on him. If you cannot back up your actions, then maybe you should stick with the suggest response from CareerBuilder.

What if your boss was doing something illegal? I have not actually thought about this... and I am not sure exactly what I should do on that matter. I'd probably read the employee handbook and probably should be handled by HR. Anyways, this is probably a bit too personal to answer publicly because if you happen to be my boss... it is probably better that you don't know what I would choose. To all the not-worst bosses, what would you suggest?

Another question is "Where do you see yourself in five years?" Does anyone really know where they see themselves in five years that are relevant to work? Does the interviewer even know where they see themselves in five years with their current work? How can they expect that from someone who doesn't even know who is going to hire them?

I seem to dislike questions that really only have one correct answer. These types of questions only seem to serve one purpose and it is not to understand the interviewee. If you or your HR is not going to put effort into finding the right candidates, I have lower views of your company. Does that mean I will not choose you? Unfortunately for me, I probably would consider the option since most companies ask the same types of questions.

But like interviewers who are looking for that one ideal candidate, I am seeking for that one ideal employer and I hope to do so by being more straightforward about my profession abilities. If there was one recommendations for employers about their interview questions, that would be that you would be able to answer the same questions you ask: "tell me who was your worst manager that you've had," "where do you see me in five years?" If you do not like answering those questions, then do not ask those questions. Like interviewees, avoid lying because you will not get what you really want. It is a lose-lose for both parties.

On a different matter, these staple responses from recruiters and head-hunters are things that have always made me uncomfortable with them. Shouldn't they be people who should be making the hiring process easier by being more honest about the truths? Why has the whole interview process been mutated into something that favors people who know how to interview and not their real talent? Does a company really care if someone knew how to answer a certain question that is really irrelevant to them? Who cares if the person cannot see where they are in 5 years? Who cares if they had a bad boss or had all bad bosses? They only care that the employee adds value to the company.

I am not saying that the knowledge is important. It is important to know if we have ambition or have social issues. But you are expecting someone to know those with just one or two questions?

Sometimes I wonder about the use of recruiters. Their business model revolves around getting people hired. People don't get hired if the company already has perfect people. They love churn because that gets them the bonuses that they work out in the contracts.

I think there is a lot of room for improvements for HR, recruiters, and head-hunters to really make more long term solutions to the interviewing process. I think recruiters have the most to gain especially with the current technology in social networking. They can now keep in touch with people for several years without being very intrusive.

Why recruiters? Because companies do really not care much about employees or potential employees' life outside of their company. They want to focus on their product. Also on the political level, there are some managers that hire people they know over people people who are capable. It only takes one poor manager to make systems extremely inefficient.

And, people want to focus on their skills so that they can add value where they are talented at. Why should the person know who they work best with, especially when the employer does not even give them a say in the matter? People struggle to get themselves hired and you want them to know someone else?

This leaves the recruiters to find the best matches because that's their role in the process. They care that you did good work for Company A, showed loyalty in Company B, and demonstrated hard work at Company C. They should care that you had that one bad boss but you overcame it. They should have a better idea what your 5 year goal is better than the interviewee (isn't it kind of messed up that they call the company the client and not the other way or even both?) With their experience, they should know where you can be in 5 years and they should know what the company would expect in 5 years. They should know historically who you have worked best with. Not only that, that knowledge should be exactly the same except that you explain it in the perspective for that person. Too bad they only care about the person being at the right place and at the right time... if not, they move onto someone else.

Anyways, there's probably an infinite and one reasons to why the system is not that way. Unfortunately, I cannot help but think on these processes on a part-time basis as I would really wish to focus on processes on building new engineering technologies. I have been distracted by other industries because getting good coworkers is the biggest problem in process improvements. So here's my weakness... I am easily distracted by things that I consider the biggest problems on things that are preventing me from working on new engineering technologies.

Reference:
http://www.cnn.com/2009/LIVING/worklife/03/04/cb.answering.tough.interview.questions/