thanks guys for the feedback, very instructive.
On Mon Dec 01 2014 at 1:14:53 PM David Rogers <[email protected]>
wrote:
> As far as responding to a recruiter, I am not concerned with whether they
> post the job source company or not. In the past, I've responded to
> recruiters that disclose their client and those that don't. Once I get to
> know them, the reasons for choosing to stay with a particular recruiter are
> mainly with their ability to do their job (negotiate, connect, persuade,
> advocate, etc.):
>
> - honest
> - how well do they sell me to a potential, interesting employer ("coffee's
> for closers")
> - do they help me negotiate the right salary
> - do they have enough opportunities such that, if one blows up, there are
> others that are interesting enough to pursue
> - easy to work with, responsive, willing to listen, won't pressure me
> - they understand what I'm seeking when I describe it to them, and if I'm
> not sure, they can help me narrow it down
> - someone with whom I can possibly have a beverage and I'd like to work
> with again
> - bonus points if they know different members of the team and can give me
> insight into their personality styles, what it's like to work with them,
> etc.
>
> Again, I don't consider whether they disclose their clients or not, very
> important. I just expect that they won't and if they do, that's fine too,
> but to work with them, they'll have to meet the above criteria. Many
> (most?) companies don't have exclusive agreements in place with just one
> recruiter/agency which makes it theoretically easier for the engineer to
> find the right recruiter to work with, and to get the best opportunity.
>
> Currently, one recruiter fits the above criteria for me. I'll disclose who
> it is if you email me, privately.
>
> - Dave
>
> On Mon, Dec 1, 2014 at 10:21 AM, Jason King <[email protected]> wrote:
>
>> I think it would be stupid to name the company in their first post to an
>> open mailing list like this. I rarely meet a recruiter who won't disclose
>> the company in a private communication after initial contact has been made.
>>
>> On Sun, Nov 30, 2014 at 9:20 PM, Ian Young <[email protected]> wrote:
>>
>>> 1000x what Matt A said. I pretty much immediately disregard any job
>>> listing that doesn't name the company, and I'm sure others do this too. I
>>> know this is how the system currently functions, but if I were a recruiter,
>>> I'd be real anxious to figure out an alternative.
>>>
>>>
>>> On Sun, Nov 30, 2014, at 09:05 PM, Matt Aimonetti wrote:
>>>
>>> Sorry if this is a bit OT, but I'm always surprised by how recruiters
>>> are so reluctant to name the companies they hire for. I understand that you
>>> have in-house and external recruiters and the pay depends on who brings
>>> candidates, but I'm curious to know if that's the only reason not to come
>>> out and say "we are hiring for X Y or Z".
>>> I would imagine that you would get more/better candidates if the
>>> candidates could know in advance if they are interested in more than a
>>> "stellar opportunity" in a well defined location.
>>> Do any of you (potential candidates) reply to vague recruiting emails
>>> like that?
>>>
>>> - Matt
>>>
>>> p.s: Matt Haines, not sure if you did it on purpose or not, but you
>>> replied to the entire mailing list :)
>>>
>>>
>>>
>>>
>>> On Sun Nov 30 2014 at 8:37:30 PM Matt Haines <[email protected]>
>>> wrote:
>>>
>>> Hi Jon,
>>>
>>> Drew Haines and I are RoR enthusiasts and run Devco, a software
>>> development company here in San Diego.
>>>
>>> Our skill sets seem to line up with what you're looking for. All of our
>>> projects are done on Rails and bootstrap.
>>>
>>> If you'd like to discuss details let us know and we can meet in person
>>> or virtual, whichever is easiest.
>>>
>>> My email: [email protected]
>>> Drew's email:[email protected]
>>>
>>> Our Company: dmDevco.com
>>> Our product: HoursLogger.com
>>>
>>> Talk soon,
>>> <MATT>
>>>
>>> --
>>> --
>>> SD Ruby mailing list
>>> [email protected]
>>> http://groups.google.com/group/sdruby
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "SD Ruby" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>> --
>>> --
>>> SD Ruby mailing list
>>> [email protected]
>>> http://groups.google.com/group/sdruby
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "SD Ruby" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>>
>>> --
>>> --
>>> SD Ruby mailing list
>>> [email protected]
>>> http://groups.google.com/group/sdruby
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "SD Ruby" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> --
>> SD Ruby mailing list
>> [email protected]
>> http://groups.google.com/group/sdruby
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "SD Ruby" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> --
> SD Ruby mailing list
> [email protected]
> http://groups.google.com/group/sdruby
> ---
> You received this message because you are subscribed to the Google Groups
> "SD Ruby" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>
--
--
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
---
You received this message because you are subscribed to the Google Groups "SD
Ruby" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
