Senior Customer Support Engineer

Fyxer · Londonsenior

En corto

▸Ingeniero de soporte técnico senior que resuelve problemas técnicos complejos sin depender de ingeniería.
▸Trabajas con productos propios, usas logs, SQL y API para diagnosticar y resolver incidencias rápidamente.
▸Destaca por reducir tickets a ingeniería mediante análisis profundo, buenas escalaciones y automatización.

No se requiere inglés, pero la comunicación con clientes puede ser en inglés.

En ~1 minuto te damos: quién te entrevista, las preguntas probables con respuestas desde tu CV, y tu CV adaptado a esta vacante. Gratis, sin tarjeta.

🎧¿Llegás a la entrevista? Llevá el copiloto. Nuestra extensión escucha la entrevista en vivo y te muestra anclas de 3-4 palabras desde tu CV y tu preparación — mirás, conectás, hablás. Gratis. Ver la extensión →

¿Qué piden?

✓3+ años en soporte técnico en SaaS o empresas cloud
✓Fluidez en APIs: lectura de documentos, comprensión de errores como 401 o 500
✓SQL avanzado: escribir joins sin ayuda en esquemas desconocidos
✓Trabajar con logs para rastrear errores entre servicios
✓Comunicación escrita clara, especialmente con clientes insatisfechos
✓Experiencia con herramientas como Zendesk, Intercom, Jira, Linear

¿No cumplís todo? Es lo normal — tu dossier gratis te dice qué gaps tenés y cómo cubrirlos en la entrevista.

LinearZendeskIntercomJiraCursorSQLAPIslogs de producciónParahelpAI (herramientas comunes en el

¿A quién escribirle en Fyxer?

Tu dossier gratis identifica a las personas que te entrevistarían — con su background, qué valoran y cómo escribirles para destacar antes de aplicar.

About Fyxer Since launching in May 2024 we've grown to $30 million in ARR. Fyxer is building an AI executive assistant that handles emails, scheduling and follow-up, freeing people in client-facing roles to focus on their customers. What You'll Be Doing Own the hardest technical tickets in the business end to end, including the customer conversation, from first report through to resolution Dogfood Fyxer’s own products, give feedback, and influence our roadmap Establish blast radius before escalating, because one customer reporting something is a ticket and forty-seven accounts in the same broken state is an incident Call bug, incident or user error correctly and quickly, and declare it when it's an incident Write escalations Engineering can act on without a single follow-up question, and stay on them until they land Spot patterns across Linear and the queue, raising a tracker before the fifth report of something becomes the tenth Reduce the need for your own role through runbooks, saved queries, Parahelp knowledge, and hands-on upskilling of our senior agents Here's the honest version of why this role exists. In one recent three-month window we escalated 47 tickets to Engineering and two of them were resolved. Engineering is capacity-constrained, and a third of what we sent them was correctly deprioritised. So this isn't a role that escalates better, it's one that resolves. You'll be backed by strong Customer Success and Product Engineering teams, and given read-only access to our codebase through Cursor, to our data through our internal tooling, and to our production logs to do it. What Success Looks Like You resolve a growing share of technical escalations without Engineering ever being involved Your escalations are complete, so Engineer can act on them quickly You use AI and you catch it when it's wrong, before it reaches a customer You hold a customer's confidence while you investigate, rather than handing them back to someone else Our senior agents are visibly more capable six months in than they are today, because of you You're the person the team wants on the ticket because they trust your judgement. What You Bring 3+ years in a technical support role within a SaaS or cloud-based company API fluency: you can read an API reference, reason about authentication, and say what a 401 rather than a 500 tells you about where the fault sits SQL you write yourself: given an unfamiliar schema you work out how the tables relate and write the join unaided Comfortable in logs, following a request across services and working backwards from an error Strong written communication, particularly to a customer who is unhappy Experience with customer support tools such as Zendesk, Intercom, Jira, Linear, others Startup-ready: adaptable, fast-moving, and hands-on We're not asking for production engineering experience or a computer science degree. We care what you can do, not how you got there. Benefits include: on-site gym, private medical, pension and lunch provided everyday The Hiring Process Submit your CV (no need for a cover letter) We'll review it An initial call with someone from the hiring team to review your experience and motivation for joining (30 mins) A call with our Head of Customer Support on your experience and how you think technically (30 minutes) A live technical exercise (60 minutes) Meet more of the team (30 minutes) For the exercise we'll give you access to a small example application, a database, an API and its logs, a couple of days ahead, along with three customer tickets. You don't need to solve anything in advance, and you're welcome to use whatever AI tooling you normally would, because that's how the job actually works. We'll be paying attention to how you check its answers. Our Culture Our culture is intentional.

No apliques sin prepararte

Investigamos quién te entrevista, adaptamos tu CV y te ensayamos en vivo — gratis la primera.