> The platform uses an individual’s work email to verify their work experience. For verifying educational credentials, users upload their student badge or ID or use their institute’s assigned email ID to get their profiles verified. The startup has plans to verify users’ past work experiences and education by expanding its verification feature over time.
How does this work for those who are not currently employed? Who's going to pay for this verification of work history? What about verification beyond "they were here during that time"? Many companies will not go into this detail. What prevents me from falsifying my experience? What if I am a contractor who lists projects and has never had formal employment?
Do users want to upload these documents for verification when they don't for LinkedIn? I don't think I would
Is this verification something that is a meaningful differentiation?
(2)
This is very much focused on developers who create public content, which is a small percentage. What about those that have only contributed to private code bases or don't blog? How do they feel about how their profile looks by comparison to those that do? What about all the non-tech people?
(1) - We are discovering more ways to verify past experiences. We think capturing relieving letter is one of the ideas here, but we are open to suggestions.
(2) We absolutely agree with this impression. The core principle of Peerlist is to help build Proof of work. We wanted to start with specific user personas during beta and then cater for others. We started with published content (including public GitHub repos) as it was easier to build with public APIs. We are planning to add more ways to fetch private (non-IP) metadata about the contributions on Peerlist in secure way to help a wider range of users.
(1) probably don't verify? Do customer research to see if this is worth spending time and money on. I suspect it is not. Start with the idea it is not and try to prove it is worth investing the effort in. You should seek to prove your hypothesis rather than seeking evidence to disprove it. In other words, assume you are wrong, then find evidence to support, generally speaking about hypotheses.
I can see a lot of manual workflow in this approach in verification, so is it scalable? How do you ensure that the Swiggy owns the domain swiggy.co.in or swiggy.com in an automated way?
10 comments
[ 4.2 ms ] story [ 32.1 ms ] thread(1)
> The platform uses an individual’s work email to verify their work experience. For verifying educational credentials, users upload their student badge or ID or use their institute’s assigned email ID to get their profiles verified. The startup has plans to verify users’ past work experiences and education by expanding its verification feature over time.
How does this work for those who are not currently employed? Who's going to pay for this verification of work history? What about verification beyond "they were here during that time"? Many companies will not go into this detail. What prevents me from falsifying my experience? What if I am a contractor who lists projects and has never had formal employment?
Do users want to upload these documents for verification when they don't for LinkedIn? I don't think I would
Is this verification something that is a meaningful differentiation?
(2)
This is very much focused on developers who create public content, which is a small percentage. What about those that have only contributed to private code bases or don't blog? How do they feel about how their profile looks by comparison to those that do? What about all the non-tech people?
(1) - We are discovering more ways to verify past experiences. We think capturing relieving letter is one of the ideas here, but we are open to suggestions.
(2) We absolutely agree with this impression. The core principle of Peerlist is to help build Proof of work. We wanted to start with specific user personas during beta and then cater for others. We started with published content (including public GitHub repos) as it was easier to build with public APIs. We are planning to add more ways to fetch private (non-IP) metadata about the contributions on Peerlist in secure way to help a wider range of users.