Hey
guys,
Recently, I had to
go through one of the perfect "nightmare" scenarios when it comes to hiring in
Bangalore.
To get a sense of
the issue, you might want to read this entry on my blog first .. http://www.logic2go.com/index.php/archives/2006/04/09/
For those who don't
want to read above, basically ... I made a job offer to a programmer, he
accepted over the phone, we spoke salary details and sent him the offer letter
with a pre-defined start date. He didn't show up to work as he had taken up
another offer and moved from Bangalore to Delhi.
..... that was early
April.
Now, early May, he
contacts my company again and wants to see if the job offer is still good.
This person is a
decent developer and I'd like to see if we can use him, so "yes" the offer is
still good.
His reason for
moving back from Delhi to Bangalore in under a month was that the company in
Delhi had offered a higher salary, but once he got there, he realized that the
work wasn't intellectually stimulating. So he is willing to take a pay-cut to
work with my team and do some really fun stuff like RFID, TabletPC development,
etc, etc. I put him on a lower salary for a 2 month probation period in which he
can decide if we are the right team for him and we can decide if he fits with my
work ethics and standards (I do it with all employees, it's my version of a
2-month interview process)
Now, he is supposed
to join us on Monday (15th May).
He lands in
Bangalore, but he doesn't come in.
Tuesday (16th May)
... he still doesn't come in.
So we call him
... and his response "I'm not happy with the offer and the salary
amt."
So why the &*^%
did you fly from Delhi to Bangalore on your own expense and waste my time and
resources if the salary wasn't high enough to begin with?
Arrrgh.
Oh, if you or your
HR departments encounter a certain Ravi Gyani ... you know what kind
of job to offer him.
I'd take a less
technically competent but stable employee any day over a smarter but jumpier
one.
As in any other
game, long term stability matters here too!
-
VB
