Incident Operations Commander
Command critical incidents end to end to restore service quickly
Serve as the on-duty commander for Alpaca's most critical incidents, directing cross-functional response to restore service quickly. You keep the right people engaged and informed, ensure correct severity assessment, and make sure every incident leaves behind actionable follow-up work for the organization.
Why This Role?
Direct founder access, real impact from day one
Key Responsibilities
- Take command of incidents from declaration to mitigation
- Keep responders focused on stopping customer and partner impact
- Ensure correct severity assessment during incident response
- Make sure the right engineers are engaged in the response
- Keep leaders informed in time during critical incidents
- Ensure follow-up work survives the incident call and is actionable
Requirements
- Experience directing cross-functional incident response
- Ability to keep responders focused during high-pressure situations
- Skill in ensuring correct incident severity assessment
- Experience keeping leaders informed during critical events
- Ability to make sure follow-up work is actionable post-incident
Required Skills
Indonesia Context
- Working Hours Overlap:
- Flexible — work your own hours
View Original Description from Greenhouse BoardsShow more
Original description from Greenhouse Boards
<div class="content-intro"><p><strong>Who We Are:</strong></p> <p><strong>Alpaca is a US-headquartered, global leader in agent-first brokerage infrastructure </strong>for stocks, ETFs, options, crypto, fixed income, 24/5 trading, and more.<br><br>Amongst our subsidiaries, Alpaca is a licensed financial services company, serving hundreds of financial institutions across 40 countries with our institutional-grade APIs. This includes broker-dealers, investment advisors, wealth managers, hedge funds, and crypto exchanges, totalling over 10 million brokerage accounts.<br><br>Our global team is a diverse group of experienced engineers, traders, and brokerage professionals who are working to achieve our mission of opening financial services to everyone on the planet. We're deeply committed to open-source contributions and fostering a vibrant community, continuously enhancing our award-winning, developer-friendly API and the robust infrastructure behind it.<br><br><strong>Alpaca is proudly backed by $400 million in funding from top-tier global investors including Portage Ventures, Spark Capital, Tribe Capital, Social Leverage, Horizons Ventures, Opera Tech Ventures, SBI Group, Derayah Financial, Unbound, Peak XV, Elefund, and Y Combinator.</strong><br><br><strong>Our Team Members:</strong></p> <p>We're a dynamic team of 400+ globally distributed members who thrive working from our favorite places around the world, with teammates spanning the USA, Canada, Japan, Hungary, Nigeria, Brazil, the UK, and beyond!<br><br>We're searching for passionate individuals eager to contribute to Alpaca's rapid growth. If you align with our core values—Stay Curious, Have Empathy, and Be Accountable—and are ready to make a significant impact, we encourage you to apply.</p></div><h3>Role</h3> <p>Serve as the on-duty commander for Alpaca's most critical incidents, directing cross-functional response to restore service quickly, keeping the right people engaged and informed, and making sure every incident leaves behind something the organisation can act on.</p> <p>You do not fix the outage. You make the response reliable: correct severity, the right engineers in the room, mitigation that does not stall, leaders informed in time, and follow-up work that survives the call.</p> <p><strong>Things You Get To Do</strong></p> <ul> <li><strong>Command incidents end to end.</strong> Take command from declaration to mitigation, keeping responders focused on stopping customer and partner impact as fast as possible. Run the bridge, keep observers out of the responders' way, and name a stall out loud when you see one.</li> <li><strong>Classify and hold the line on severity.</strong> Set severity at declaration and re-check it as facts arrive. Risk advises on financial and regulatory materiality; the call is yours.</li> <li><strong>Engage the right people, fast.</strong> Identify the owning team by service, symptom and blast radius, page them, and expand the responder set the moment the first team is wrong or not enough. When a page goes unanswered, escalate - and escalate the escalation. Bring in the leaders who must make business calls: feature flags, traffic shedding, failover, freeze-or-ship.</li> <li><strong>Hold the bridge, and protect the people fixing it. </strong>Keep engineering and technical support uninterrupted - questions from stakeholders, partners and executives come to you. Be the single source of truth to the partner communications team on impact, severity and timing: you decide when a status page update or partner contact is needed, they write and send it, and chasing a late or stale update is yours.</li> <li><strong>Run follow-the-sun handoffs.</strong> Deliver warm, high-fidelity handoffs across regions: current impact and severity, mitigation path and next actions, who is in the room, outstanding decisions, and what must not be dropped. The incoming commander confirms ownership before you step away - command never goes dark at a region boundary.</li> <li><strong>Close the loop, on the clock.</strong> Maintain the timeline of facts as the incident runs rather than reconstructing it afterwards - in a regulated business that record has to hold up long after the call ends. Once mitigated, make sure a blameless retrospective is scheduled with a named owner and a timebox, and record where the cause sits - that choice sets which follow-up items are mandatory. Every action item needs a real ticket, one named accountable, a priority and a category, delivered inside the agreed service level. If a postmortem produces nothing but low-priority items, treat that as a signal the analysis stopped early and escalate to SRE rather than passing it on.</li> <li><strong>Automate the coordination away.</strong> Coordination is the part of this job that should eventually belong to a machine. Every manual prompt you send - the update that is due, the question nobody answered, the partner nobody contacted - is a candidate for automation, and the direction we are heading is AI handling the routine so commanders can spend their attention on judgement. You get us there by working to the decision trees, saying where they are wrong, and being honest about which of your instincts are actually rules.</li> </ul> <p><strong>Who You Are (Must-Haves)</strong></p> <ul> <li>4+ years commanding or co-commanding high-severity incidents in a production engineering, SRE or technical operations environment.</li> <li>You direct technical responders under pressure without being the person writing the fix.</li> <li>You make and defend crisp severity and escalation decisions, and you take charge without waiting to be asked. Command means waking senior people at 03:00, interrupting an executive, and telling an experienced engineer to stop what they are doing - with an audience watching. It is a visible, directive role and it needs to be instinctive.</li> <li>You can read a dashboard and judge for yourself whether impact has actually stopped.</li> <li>You communicate clearly with engineers, executives and partner-facing stakeholders - and you know the difference between briefing the comms function and speaking for the company.</li> <li>You are comfortable holding other teams to account in the moment, across a reporting line that is not yours, without turning it into friction.</li> <li>You thrive in a follow-the-sun model with clean cross-region handoffs.</li> <li>You understand FinTech concepts and the trust stakes of API-driven financial platforms.</li> <li>You use AI tools and agentic automation to reduce manual toil and speed up response.</li> <li>You will work a regional coverage window as part of a global 24x7 Incident Commander roster.</li> </ul> <p><strong>Who You Might Be (Nice-to-Haves)</strong></p> <ul> <li>Formal incident command training - ITIL, Major Incident Management or crisis management.</li> <li>Experience with modern incident management and on-call platforms.</li> <li>You have written severity rubrics, decision trees, escalation matrices, runbooks or incident playbooks.</li> <li>You have commanded in game days, tabletop exercises or incident simulations, not only in production.</li> <li>You have partnered with problem management or reliability programme functions to roadmap incident follow-ups.</li> <li>Online securities trading or capital markets experience, or another regulated, market-hours-sensitive domain.</li> </ul><div class="content-conclusion"><h3><strong>How We Take Care of You:</strong></h3> <ul> <li style="font-weight: 400; text-align: justify;"><span style="font-weight: 400;">Competitive Salary & Stock Options</span></li> <li style="text-align: justify;">Health Benefits</li> <li style="font-weight: 400; text-align: justify;"><span style="font-weight: 400;">New Hire Home-Office Setup: One-time USD $500</span></li> <li style="font-weight: 400; text-align: justify;"><span style="font-weight: 400;">Monthly Stipend: USD $150 per month via a Brex Card</span></li> </ul> <p><em><span style="font-weight: 400;">Alpaca is proud to be an equal opportunity workplace dedicated to pursuing and hiring a diverse workforce.<br></span></em></p> <p><span style="font-size: 8pt;"><a href="https://files.alpaca.markets/disclosures/AlpacaRecruitmentPrivacyPolicy.pdf"><em><span style="font-weight: 400;">Recruitment Privacy Policy</span></em></a></span></p></div>
Salary Context
Similar Engineering roles on LokerDollar pay around $170k/yr (range $1k–1000k/yr, n=830 active listings).
Hiring at Alpaca
Alpaca has 16 other active roles on LokerDollar and has been hiring here since Jul 25, 2026 — across Engineering, Data & Analytics.
View all Alpaca openings →Market context
- ESTIMATEEstimated pay is 15% below the role median of $170,000/year (n=830 pay-disclosing listings).
- VERIFIEDAlpaca: 22 postings in the last 3 months, 22 all-time on LokerDollar.
- VERIFIEDCompany first seen Jul 25, 2026.
- VERIFIEDThis listing first seen Sep 15, 2026.
- VERIFIEDLast verified live Sep 29, 2026.
Openness not stated by employer — check the listing
Frequently asked questions
- Is Incident Operations Commander at Alpaca a remote job?
- Yes, Incident Operations Commander at Alpaca is remote, but the employer did not state which countries can apply. Check the listing before applying.
- What type of employment is Incident Operations Commander at Alpaca?
- This is a full time position.
- How do I apply?
- Click the "Apply" button on this page to go to the official application at Alpaca.
Explore related
Market data & reports
Salary & skill-demand research built from our own listings data.
- Indonesia IT Jobs vs Global Remote (2026)Primary analysis of 2,049 listings: methodology, classification rules, downloadable datasets.
- AI-Skill Demand: Indonesia vs Global Remote (2026)10,000+ postings, taxonomy-first classifier, Wilson CIs, pre-registered before analysis.
- Remote ≠ Remote: The Skills That Open Global Work to Indonesians (2026)12,891 remote listings: the highest-paid coding skills are the most geo-locked for Indonesia-based applicants. CC BY 4.0 aggregate dataset.
- The Compliance Layer of the AI Hiring Stack (2026)6,349 remote listings: 77.2% never state who may apply. Methodology and a CC BY 4.0 aggregate dataset.
- Indonesia Hiring Report: Tech vs Non-TechJob demand by field from aggregate open-job counts — never individual listings.
- Indonesia Salary BenchmarkAggregate salary ranges across roles, with open methodology and dataset.
- Indonesian Remote Work Salary & Demand IndexHow much of the global remote job corpus is open to Indonesia, and what it pays (USD) by role.
- Indonesia Quarterly Labor Market ReportLayoffs, funding, salaries & skills per quarter — open aggregates.
- Remote Market Reports by RoleAuto-generated per role family — skills, seniority, companies, salary.
- Global Remote Salary BenchmarkAnnual salary by role & currency, plus the share of listings open worldwide.
From the blog
- Interview Radiologist Remote: What You NeedBreaking down the remote radiology interview process for USD-paying jobs, from screening to offer letter.
- Remote Work Realities: What You Need to Know About Global USD OpportunitiesCut through the noise of viral job claims. Discover the reality of the global remote market, essential skill demands, and how to find verified USD-paying roles.
- Common Mistakes When Applying for RemoteStop getting your applications rejected. Here are the 7 common mistakes remote professionals make when applying for global, USD-paying roles.