Thanks Omar - waiting on hearing your news too.

Thanks Josh.

Thanks Jan.

We're upfront about the probationary period with all candidates, they start knowing they'll receive a lot of feedback in the first few weeks, they'll get an opportunity to see if it's a fit from their side and also from the team's side.

Perhaps you're firing so many people up front because your policies only attract weird people willing to put up with them?

I think getting hiring right is a process, we were certainly a lot more hit & miss right after demo day, than we are now.

May I suggest the one week trial?

Weighing in from the "Recruiting" Startup industry myself, check out https://grouptalent.com/ (which i have nothing to do with) if you are in that hiring mentality, that way everyone knows exactly what is going on and there is a better reaction set all around.

Agreed, it's a key advantage for YC companies.

This is a critical part of our high availability infrastructure.

Just curious, what's sendhub's architecture? How many nodes? How many heterogeneous nodes?

We are all SOA, and with ShipBuilder the types of nodes are simplified to: shipbuilder nodes running any kind of desired app servers, databases, load-balancers, and cache servers.

We followed up directly on this and it seems to be working fine now.

Really appreciate the phone call, talking to potential customers is a big thing a lot of startups never do, its just great customer service.

This is false.

At cuil we were told by mgmt of the launch date and our very talented PR team kicked into gear and generated a ton of buzz via a nationwide press tour.

Despite popular opinion, the ops team kept the site up during the massive traffic surge. A combination of poor mgmt, initial deference to user testing, last minute commits and a nasty indexing bug were the reasons the relevance sucked on day 1.

It wasn't just Anna, there were many former archive staffers at cuil. I suspect that's how the data ended up being transferred.