<div><strong>Location:</strong> Europe or South America (remote)</div>
<div><strong>Team:</strong> Engineering</div>
<div><strong>Reports to:</strong> Head of Engineering<br><br><strong>About Extenteam</strong><br>Extenteam is the AI-driven operations platform for short-term rental property management, headquartered in Miami and founded in 2021. Our platform, Shared Services, handles guest communication and daily operational workflows for 80,000+ properties by pairing an AI orchestration layer with a shared-services team of hospitality-trained specialists, so no guest inquiry goes unanswered, day or night, and no property manager has to staff for the 2am cancellation themselves.<br><br>We're industry-only: every workflow, integration, and agent we hire is built around property management specifically, not bolted on from a generalist platform. As we push more of that platform toward AI-led automation and self-serve tools, the software our own Shared Services team works in every day has to keep pace, that's this role.<br><br><strong>Why This Role Exists</strong><br>Shared Services' guest communication runs on two things: an AI layer that handles as much of a conversation as it safely can, and a shared-services team of hospitality-trained agents who catch what the AI shouldn't touch alone. Every day, that team hits walls in the platform they use to do the work; bugs, missing tooling, workflows that don't match how a busy overnight shift actually runs. Some of that is a quick fix. Some of it is a signal that the platform is failing at scale, and by the time it reaches Engineering it's already cost real client trust.<br><br>We don't have a layer of PMs pre-chewing every one of those signals into a spec. We're hiring an engineer who can sit close to Operations, tell the difference between a one-off bug and a systemic gap, and ship the fix with no handoff required.<br><br><strong>The Role</strong><br>You'll report to the Head of Engineering. Priorities are set jointly with the Head of Operations, who owns the operational signal driving what gets built. You'll do two things:</div>
<ol>
<li><strong>Close incoming platform tickets from Shared Services.</strong> Agents, Team Leads, and Operations report issues daily; quick fixes, workflow bugs, configuration problems. You triage, diagnose, and ship.</li>
<li><strong>Find the pattern and fix it at the source.</strong> When multiple agents report the same friction, that's not a ticket, it's a product problem. When a client complaint traces back to repeated agent failures, you ask why the platform is allowing it, and you close that gap for good.</li>
</ol>
<div>Every ship goes through the same process as any other engineer's here: product filters for coherence, design filters for UX consistency, standard code review. This role works inside those guardrails, not around them.<br><br><strong>What You Will Do</strong></div>
<ul>
<li>Own features end to end; problem framing, design, backend, frontend, instrumentation, rollout, and the follow-up fixes nobody filed a ticket for.</li>
<li>Work with founders, product, and design at the whiteboard stage, before anything is written down, and help decide what's worth building.</li>
<li>Build the AI surfaces of the product; prompt and agent architecture, tool calling, retrieval, guardrails, and the human-in-the-loop escape hatches that make automation safe to ship.</li>
<li>Build and maintain evals. Treat "does this actually work" as an engineering artifact with a regression suite, not a vibe check before launch.</li>
<li>Watch real usage. Session replays, logs, transcripts, support tickets, and customer calls. Bring back what you learn as shipped changes, not as a document.</li>
<li>Own the details that make software feel good; latency budgets, token cost, empty states, error copy, loading behavior, keyboard paths. These are part of the feature, not a separate polish phase.</li>
<li>Cut scope and kill things. Argue a feature is wrong before you build it well.</li>
<li>Compound the team's velocity; CI, preview environments, internal tools, seed data, debugging surfaces. Leverage counts as product work.</li>
</ul>
<div><strong>What This Role Is Not</strong></div>
<ul>
<li><strong>Not a ticket queue firefighter.</strong> That's other roles on the Operations side.</li>
<li><strong>Not a shadow engineering team.</strong> You report to and work within Engineering.</li>
<li><strong>Not an independent operator building outside the platform.</strong> Everything you ship goes through product.</li>
</ul>
<div><strong>Anti-Signals</strong></div>
<ul>
<li>You want a ticket fully spec'd before you'll touch it</li>
<li>You treat "why does this keep happening" as someone else's question to answer</li>
<li>You measure your work by whether you closed the ticket, not whether the pattern stopped</li>
<li>Your AI/LLM experience is prompting a demo — never held to a reliability bar with a real agent depending on it at 2am</li>
</ul>
<div><strong>Required Experience</strong></div>
<ul>
<li>4+ years of <strong>full stack</strong> (stronger on the BE) software engineering experience shipping production enterprise software</li>
<li>Direct experience building internal tools, agent-facing platforms, or operational systems</li>
<li>Product mindset: comfortable scoping problems, asking the right questions, and communicating/prioritizing tradeoffs</li>
<li>Track record of shipping fast while working inside a product and design process</li>
<li>Experience working asynchronously with distributed teams</li>
</ul>
<div><strong>Required Technical Skills</strong></div>
<ul>
<li>Strong fluency in TypeScript. We currently use:
<ul>
<li>Next JS</li>
<li>NestJS</li>
<li>TypeORM with Postgres</li>
<li>BullMQ</li>
</ul>
</li>
<li>Comfortable with agentic coding tools (Claude Code, Cursor, Replit Agent)</li>
<li>API integration experience (REST, webhooks, third-party SaaS APIs)</li>
<li>Prompt engineering experience with production AI systems (OpenAI, Anthropic, or similar)</li>
</ul>
<div><strong>Strongly Preferred</strong></div>
<ul>
<li>Experience building tools for contact center, customer support, or operations teams</li>
<li>Short-term rental, hospitality, or property management domain knowledge</li>
<li>Track record of deploying AI agents in production</li>
</ul>
<div><strong>How You'll Work</strong></div>
<ul>
<li>Reports to the Head of Engineering</li>
<li>Priorities set jointly with the Head of Operations, based on operational signal</li>
<li>Product decisions filter through the Head of Product</li>
<li>Design decisions go through our design team</li>
<li>Weekly syncs with Engineering, Operations, and Product</li>
<li>5 hours of overlap with Miami time (Eastern), minimum, daily</li>
</ul>
<p><strong>Compensation</strong></p>
<p>Base range is $70-105K USD depending on location and experience.</p>
<p> </p>
