Twilio Technical Support Engineer interview questions

Interview process was with a technical support engineers, team lead, managers. There can be 3 to 4 separate interviews. Before getting through to the interview process, you must complete a take home test. Once you pass the take home test, the interview rounds begin.

Ghosted after a poor interview with a guy from Medellín. Now there are several tasks to complete as a filter. Feels excessive and unfair. The call itself was underwhelming—rushed, distracted, and over before it really began. No chemistry, no clarity on the role, just a vague overview and a promise to "review and be in touch." That was weeks ago. Since then, silence. No rejection, no feedback, no response to follow-ups. Just the hollow echo of an unanswered inbox. Then came the tasks. Not one, but several. Designed, apparently, to "demonstrate capability" and "show commitment." A filter, they said. But a filter for what? A role that may or may not exist? A process that may or may not continue? There's no transparency, no timeline, no indication that anyone is actually reviewing the work being submitted. It's a one-way street. Effort flows out, nothing flows back. And yet, the tasks keep coming. Each one more elaborate than the last. Each one demanding hours of unpaid labor under the guise of "assessment." Meanwhile, the silence from Medellín persists. No check-ins, no updates, no acknowledgment. This isn't hiring. It's extraction. Free labor disguised as opportunity. Hope weaponized against desperation. And the worst part? You know it's happening, but you do the work anyway—because what if this one is real? What if this time they actually follow through? But they never do. The ghosting says everything. The tasks say the rest. It's not a filter. It's a firewall. And you're on the wrong side of it