Ask HN: Any interest in learning how startups actually work?
I've been throwing around this idea of interviewing startups to learn how the actual systems and processes work behind the scenes. (ie, what do you use to handle billing and how does it tie into everything else? how about customer support?)
I put up the second interview today (http://www.resultsjunkies.com/blog/back-office-exposed-zippykid) and was hoping I could get some feedback from other HN readers.
Is this interesting? Any areas you want me to dive particularly deep on?
(
18 comments
| 45 points
| on HN
)
What's interesting? Oh, where to start, where to start. Dashboards. Metrics. Customer service processes. Architectural decisions. Rationales and priorities, most particularly "We intentionally avoid doing X, because..."
This is a specific system design question, but I'd also like to hear about choosing between job queues (e.g., Beanstalk) and batch systems (e.g., Hadoop) for soft real-time data processing.
Interesting startups to interview:
- FlightCaster and BackType (lots of data, users get product for free, discuss process of finding and selling to customers interested in associated data; both also deal with real-time data)
- Shopify (supporting users that use your product to sell their product)
- banksimple (regulated industry)
- DuckDuckGo (building a system to compete with a wealthy behemoth)
- WakeMate and Square (designing and manufacturing hardware)
Will definitely check back every once in a while!
The only thing I'd say is, get interesting startups -- and the rest will take care of itself.