We're a team of 17 dedicated reporters and engineers (and counting), growing the future of journalism from a sunny perch in the Financial District of San Francisco.
We founded The Information in late 2013 with a simple idea: write deeply-reported articles about the technology industry that you won't find elsewhere.
Nearly two years later, we've moved markets, gotten the early scoop on billions of dollars of acquisitions and told you what's happening deep inside companies like Apple, Facebook and Google. Our stories have been followed by the Wall Street Journal, the New York Times, Bloomberg and other major outlets thousands of times. How we compete is simple. We recruit the best reporters, give them the freedom to write about important topics and tell them not to worry about the small stuff.
Because our articles are deeply reported and written for an engaged audience, they have real impact. Our coverage of the secret terms of VC deals—and what they mean for employees—has reshaped how some investors and companies approach those deals. And our Future List project about the lack of diversity among tech investors has been cited by more than a hundred publications.
Quality stories breed quality subscribers. As our subscriber community grows, we're investing aggressively in our team and reporting. We believe this formula is far more scalable than relying on traffic or conferences, and it's totally—100 percent—aligned with our readers.
Unlike most other news sites, we don’t have venture capital or corporate owners, but like other publications, we do sometimes do business deals with companies that we cover.
For engineering staff we use a three-interview process. The first interview is typically a video conference; the next two are in-person.
In the first interview we'll ask you about your background, your interests, what you're excited to get out of your next role; questions that help us assess whether you'd be a good fit for our team. We'll also give you a chance to ask us about life here at The Information, our work environment, and company culture so you can decide whether we sound like a good fit for you! This interview typically takes between 30 and 45 minutes.
If that goes well, we'll invite you to send a code sample to us. We have a set code challenge you can do, or you can submit an open-source project or even a code challenge you did for another company. Ideally what you send us should be complete, executable, and representative of your work. We'll then review the code, and if we like what we see we'll invite you to a technical interview where you'll answer questions about what you wrote.
The goal of the technical interview is to assess how effectively you'd be able to function as our colleague in our deparment. We'll ask you to defend architectural and infrastructural decisions you made; identify edge cases; and explain how to identify and resolve bugs. If your code implements a data structure or algorithm, we'll ask questions about it. We don't believe in interview by ambush, we're never confrontational, and we don't use a whiteboard. This interview can run anywhere from 45 to 90 minutes.
The last part of the process consists in meetings with our editor-in-chief as well as other members of our staff.