Envié una solicitud electrónica. El proceso duró 3 semanas. Acudí a una entrevista en TrialPay (Palo Alto, CA) en feb 2017
Entrevista
It starts off with a Hackerrank test with very easy programming and multiple choice questions. Total 5 questions in my case.
After that I had a 30 mins call with a product manager. It was based on previous job experience and projects and why TrialPay, etc. I made it through this one.
The onsite interview followed. They said it will be around 3 and a half hours long. But after 2 hours of interviewing they said they're looking for someone more experienced and escorted me out. If you're going for this full stack interview make sure you're good at designing the system and the entire stack. There's no way around it. If you can't come up with a satisfactory model and explain it with your background in webapp development, it most probably won't work out. The designing round which I screwed up was followed by a programming round where they asked their favorite duplicate files in a directory question. I think I did well in that one but the damage was already done in the first hour.
I have mixed feelings about their way of interrupting the interview suddenly. But I appreciate the swiftness in the sense that you don't have to keep going if you're not doing well. Both parties save time in the end. But their selection process is flawed if this is happening more often. They probably need to do more rigorous phone interview or something before calling onsite.
Overall a neutral experience. Their recruiter is good and people are really nice. Just need to work on their initial selection process.
Preguntas de entrevista [1]
Pregunta 1
How would you design an incoming reference based aggregation system for TrialPay back end server so that info about the incoming traffic can be stored and used to improve the system?
Duplicate files in a directory. Files are very large, so can't read the whole file into the memory.