by Patrick Newman (patorick002@gmail.com). Originally written in 2017, revised 2023-November.
Prior to joining my first big tech company in 2017, I spent 11 years working at startups. I fully expected to spend my entire career in startups, and I interviewed at several that I didn't wind up joining. These companies tended to be ones that had attracted venture funding, but weren't yet household names, and when interviewing I spent a lot of time assessing how likely they were to survive and thrive. Over time I developed a set of questions to ask to help with that task. In essence, what I wanted to learn was whether the company has something (production, roadmap, vision) that a customer base is willing to pay for, and whether they have enough assets (technology, talent, revenue, cash) to reach their potential. Of course, I also wanted to get a sense of whether I was the right person to help move the business forward. I don't think there are any precise 'correct' answers for these questions, though there are probably some wrong ones. Different companies at different stages of maturity will have these figured out to varying degrees, so there is some judgement involved with assessing the answers. I don't think I ever asked all of these questions in a single interview, that would have been overkill. I tended to focus a little more on one area or another depending on what I was observing.
I have used questions from this list in interviews at multiple startups over the years, though not as much recently. The startup I interviewed with that went on to get the biggest was Palantir. The two that I was the most sure about were Auth0 and Narvar. The one I incorrectly disregarded was Chewy. The one I correctly declined was OnLive. Palantir has since IPO'ed, Auth0 was acquired by Okta, Chewy was acquired and later IPO'ed, and Narvar is still in business. OnLive dramatically went out business a few years ago. Ironically, I didn't wind up working at any of these places, for various reasons.
I wrote these questions from the perspective of an engineering leader, but many of them should be reusable accross different roles.
PRODUCT AND CUSTOMERS
TECHNOLOGY
ENGINERING PROCESS
CASH AND FINANCES
LEADERSHIP
ORGANIZATION
MY ROLE
EQUITY AND LIQUIDITY