Live data from Hacker News

Learnings of a CEO: Matt Schulman, Pave, on Hiring

ycombinator.com

31–35 of 35 posts

Re: Learnings of a CEO: Matt Schulman, Pave, on Hiring

#31

I talked to Pave last year and bowed out after hearing how they do business. Their business model and their techniques could have changed since I last talked to them. At the time, customer companies give all their compensation data to Pave, including employee names, and then they use that to create compensation data across the list of their customers and share it. They were targeting startups, but I don't know if the…

Hi, I work for Pave (but I don't speak for Pave, etc etc).

> If I remember correctly, because they have your name, they also scrape LinkedIn data about you and try to get as much information about you as possible like job titles, etc.

I am not aware of Pave doing anything like this.

> I would not want my entire salary history to be shared with prospective employers so that they could definitively say "Well, this person got paid X in their previous position, we shouldn't pay more than 5% above that."

Pave does not share specific identifiable data like "John Doe got paid $X at EmployerCo".

Pave only shares aggregations like "people in San Francisco, with the title Senior Software Engineer, at companies between 100 and 500 employees, typically get paid $X at the 50th percentile, $Y at the 75th, and $Z at the 90th".

From Pave's website, https://www.pave.com/products/compensation-benchmarking-data:

> Benchmarking can never be traced back to an individual or employee.

I am not aware of any of these things having changed at any point.

Re: Learnings of a CEO: Matt Schulman, Pave, on Hiring

#32
post #3

Quoted post unavailable.

The idea of slope vs y-intercept as applied to people/hiring is not some random unknown made-up theory; it's quite commonly discussed/repeated among founders, VCs, etc. I think it may've originated with John Ousterhout.

https://twitter.com/search?q=slope%20y-intercept

Re: Learnings of a CEO: Matt Schulman, Pave, on Hiring

#34

Sometimes I daydream about starting a product company and my thinking goes like this: Do you have a decent idea that solves a real problem? - yes, check. Do you have respect for the iterations and learning required to find product market fit? - yes, check. Do you have years of relevant engineering and product experience and can you build and execute on stuff? - yes, check. But then my thoughts turn to what seems to a…

Hey, at least you're self-aware. :)

I think most of us programmer types struggle along similar lines; I can exert myself for short bursts to tick the extravert boxes you mentioned but it is tragically unsustainable.

Re: Learnings of a CEO: Matt Schulman, Pave, on Hiring

#35
> We paid them a fair market rate, and as mentioned, we were flexible on working hours. One contractor worked their day job until 5:00pm and then on Pave from 6:00pm-2:00am, for example.

Can anyone find anything positive about this arraignment? I can't. It can only work at all for very short term, and even then the likelihood of avoidable tech debt due to poor decision making at the end of a 16-hour work day is very high.

Post reply on HN