When developers on a team using sourcing.io connect themselves to the service (in order to enable the social search functionality), does this add them to the sourcing.io database? If so, doing this would probably lead to more spammy recruitment emails for all those devs.
Sourcing.io
11–20 of 59 posts
Re: Sourcing.io
#12Engineers are valuable for what they can learn (skills and about the problems they are solving) not for what they know at a particular point in time. A myopic way to look at hiring. Edit: You should care about the delta of an engineer's career and knowledge. That says a lot more about how they'll perform now and in the future. These days companies prove themselves to engineers. I'd rather see something like a more de…
I used to say this as well, as someone who has done C# (5yrs), Perl(2yrs), and Python(5yrs) work. But the truth is that there is a training/ramp-up period during that learning period. When I made the switch from C# to Python it probably took me a year or two before I became as good at Python as I was at C#. This is also true for a lot of the developers I currently work with who are using Python for the first time. Th…
A lot of people have a "Clojure" tag on their LinkedIn profile. It doesn't mean anything. You have to assume in any case that if you're seeking depth, you're going to have to talk to them.
The problem is the tacit assumption that the engineer doesn't also need to pre-validate the company before an interview.
Re: Sourcing.io
#13Yikes, on the one hand this sounds like a very useful search tool for technical recruiting. On the other, it sounds like its usefulness depends on how many members of your team you sign up for it...and once someone is signed up they scrape all their data and add it to their "database".
Re: Sourcing.io
#14Right, so I'll just come right out and say this:
What the flying fuck?
I already get a TON of recruiterspam (much of it hilariously inaccurate, like offering me a relocation bonus to move to the city I was living in).
Based on their "How do you find engineers" answer
> We scour the web, and use multiple different sources of public data to find candidates. Next we put all that information through a variety of different algorithms to try and separate the wheat from the chaff.
Re: Sourcing.io
#15Engineers are valuable for what they can learn (skills and about the problems they are solving) not for what they know at a particular point in time. A myopic way to look at hiring. Edit: You should care about the delta of an engineer's career and knowledge. That says a lot more about how they'll perform now and in the future. These days companies prove themselves to engineers. I'd rather see something like a more de…
(I'm working with Alex on Sourcing.io.)
Hi Chris--I completely agree that an engineer's ability to learn is a huge part of their value. With that said, many companies are searching for engineers who are intimately familiar with particular languages or frameworks. Anyone can get comfortable with a new framework over a weekend--it takes much longer to be become an expert.
Your idea for a better Glassdoor is an interesting. In the future we're hoping to build a set of tools for engineers who are interested in getting a job--we'd like to cater to both sides of the market.
Alex and I do not want to increase the volume of recruiting spam in the world. Poorly-constructed, boilerplate emails are the mark of a bad technical recruiter--we're not building tools to help them. We want to give the great technical recruiters a tool to help them figure out if they should be sending an email to an engineer in the first place. Furthermore, we're encouraging our customers to have the C*O's and engineers construct and send the initial emails--an email from the person you'd be working with is much better than another piece of recruiting spam.
If you'd like to get in touch and chat more please feel to email on richard@sourcing.io.
Re: Sourcing.io
#16Hello, I'm working Alex on Sourcing.io. Please feel free to ask me a question here or email me at any time (richard@sourcing.io).
Re: Sourcing.io
#17When developers on a team using sourcing.io connect themselves to the service (in order to enable the social search functionality), does this add them to the sourcing.io database? If so, doing this would probably lead to more spammy recruitment emails for all those devs.
(I'm working on Sourcing.io.)
Great question. Our database is built up by indexing publicly available information. Some (or all) of the engineers that connect their accounts will already have a GitHub account and, if so, will probably be in our index. However, we certainly don't use the social connection feature to index even more people, particularly if they're not publishing code and are more private.
The ability to see your team's extended network of engineers is really useful but we recognize that it's pretty scary to connect your personal social accounts to an app that's work-related. We're working hard to earn the trust of the engineers who happy to share their network with their employers.
Re: Sourcing.io
#18Right, so I'll just come right out and say this: What the flying fuck? I already get a TON of recruiterspam (much of it hilariously inaccurate, like offering me a relocation bonus to move to the city I was living in). Based on their "How do you find engineers" answer > We scour the web, and use multiple different sources of public data to find candidates. Next we put all that information through a variety of differen…
(I'm working on Sourcing.io.)
We don't currently have a quick-and-easy way for you to opt out--we will do soon. If you'd like to email me on richard@sourcing.io I'd be more than happy to find your profile, show it to you, and remove it permanently.
As an aside, we really hate recruiter spam too. We've just got started but our plan is to build a tool to help great recruiters manage engineer-to-engineer outreach--it's much better to receive a recruiting email from the person you'd be working with. If you're interested, they can connect you to their technical recruiter who can manage the process from there.
Re: Sourcing.io
#19So how does one know if they are in your database?
(I work on Sourcing.io.)
Right now we don't have a simple way for engineers to see what their profile looks like--we'll be adding this soon. In the meantime, please feel free to email on richard@sourcing.io so I can show you what your profile looks like. If you'd like to be permanently removed from our index I can do that right away.
Re: Sourcing.io
#20Not honest to say its 'our database' when you are just scraping/searching github and stuff. But I looked at the https://help.github.com/articles/github-terms-of-service and I don't think it says you can't scrape to a database, although at least one clause about reselling or whatever causes a question. Its cool if they are honest in their marketing and actually add something to github search, which I am pretty sure th…
(I work on Sourcing.io.)
I'm sorry to to hear that you don't like the copy on the homepage--it's definitely a work in progress and I appreciate the feedback. We're going to be adding a section for engineers soon.
Just as Google keeps a copy of the web, we have an index of all the engineers we can find in a database. This is built up by crawling publicly available information.