Learnings of a CEO: Matt Schulman, Pave, on Hiring
ycombinator.com
ycombinator.com
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 actually matter (re-enforced by articles like this):
Are you an extravert who wants to spend all their time talking to investors and raising money? - no, fail.
Are you an extravert who wants to spend the other half of all their time interviewing and hiring new employees? - no, fail.
Have you ever actually met an extravert who you would trust enough to delegate these two critical responsibilities above? - no, fail.
Running or building a company is about allocating capital, hiring good people and being able to manage them effectively, and being comfortable with delegating tasks to competent experts instead of trying to micromanage everything. That's how you get scale.
If you don't have those skills, nothing wrong with that, most people don't. Instead you find an existing company that has that, and you join them and offer them the skills that you do have.
One thing you quickly realize when you start a company is just how chaotic it is in ways you never expected from legal aspects, financial aspects, coordinating things internally within your company and externally with third party vendors and your customers, and you begin to feel the pressure of having competition that is constantly trying to shut you down, especially as you get bigger and bigger. It's very fierce and you are reminded that every single dollar you make is a dollar that someone else is fighting for.
If what you want to do is focus mostly on a product and employ your particular area of expertise then do not start a company, join one. Finally this extravert vs introvert stuff is nonsense, don't use it as an excuse or let it deter you. Plenty of introverts are incredible leaders that have managed to run some of the most wildly successful companies ever known. Look at some interviews with tech CEOs before they became successful; they are some of the most socially awkward and uncomfortable looking people you can imagine who seem to really hate giving talks, heck check out the infamous Zuckerberg 60 Minutes interview or other interviews from around 2004. Early Bill Gates interviews are only slightly less awkward as are interviews with Google's Larry Page.
Building a successful company is about far more than just building a product. If you're one of the lucky few that find product-market fit, you still need to scale the company and build up an organization that execute on the opportunity that exists. That is mostly a people and leadership problem, and not a technical one.
Not all companies have to be big, and maybe you don't even need to create a company to create something helpful / beautiful / profitable / whatever floats your boat.
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.
The only org that did that said I beat everyone else and they're interested in having me (currently in progress in fact). Make of it what you will; I don't know what to think. They all want innovative problem solvers with deep knowledge but don't ask the interview questions that would show that up. It makes no sense.
> They all want innovative problem solvers with deep knowledge but don't ask the interview questions that would show that up.
The hiring process is a quintessentially human process so you're going to experience many different types of people.
Keep focused on enthusiastic service. Focus on showing how you can help the company out with their mission. Research the company ahead of time and build a case that you are ready to communicate to the hiring team. Answer their questions honestly and directly but if they don't ask great questions, no big deal, just proactively fill that gap with good reasons why they should bring you on.
> Research the company ahead of time and build a case that you are ready to communicate to the hiring team
Yeah, to do that you need to know the companies' requirements. As an outsider you can't know them.
> proactively fill that gap with good reasons why they should bring you on.
I've even offered to work free for companies to start with. I got not one taker in the past few years. I offered to work paid - I go through the interview process where I don't asked get asked tech questions, just the touchy-feely stuff which I can't stand out in (who can?).
Point is, interviewing could be made a lot simpler and more effective I think; per https://news.ycombinator.com/item?id=33334492 I don't think you need to spend "half of all their time interviewing and hiring new employees". You should be able to filter far more efficiently. That's my point, not whingeing about my particular case.
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 they have expanded since.
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 wasn't comfortable with this so I bowed out. I'm not sure how much control employees have to prevent this sharing to Pave, because 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."
They may have changed their data policy, like I mentioned I haven't talked to them since last year.
> 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.
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.
Their data can really help a lot of individuals negotiate salaries.