Ignore the Requirements, Check the Proxies

Photo by Free To Use Sounds on Unsplash

This past week, I talked to 10 candidates for our first round of summer intern interviews. It was awesome to see the enthusiasm and energy in the applicants, as well as the range of people who applied. On the job listing, we stated that “experience is preferred, but not required”—so we got a lot of MBA students, young professionals, recent graduates… and, to my surprise, one rising sophomore.

This young man, let’s call him Carl, realized there was no downside to having a conversation about the role. Because if he got picked to have a conversation, he could pitch why, despite how young he is, he’s qualified for the role. And if he impressed (which he did), he could put himself in a position to land future roles or be referred to other opportunities. He would also make a connection in the venture industry that he wouldn’t otherwise have had. Having spoken to him, I can put a face to the name, and I have a positive impression.

Because we had such fantastic candidates, Carl didn’t move on to the next round. But, he stands out in my mind for having the chutzpah and confidence to put himself out there. At Spero, we are giving some serious consideration to having ongoing, in-term interns, and Carl will be on the very short list of people I’d call if that opportunity opens up.

This story connects to the broader issue of how requirements are written and what they actually mean. Most of the time, a requirement is a proxy for a skill that people want to see so you can be successful in the role.

For example, in a job description:

An MBA is a proxy for analytical skills, basic financial skills, modeling basics, and an ability to evaluate businesses.

Experience in a specific role/industry is a proxy for the ability to hit the ground running versus needing people to spend time explaining how the industry works.

Years of experience is a proxy for maturity, the ability to collaborate with people, and the ability to handle the kinds of decisions the role will require.

And when raising venture investment, $1M revenue is often a proxy for product-market fit. There may be other ways to show PMF without being at exactly $1M.

This is not to say that every prerequisite is a proxy, or that you should fudge the facts. If you’re 2 credits short of your MBA, don’t say you have an MBA — but don’t automatically assume you’ll be rejected, either.

In our summer intern posting, we didn’t specify a single hard requirement, not even a college degree. I believe the whole professional world is moving towards tours of duty, which don’t depend on credentials like that. One of the smartest product designers I know doesn’t have an undergraduate degree. He is awesome and has accomplished a lot at some of the very best tech companies in Silicon Valley.

Next time you see one of those proxies, if you feel you‘ve demonstrated what the proxy is asking for, don’t hesitate to apply. I‘m fairly confident that Carl will do something interesting with his life. He recognizes that he is the asset and despite his youth, he understands the concept of proxies. He took the chance to put himself out there, and in nearly every situation, that’s better than not applying.