fault-tolerant

You're misinterpreting 'fail fast' - it doesn't mean 'entire system should fail catastrophically at slightest problem' or 'systems should not be fault-tolerant'.

You know how to build highly scalable, robust, and fault-tolerant services that support our unique rate-of-growth requirements.

Erlang and OTP do provide you with the tools to relatively easily make fault-tolerant, scalable software.

What tools do you use when you must write highly-fault-tolerant, scalable software?

I can trust to DO only fault-tolerant services when to Linode I can trust any kind of service to run.

Web application developer with experience building large scalable and fault-tolerant applications.

This person will be responsible for designing fault-tolerant mechanisms for keeping distributed systems healthy, and developing proactive monitoring back to DevOps and the development teams.

In many ways these were more important than raw throughput in that if it could not handle the massive concurrency and build truly fault-tolerant systems then it wasn't interesting.

If you have really serious performance needs for your robust distributed (or simply fault-tolerant) system, do some perf tests, write the performance-critical parts in C or C++ or whatever, then use an Erlang Port Driver (or maybe some IPC mechanism of some sort) to connect them to the more difficult or logically tricky bits that are written in Erlang.