zlacker

>>winsto+(OP)
Hey everyone. Happy to answer any questions about this. Basically, we think that LinkedIn profiles don't do a good job of showing engineering skill (especially for self-taught people or people from non-traditional backgrounds). I'm excited to just build better support for showing side projects and GitHub contributions. LinkedIn profiles have become the default engineering resume (despite the fact that most engineers are not particularly happy with their LinkedIn profile). But there's lock-in. I hope that we have enough scale to be able to chip away at this.

>>ammon+z4
What’s the next step from here? Public profiles themselves aren’t very useful in of themselves.

Asking as someone who has been on the platform for a while but has not found any success through it. I have other thoughts but would like to hear your plans before adding.

>>hysan+o6
We plan to add more engineering-specific sections to the profiles. I think there's a lot of room to just display what matters to engineers/eng hiring managers better. Then we want to use the profiles to push the industry to look beyond traditional credentials (school, work at top companies). Recruiters say that they want to do this, but we need to get them off of LinkedIn where everything is designed around the traditional credentials.

>>ammon+88
You know what, it's clear that you've put a lot of thought into this from the product & strategy side, and these are genuinely great ideas with significant potential social impact that are worth exploring further.

But it really is a shame that from this incident, myself and many others will no longer be willing to trust you and your team with the data needed to execute on these ideas.

At the end of the day, we entrusted you with extremely sensitive data in order to use your service that could threaten our very livelihoods if exposed. Your choosing to expose this data without explicit opt-in shows an alarming lack of empathy for your users and that you were never deserving of this trust.