Treat achievements as questions to explore
A competition result or founder background can reveal useful experience, but it does not answer every hiring question. Ask what the person actually did, which decisions they owned and how their contribution relates to your role. Separate an impressive achievement from evidence about the work you need now.
Explore the work behind a competition result
Ask about the problems solved, preparation, collaboration and how the candidate approached uncertainty. Then assess the responsibilities your job requires, such as maintaining a product, communicating with customers or working across a team. Do not assume that a competition result proves or disproves those capabilities.
Understand why a founder wants to join
A former founder may bring experience of ownership, product decisions and uncertainty. Explore which responsibilities they want next and how they will work within another founder’s direction. Fundraising is context for the story, not a measure of engineering skill or a substitute for understanding the product they built.
Keep the evidence tied to the role
Use consistent criteria across candidates with different backgrounds. A shipped feature, research experiment, open-source contribution or difficult operational decision can each provide relevant evidence. Ask about constraints, other people’s contributions and what the candidate would change. Avoid making a famous institution or employer an unstated requirement.
Protect confidential information
Candidates should be able to discuss decisions without sharing information they are not permitted to disclose. Offer room to generalize customer details, code or unpublished research. Judge the explanation and relevant reasoning rather than rewarding access to another company’s private material.
Keep historical examples in context
Before Corellia Talent, Josh placed ICPC finalists into a Series A startup in New York and a former founder who had raised $4.5 million into a seed-stage New York startup. Those are personal career placements, not Corellia client endorsements. They illustrate different backgrounds worth exploring, not a claim that either background guarantees success.
Check the compensation assumptions.
Our salary guide separates advertised pay, disclosed equity and bonus from planning estimates. Compare the role, location and company context before using a figure in a decision.
Explore the evidence and compensation plannerQuestions founders ask
Should we hire only competition finalists?
No. Define the evidence relevant to your role and assess candidates against it. Competition results can be useful context, but they do not cover every responsibility.
Does founder experience prove someone can lead engineers?
Not by itself. Explore actual people-management, technical and delivery responsibilities rather than relying on the founder title.
Can open-source work be useful evidence?
Yes, where it relates to the role. Ask about the person’s contribution, decisions and collaboration rather than using popularity alone as a proxy.
Should we ask for private code from a previous employer?
No. Use examples the candidate is allowed to share and a relevant discussion of their decisions.
Do these placements belong to Corellia Talent?
No. The historical examples describe Josh Smith’s personal recruitment experience before founding Corellia Talent.
How do we avoid inconsistent assessment?
Agree role-related criteria before interviews and compare evidence against the same responsibilities. Make room for different backgrounds to demonstrate relevant capability.