This article doesn't actually have much interesting content. It's pretty typical high-level boilerplate, to my eyes.
I'd be more interested in the actual content of the interviews. Instead of simply writing "three hours of technical interviews and one or more of other" it would have been helpful to see what the technical interviews might consist of.
For example, after reading this I have no idea if Strava's technical interviews are "implement X on the whiteboard", where X is something out of a CS textbook, or if there is any actual engineering content to them, or a mix of both.
I'd be more interested in the actual content of the interviews. Instead of simply writing "three hours of technical interviews and one or more of other" it would have been helpful to see what the technical interviews might consist of.
For example, after reading this I have no idea if Strava's technical interviews are "implement X on the whiteboard", where X is something out of a CS textbook, or if there is any actual engineering content to them, or a mix of both.