Twilio logo

Twilio Technical Support Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 46 interview experiences · FREE TO READ

3.8 Rounds average
Average Typical difficulty
43.5% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Twilio.

Showing 3 of 46
Twilio logo
Twilio

Technical Support Engineer

Engineering · nearly a year ago

Entry Average Negative experience Decline offer 2 rounds
Interview process
Recruiter call Take home Background check
Interview formats
Technical Other

I had a poor interview with someone from Medellín. It felt rushed and I didn't get a clear understanding of the role. After that, I was ghosted for weeks. Then, I was asked to complete several unpaid tasks as a filter. There's no transparency on whether these tasks are being reviewed or if the process will even continue. It feels like free labor disguised as an opportunity, with no feedback or follow-up.

Confirmed questions2 questions
  • Can you tell me about your experience?
  • Please complete several unpaid tasks to show your capability and commitment.
Twilio logo
Twilio

Technical Support Engineer

Engineering · a year ago

Mid Average Negative experience No offer 4 rounds
Interview process
Technical screen Recruiter call Technical screen Background check Offer
Interview formats
Technical Behavioral Coding

I went through a pretty long interview process for a Technical Support Engineer role at Twilio, taking almost three weeks with tests and interviews, and honestly, I'm pretty let down. First up was a HackerRank Flex Test, which wasn't a coding test but more about how I'd handle support emails. It had a question where I had to email a solution to a customer's problem and another where I had to use Twilio's tools, read docs, and make a workflow. Seemed relevant, not super hard though. Then, I had a phone interview with a recruiter. It was the usual chat about my background, the job, and why Twilio. Got good vibes from that. After that, there were technical interviews focusing on Node.js, React.js, and networking stuff. These weren't too tough, fit my skills well. Then came a bunch of behavioral interviews where I used the STAR method to talk about my past experiences. I felt pretty good about how those went. The issue really started in the last interview with a senior manager. The vibe changed after they asked where I was based, which felt random. Then, the manager focused on my past salary, which I found inappropriate since I said I was uncomfortable sharing it and it's not really how things are done now. It got awkward and unprofessional, totally messing up the good flow before that. After three weeks of this, I got rejected with a flimsy reason about my behavioral answers not being good enough, even though no one mentioned that before. It felt like the real reason was something else entirely. For a company that talks about diversity and inclusion, this experience felt the opposite. If you're thinking about Twilio, be ready for a long haul that might not be worth it, especially if they judge you on weird stuff.

Confirmed questions5 questions
  • Can you review a customer's technical issue and draft an email response with a solution?
  • Using Twilio's documentation and tools, how would you build a workflow to address a customer's needs?
  • What are your experiences with Node.js, React.js, and common network issues?
Twilio logo
Twilio

Technical Support Engineer

Engineering

Entry Easy Positive experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral

Applied a few months ago and then got an email to set up a phone interview. The first call was with a recruiter who asked me some general background questions. The recruiter mentioned they needed to check if they could hire me in my state before moving my application to the hiring manager. After I followed up on the state issue a couple weeks later, the recruiter responded that they unfortunately couldn't hire in my state. I'd never encountered that before, but I guess it means they didn't have the proper employment/payroll setup there. Because of this, my application wasn't advanced.

Confirmed questions1 question
  • Could you tell me about your previous work experiences?

Twilio Technical Support Engineer Interview Questions

Quoted word for word from Twilio interview reports.

What are Web APIs and network protocols like TCP and UDP, and how are they used?

Read reports

I've just started my home business, how can I forward my Twilio number to my cell phone, as I'm not a developer?

Read reports

I need a way for someone to answer their phone and receive a message, how can I achieve this?

Read reports

Could you explain what an API is to someone without a technical background?

Read report

Which do you believe is more critical: technical support or customer service?

Read report

Using Twilio's documentation and tools, how would you build a workflow to address a customer's needs?

Read report

Can you review a customer's technical issue and draft an email response with a solution?

Read report

What are your experiences with Node.js, React.js, and common network issues?

Read report

Formats, difficulty and experience

Across all 46 Twilio interview reports.

Interview formats

Behavioral 39.6%
Technical 39.6%
Other 7.9%
Coding 5.9%
Presentation 5%

Interview difficulty

Easy 15.2%
Average 76.1%
Difficult 8.7%

Candidate experience

Positive 43.5%
Negative 43.5%
Neutral 13%