Solicité el puesto a través de un captador. Acudí a una entrevista en IXL Learning en jun 2017
Entrevista
I took an hour and a half tech test. Then I had another tech screening. Then I had another tech screening. All this before ever being able to talk to anyone at the office where I would be working to see if the job would be a "fit" for me. And then most of that interview also involved tech screening. I really feel I wasted a lot of time, because it wasn't a fit, and I would have liked the opportunity to learn that earlier.
Envié una solicitud electrónica. El proceso duró 4 semanas. Acudí a una entrevista en IXL Learning (San Mateo, CA) en mar 2025
Entrevista
Standard flow of recruiter screen -> tech screen (video call with a real person) -> recruiter follow-up -> slate of on-site interviews.
The on-site involved two technical interviews, a lunch casual chat with a couple of engineers, and an interview with the CTO. All of the technical interviews were standard DS&A and coding, none of them were domain-specific for the role I was applying for. I was rejected after the onsite.
Everyone was very friendly and kind throughout the process. The only odd thing was that my recruiter had a strong preference for calling me instead of emailing, and called me to let me know I'd been rejected as well. I'm guessing this was a cultural difference, and she thought it was kinder not to reject someone impersonally over text? But I would have much preferred to communicate over email.
Envié una solicitud electrónica. El proceso duró 1 semana. Acudí a una entrevista en IXL Learning (Research Triangle Park, NC) en mar 2016
Entrevista
The whole process took 2 weeks. Applied to senior software engineer opportunity by seeing the opportunity online. Some one mailed me asking the available dates for the telephonic interview. The interview lasted for half an hour. Asked couple of algorithms in the telephonic interview. Asked to write a program in telephonic interview.
