About this role
Twilio provides the APIs that let companies build messaging, voice and email into their products, and this team is the technical escalation point for customers using them. You would work with customer developers and architects on problems that are genuinely hard to reproduce, troubleshoot server side and client side JavaScript, dig into network and telephony issues, and file the reproducible bugs that reach Twilio's own product and engineering teams. It is one of the few genuinely remote roles on today's board, and at 2+ years it is one of the lowest bars. Two things to weigh before applying: it is shift work, and remote here is restricted to five states. This is support engineering rather than product development, so choose it because you like debugging other people's systems, not as a side door into an SDE role.
Who this is for
Asks for 2+ years of technical support or similar relevant experience. Full stack JavaScript support experience with the ability to troubleshoot server side code (Node.js, C#, Java or Python are named as a bonus) and client side JavaScript, with React.js a bonus. Also wanted: object oriented programming concepts, basic SQL and query writing, a good understanding of APIs, HTTP and RESTful services, network troubleshooting including TCP and UDP with the basics of SSL and TLS, and experience troubleshooting SIP, VoIP and IP telephony. High competency communicating complex technical issues to technical and non technical audiences by phone and email is required, not optional.
Desired: serverless (Lambda) experience, native and mobile application expertise, contact centre product troubleshooting, and cloud solution troubleshooting.
Day to day: address customer issues and feed customer input back to product and engineering, work with customer and partner developers on complex problems, resolve quality of service issues, collaborate over Slack and file JIRAs for reproducible bugs, and support customers on holidays.
Location and shift reality, and read this part carefully: the posting states the role is remote and based in India, restricted to Karnataka, Maharashtra, Tamil Nadu, Telangana and Delhi. Twilio describes itself as remote first but says you may be asked to attend in person on an ad hoc basis. The role reports to a manager based in the Bengaluru office. Shift timings listed for APJ and EMEA coverage are 6:30 AM to 3:30 PM, 12:00 PM to 9:00 PM, 1 PM to 10 PM and 1:30 PM to 10:30 PM IST.
Twilio states it uses AI to make hiring more efficient but that every hiring decision is made by a person. No interview stage list is published.
Desired: serverless (Lambda) experience, native and mobile application expertise, contact centre product troubleshooting, and cloud solution troubleshooting.
Day to day: address customer issues and feed customer input back to product and engineering, work with customer and partner developers on complex problems, resolve quality of service issues, collaborate over Slack and file JIRAs for reproducible bugs, and support customers on holidays.
Location and shift reality, and read this part carefully: the posting states the role is remote and based in India, restricted to Karnataka, Maharashtra, Tamil Nadu, Telangana and Delhi. Twilio describes itself as remote first but says you may be asked to attend in person on an ad hoc basis. The role reports to a manager based in the Bengaluru office. Shift timings listed for APJ and EMEA coverage are 6:30 AM to 3:30 PM, 12:00 PM to 9:00 PM, 1 PM to 10 PM and 1:30 PM to 10:30 PM IST.
Twilio states it uses AI to make hiring more efficient but that every hiring decision is made by a person. No interview stage list is published.
Apply on company site
Opens job-boards.greenhouse.io, the employer's own application page. Applying is always free.