computer science

Dalton Caldwell and Michael Seibel describe how technology and startups shifted from outsider pursuits to high-status, structured career paths that attract conformists. They argue that some people enter startups to gain investor approval or status rather than to build and solve customer problems. They identify signs of builder-minded founders, including wanting to make a small amount of funding go far, welcoming difficult challenges, and betting on their ability to learn. Their advice is to seek out like-minded nonconformists, consider joining an early-stage startup, and avoid playing status games.

The founders of Squire, Edlyft, and Promise explain how personal experience helped them identify problems worth solving. Squire set out to improve the barbershop experience with business management and point-of-sale software, while Edlyft aimed to support students who lacked encouragement and resources to pursue computer science. The speakers describe reflection, mentorship, early customer conversations, and startup structure as ways to manage the risks of building a company. They also discuss widening access to technology entrepreneurship and supporting more Black founders.

Ammon Bartram explains why hiring interviews are noisy: companies define engineering skill differently, and short interview problems only imperfectly predict success on long, complex work. He recommends deciding which skills matter for a company, using consistent evaluation, and refining the process against results. Triplebyte separates its assessment into programming productivity, computer science knowledge, debugging, and system design, while favoring relatively easy problems that produce fewer false negatives. He also discusses candidate preparation, résumé screening, trial employment, interview fairness, and ways to reduce stress and bias.