Technical Support Engineer

<h2><strong>Meet Siena</strong></h2><p style="min-height:1.5em">Siena is the first intelligence layer for customer experience. We're creating an operating system of AI agents that learn, remember, and act across every customer touchpoint—from support conversations to shopping experiences to voice and social media interactions.</p><p style="min-height:1.5em">Siena doesn't just automate support; it powers shopping agents, builds persistent customer memory, generates actionable business insights, and creates empathetic interactions that feel human. </p><p style="min-height:1.5em">We're transforming how businesses understand and connect with their customers, turning every interaction into intelligence that makes the next one better.</p><h2></h2><h2><strong>The team</strong></h2><p style="min-height:1.5em">We're a small, distributed team that punches way above our weight. Every person here has outsized impact because we've built leverage into everything we do. This philosophy makes us faster and, frankly, more fun to work with.</p><p style="min-height:1.5em">If you're excited about building something that doesn't exist yet, keep reading. We're building agents that don't just respond to customers—they remember them, learn from every interaction, and connect experiences across channels.</p><h1><strong>About the Role</strong></h1><p style="min-height:1.5em">You own the space between our customers and Engineering. As Technical Support Engineer, you take Tier 2+ escalations end-to-end: diagnose, resolve, close. You pull in engineers only when there’s a genuine product bug or infrastructure issue underneath — not as a default path.</p><p style="min-height:1.5em"></p><p style="min-height:1.5em">You’ll work directly with the e-commerce brands running Siena’s AI agents across complex integration environments. You’ll sit within the Engineering org, report to our Support Manager, and collaborate with Engineering on the issues that actually require them.</p><p style="min-height:1.5em"></p><p style="min-height:1.5em">What separates this from a senior IC support hire is what happens after the ticket closes. Every Tier 2+ resolution carries two follow-up questions you own: </p><p style="min-height:1.5em"><em>1) Does this pattern belong back in Tier 1? </em></p><p style="min-height:1.5em"><em>2) How do you build the system so the next instance never escalates, or reaches you faster? </em></p><p style="min-height:1.5em">Runbooks, auto-routing, observability access for the Support team — that’s the leverage this role is built to create.</p><p style="min-height:1.5em">When the Tier 2+ queue is quiet, you work Tier 1 tickets alongside the Support team, staying close to the volume that tells you what to systematize next.</p><p style="min-height:1.5em"></p><p style="min-height:1.5em"><strong>The bar: diagnose it, resolve it, make the system better so it happens less often.</strong></p><p style="min-height:1.5em"></p><h1><strong>What You’ll Do</strong></h1><h2><strong>Own technical resolution end-to-end</strong></h2><ul style="min-height:1.5em"><li><p style="min-height:1.5em">You take full ownership of Tier 2+ escalations. You diagnose and resolve without pulling in engineers unless there’s an actual product bug or infrastructure issue underneath.</p></li><li><p style="min-height:1.5em">You debug API integrations independently: auth failures, webhook issues, data sync gaps, rate limiting, intermittent failures, provider-specific limitations.</p></li><li><p style="min-height:1.5em">You diagnose and resolve customer-side JavaScript issues: widget behavior, event tracking, data passing, script conflicts, cross-browser bugs.</p></li><li><p style="min-height:1.5em">You triage AI and chatbot behavior — wrong answers, workflow misconfiguration, hallucination patterns, Custom Action misfires — tracing whether the issue is prompt, KB, workflow config, or model.</p></li><li><p style="min-height:1.5em">You run diagnostic SQL on data discrepancies, missing records, and report mismatches.</p></li><li><p style="min-height:1.5em">When the escalation queue is clear, you work Tier 1 tickets alongside the Support team, staying close to the patterns that tell you what to systematize next.</p></li></ul><p style="min-height:1.5em"></p><h2><strong>Build leverage, not just resolution</strong></h2><ul style="min-height:1.5em"><li><p style="min-height:1.5em">After every Tier 2+ resolution, you ask: can this move back to Tier 1? If a pattern can be handled by the Support team with a runbook or training, you move it back.</p></li><li><p style="min-height:1.5em">You build and maintain internal documentation for common failure modes, turning one-off resolutions into team-wide capability.</p></li><li><p style="min-height:1.5em">You scope and drive systemic improvements: auto-routing, observability access, tools that turn recurring manual tasks into repeatable systems.</p></li><li><p style="min-height:1.5em">You surface patterns, recurring bugs, and product gaps to Engineering systematically — not ad hoc.</p></li></ul><p style="min-height:1.5em"></p><h2><strong>Own the customer-facing experience</strong></h2><ul style="min-height:1.5em"><li><p style="min-height:1.5em">You own complex technical issues directly with customers. You’re the technical face of Siena when depth is required.</p></li><li><p style="min-height:1.5em">You translate complex technical problems into clear explanations for customers and non-technical teammates.</p></li><li><p style="min-height:1.5em">You manage expectations confidently through multi-step debugging processes.</p></li><li><p style="min-height:1.5em">You escalate to Engineering only when an issue genuinely requires a code fix, infrastructure access, or schema migration.</p></li></ul><p style="min-height:1.5em"></p><h2><strong>Work at the edge of AI-native infrastructure</strong></h2><ul style="min-height:1.5em"><li><p style="min-height:1.5em">You support customers integrating with Siena’s AI agents across Shopify, Gorgias, Zendesk, Kustomer, Gladly, and custom environments.</p></li><li><p style="min-height:1.5em">You troubleshoot LLM-based agent behavior, integration edge cases, and platform failures.</p></li><li><p style="min-height:1.5em">You use AI tools actively in your diagnostic workflow. You’re not just supporting AI products — you’re fluent in them.</p></li></ul><p style="min-height:1.5em"></p><p style="min-height:1.5em"></p><h1><strong>Who You Are</strong></h1><h2><strong>Technical skills</strong></h2><ul style="min-height:1.5em"><li><p style="min-height:1.5em">You have 1+ year of technical support at a SaaS company. You’ve owned hard technical threads end-to-end, from customer report to closed ticket, without handing the thread to engineering.</p></li><li><p style="min-height:1.5em">You debug REST APIs, webhooks, auth flows, JSON, and HTTP protocols. You find the break and distinguish customer-side cause from product cause.</p></li><li><p style="min-height:1.5em">You’re fluent in customer-side JavaScript: browser devtools, event handlers, script conflicts, timing issues. You’re comfortable using AI coding tools like Claude Code to navigate unfamiliar codebases quickly.</p></li><li><p style="min-height:1.5em">You write diagnostic SQL to validate data, trace ingestion paths, and answer your own data questions without waiting on a data team.</p></li><li><p style="min-height:1.5em">You’re comfortable with production systems: logs analysis, monitoring tools, system debugging.</p></li></ul><p style="min-height:1.5em"></p><h2><strong>AI/LLM expertise (preferred)</strong></h2><ul style="min-height:1.5em"><li><p style="min-height:1.5em">You have experience with LLMs, prompt engineering, or AI model integration.</p></li><li><p style="min-height:1.5em">You can triage AI agent behavior and distinguish a prompt/config issue from a model-level problem.</p></li><li><p style="min-height:1.5em">You’re familiar with how LLM-based systems fail: hallucinations, retrieval gaps, prompt sensitivity, workflow misconfiguration, Custom Action misfires.</p></li><li><p style="min-height:1.5em">You have experience with AI APIs (OpenAI, Anthropic, etc.).</p></li></ul><p style="min-height:1.5em"></p><h2><strong>Customer-facing skills</strong></h2><ul style="min-height:1.5em"><li><p style="min-height:1.5em">Your written and verbal English is strong. You explain complex technical issues to non-technical stakeholders without losing them.</p></li><li><p style="min-height:1.5em">You build trust quickly. Customers feel like their problem is in capable hands.</p></li><li><p style="min-height:1.5em">Empathy and urgency coexist naturally for you.</p></li><li><p style="min-height:1.5em">You work independently in a remote environment with strong async communication.</p></li></ul><p style="min-height:1.5em"></p><h2><strong>Built for startup pace</strong></h2><ul style="min-height:1.5em"><li><p style="min-height:1.5em">You’re comfortable in ambiguity. You create structure where there isn’t any.</p></li><li><p style="min-height:1.5em">The leverage mindset is already a habit: when you talk about past wins, you naturally mention what you did so the next instance wouldn’t escalate — not just how you fixed the ticket.</p></li><li><p style="min-height:1.5em">You’ve coached or trained non-technical teammates. Pairing sessions, documentation that got used, concrete evidence of being a multiplier.</p></li><li><p style="min-height:1.5em">You're available to cover North America timezones</p></li></ul><p style="min-height:1.5em"></p><p style="min-height:1.5em"></p><h1><strong>What Success Looks Like</strong></h1><h2><strong>90 days</strong></h2><ul style="min-height:1.5em"><li><p style="min-height:1.5em">Engineers are no longer pulled into support escalations. Tier 2+ resolution is yours by default.</p></li><li><p style="min-height:1.5em">Tier 2+ resolution time baseline is established and surfaced.</p></li><li><p style="min-height:1.5em">You’ve mapped the most common technical failure patterns across the customer base.</p></li><li><p style="min-height:1.5em">At least one Tier 2 pattern has moved back to Tier 1 with a runbook the Support team is actively using.</p></li><li><p style="min-height:1.5em">You’ve built a working partnership with the Support Manager and are co-prioritizing what to systematize next.</p></li></ul><p style="min-height:1.5em"></p><h2><strong>6 months</strong></h2><ul style="min-height:1.5em"><li><p style="min-height:1.5em">Resolution time is measurably improving from the 90-day baseline.</p></li><li><p style="min-height:1.5em">CSAT on technical issues is improving.</p></li><li><p style="min-height:1.5em">Engineering is fully protected from support interruptions.</p></li><li><p style="min-height:1.5em">The feedback loop to Engineering is running systematically — patterns, bugs, and product gaps surfaced before things break loudly.</p></li><li><p style="min-height:1.5em">The Support team is resolving more independently. Your internal documentation covers the most common failure modes.</p></li><li><p style="min-height:1.5em">You’ve shipped at least one systemic improvement project: auto-triage, observability access, or equivalent.</p></li></ul><p style="min-height:1.5em"></p><p style="min-height:1.5em"></p><h2><strong>Nice to Have</strong></h2><ul style="min-height:1.5em"><li><p style="min-height:1.5em">You’ve supported AI or LLM-based products before: hallucination patterns, prompt sensitivity, retrieval-grounded responses.</p></li><li><p style="min-height:1.5em">You have a background in e-commerce or DTC and understand the merchant world: catalog, orders, fulfillment, returns.</p></li><li><p style="min-height:1.5em">You’re familiar with modern observability tooling: Honeycomb, Grafana, Splunk, Sentry, Kibana, or equivalents.</p></li><li><p style="min-height:1.5em">You’ve built internal tooling or automation to improve support workflows — a triage bot, runbook generator, custom dashboard, or anything that turned a recurring manual task into a repeatable system.</p></li><li><p style="min-height:1.5em">You’re fluent with Claude Code or equivalent AI coding tools. Your value is judgment about when to automate and how to verify output, not syntax recall.</p><p style="min-height:1.5em"></p></li></ul><p style="min-height:1.5em"></p><h2><strong>Why Siena?</strong></h2><ul style="min-height:1.5em"><li><p style="min-height:1.5em">Meaningful impact. Your work directly shapes our product and company.</p></li><li><p style="min-height:1.5em">Globally distributed team working at the bleeding edge of CX and AI.</p></li><li><p style="min-height:1.5em">Great salary plus the opportunity for equity or stock grants.</p></li><li><p style="min-height:1.5em">Learning budget. If you're growing, so are we.</p></li><li><p style="min-height:1.5em">The thrill of building something new. Join us at a stage where your contributions matter most.</p></li><li><p style="min-height:1.5em">AI-fluency. Make AI your second nature. </p></li><li><p style="min-height:1.5em">Tackle unsolved problems. We’re redefining how customer experience will look like in the next decades.</p></li></ul><h2><strong>Our values</strong></h2><p style="min-height:1.5em">The people who thrive here are curious, customer-obsessed, and take ownership without being asked. They fix problems first and explain later. They're direct about feedback—both giving and receiving it—because they care more about getting things right than being polite. </p><p style="min-height:1.5em">They maintain high standards while moving at startup speed, and they build real relationships with teammates because they know that's how great work gets done. When things get tough, they adapt and keep pushing forward.</p><h2><br><strong>Our approach to AI</strong></h2><p style="min-height:1.5em">The people who thrive here treat AI like a natural extension of themselves. They've built their own ecosystem of agents - some for research, others for debugging, writing, analysis, or writing code. They know which AI works best for what problem.</p><p style="min-height:1.5em">Everyone gets premium accounts (ChatGPT, Claude, Perplexity Pro, Cursor, Lovable) plus a quarterly budget for new tools. But the magic happens in how we share knowledge. Demo days where someone shows off a clever workflows. Slack threads about which model handles a specific use case better. Learning from each other's AI workflows.</p><p style="min-height:1.5em">At Siena, we’re not just looking for people who can do a job. We’re looking for people who want to break boundaries, create the future, and reshape industries. If that’s you, we look forward to your application.</p><p style="min-height:1.5em">We use AI-assisted screening tools as part of our hiring process. All decisions are made by humans. You can request a human-only review at <a target="_blank" rel="noopener noreferrer nofollow" class="underline underline underline-offset-2 decoration-1 decoration-current/40 hover:decoration-current focus:decoration-current" href="mailto:talent@siena.cx">talent@siena.cx</a>.</p><p style="min-height:1.5em"><em>Siena provides equal employment opportunities to all employees and applicants for employment without regard to race, color, religion, sex, national origin, age, disability, genetics, sexual orientation, gender identity, or gender expression. We are committed to a diverse and inclusive workforce and welcome people from all backgrounds, experiences, perspectives, and abilities.</em></p>

Back to blog

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...