Remote Job at Alpaca – 8 Positions

Applications are invited from interested and qualified candidates to apply for the Remote Job at Alpaca.

Alpaca is a fast-growing series B fintech company that’s raised over $120 million in funding. Alpaca is an API-first stock and crypto platform that enables developers and businesses across the world to build trading algorithms, applications, and brokerage services.

We have 150+ globally distributed (remote) team members who love to work from their favorite places in the world. We have team members based in the USA, Canada, Hungary, Japan, Brazil, Spain, Philippines, Nigeria, UK, and more! We love candidates who have a passion for making a global difference in financial services and technology, by impacting local communities and becoming a part of our hyper-growth company.

Individuals interested in the Job at Alpaca should review the details, requirements, and application process provided below.

Corporate Operations Lead

Specifications:

• Full Time | Remote
• Eligibility: All Countries
• Location: US | Abroad. See other Remote Jobs
• Category: Tech
• Job Alerts: To receive Job Alerts on WhatsApp, Click HERE

Description:

Make Alpaca scale by owning and resolving the operating constraints Corporate Operations prioritizes.

Your mission is to take high-impact operating constraints from discovery through measurable outcome: drive them to resolution, establish durable ownership with the right long-term owner, then move to the next priority. You parachute into unfamiliar domains (HR, Finance, Engineering capacity, regional operating models, broker dealer bottlenecks, and more), diagnose what’s actually limiting scale, create the solution, and stay accountable until the outcome actually changes. You are a builder-operator, not a coordinator. You work on the problems Corporate Operations has prioritized as highest-value for the company right now.

Things You Get To Do:

• Own prioritized constraints end-to-end. Take cross-functional operating problems from zero context through measurable outcome. When the constraint is removed and the fix persists, you move on. You do not hold permanent territory in any function.
• Work in any domain, including BD ops when it’s the bottleneck. This month that might be HR automation or Finance close; next quarter decision delegation or Engineering throughput; later a broker dealer constraint (AML scale, reconciliations, operational readiness) if that’s where Alpaca is stuck. Domain expertise is not the job. Systems thinking across unfamiliar domains is.
• Sense → Design → Build → Drive. Measure what’s happening, redesign what’s broken, create the processes/automation/governance/infrastructure needed (or mobilize Engineering, Product, ORE, or functional teams when that’s the right answer), and drive adoption until the outcome changes.
• Partner across the company. Work directly with functional leaders and their teams to mobilize resources and drive adoption. You influence priorities and surface capacity needs; you do not absorb the function or run their day-to-day execution.
• Create non-linear leverage. Ask whether workflow redesign, automation, org design, better decisions, vendor changes, or hiring is the right lever, and use whichever applies. Success means creating leverage so Alpaca needs fewer incremental people to support the same growth in the areas you touch.
• Contribute to company deep-dives. Help establish baselines for velocity, capacity, and friction in the areas you work in.
• Communicate capacity honestly. Be explicit about trade-offs and escalate when scope or priority needs Director or VP input, including when work should be deferred.

Qualifications and Requirements:

• Builder-operator with end-to-end ownership. Proven track record taking ambiguous, high-stakes problems from zero context to measurable outcome. You don’t hand off recommendations and walk away.
• Systems thinker who learns fast. Able to parachute into unfamiliar domains, map workflows/capacity/decision systems, diagnose root cause, and become effective without deep prior subject-matter expertise.
• Influence without authority. Proven ability to mobilize cross-functional teams, partner with senior stakeholders, and drive adoption among people who don’t report to you.
• Prioritization and judgment. Able to distinguish root cause from symptoms, focus on what matters, and push back with evidence when scope drifts.
• Analytical rigor. Comfortable establishing metrics, measuring before/after, and using data, not anecdotes, to diagnose problems and prove impact.
• High ownership through implementation. You finish what you start. Adoption and lasting change matter as much as the design.
• 7+ years of relevant professional experience, including demonstrated ownership of complex, cross-functional operating initiatives from diagnosis through implementation and measurable outcome.

Who You Might Be (Nice-to-Haves):

• Experience in internal product, strategy/ops, business operations, or operational transformation with strong builder instincts.
• Strong fluency in AI and automation as tools for creating operating leverage.
• FinTech or brokerage exposure is helpful in BD ops contexts. The job is operating pattern recognition, not securities expertise.
• Capability spikes in systems/product build, executive orchestration, or quantitative capacity analysis.

What This Role Is Not:

A PMO project manager, business analyst who hands off recommendations, permanently embedded functional ops leader, process documentation role, product manager owning a product roadmap, or coordinator who stops at diagnoses and handoff. Functional leaders retain their teams and recurring execution; you own the constraint until it is resolved and durable ownership is established.

How We Take Care of You:

• Competitive Salary & Stock Options
• Health Benefits
• New Hire Home-Office Setup: One-time USD $500
• Monthly Stipend: USD $150 per month via a Brex Card

Software Engineer – Market Data

Specifications:

• Full Time | Remote
• Eligibility: All Countries
• Location: UK | Abroad. See other Remote Jobs
• Category: Tech
• Job Alerts: To receive Job Alerts on WhatsApp, Click HERE

Description:

As a Senior Software Engineer on the Platform team, you will build and own the frameworks, tooling, and CI/CD infrastructure that let Alpaca’s engineers ship new features quickly and reliably. This is a software engineering role at its core: you will spend most of your time writing Go, designing automated test frameworks, and digging into application code and Kubernetes when needed. Just as importantly, you will help redefine how we use AI to raise the bar on quality – leveraging LLMs and AI-driven tooling to generate tests, catch regressions before they ship, and turn every incident into durable, automated coverage. We are looking for engineers who treat quality as an engineering discipline and see AI as a force multiplier for it – people who build the systems that make testing fast, reliable, and effortless for the teams that depend on them.

Things You Get To Do

• Design and build automated test frameworks across our REST and gRPC API surface.
• Leverage AI and LLM-based tooling to accelerate test generation, harden regression coverage, and turn production incidents into automated tests – embedding these practices into the frameworks the whole engineering org relies on.
• Build and maintain CI/CD pipelines – we use a mix of GitHub Actions and Google Cloud Build.
• Design and execute load, stress, and scalability tests to ensure our platform can handle growing demand.
• Introduce chaos engineering practices – designing fault-injection and resilience experiments that surface failure modes before our customers do.
• Standardize tooling and infrastructure to improve the day-to-day developer experience.
• Partner with other teams to raise test coverage, reliability, and speed across services.
• Dig into application code to root-cause failures and drive fixes to completion.
• Mentor and guide product engineers, fostering a culture of quality and continuous improvement.

---

Join Jobs Region WhatsApp Group To Receive Job Alerts!

• Jobs Region Group 1
• Jobs Region Group 2
• Jobs Region group 3

---

Qualifications and Requirements:

• You have 5+ years of experience as a software engineer building and maintaining production systems.
• You have written code in strongly typed languages and have at least 1 year of experience with Go.
• You are fluent with AI-assisted engineering – you actively use LLM-based tools in your workflow and have a clear point of view on where they elevate quality (and where they don’t).
• You have built and maintained CI pipelines before – ideally with GitHub Actions or Google Cloud Build.
• You have designed and built automated test frameworks, and you understand the challenges microservices pose for reliable integration and end-to-end testing.
• You are familiar with Kubernetes beyond the basics – you can write a Helm chart for a new service with relative ease, you understand best practices around security, and you have prior job experience or certifications to prove this.
• You have worked at a startup before – you understand that things don’t always go according to plan, that there is significant technical debt, that some tasks just need to be done, and that sometimes there are no processes or documentation to guide your hand.
• You are not afraid of taking a task from start to finish – gathering requirements, figuring out and implementing the best technical solution, then deploying and monitoring the results.

Who You Might Be (Bonus Points)

• You have used AI/LLM tooling to build QA automation – test generation, flaky-test triage, or incident-to-regression pipelines – and can speak to what worked and what didn’t.
• You have written code in Python or TypeScript, and can build efficient Dockerfiles and secure container images.
• You have implemented load tests with k6 (REST) and ghz (gRPC) and have experience analyzing pprof/trace output.
• You have done IaC deployments with Argo CD or Terraform, or have used Google Cloud Platform and Google Kubernetes Engine before. You are familiar with Tilt and have written a Kubernetes Operator before.
• You have practiced chaos engineering – running fault-injection or resilience experiments with tools like Chaos Mesh, LitmusChaos, or Gremlin.
• You are familiar with testing event-driven systems using Kafka (or even better, Redpanda).

How We Take Care of You:

• Competitive Salary & Stock Options
• Health Benefits
• New Hire Home-Office Setup: One-time USD $500
• Monthly Stipend: USD $150 per month via a Brex Card

Senior Software Engineer – Ledger

Specifications:

• Full Time | Remote
• Eligibility: All Countries
• Location: US | Abroad. See other Remote Jobs
• Category: Tech
• Job Alerts: To receive Job Alerts on WhatsApp, Click HERE

Description:

As a senior software engineer, you will help build and scale the systems and services that form the foundation of Alpaca and empower millions of users who are trading billions of dollars worth of assets.

The market data team is responsible for improving the overall architecture of Alpaca connected to data products such as stocks, options, crypto, and foreign exchange markets. Oversee their public API structure and documentation on both streaming and historical endpoints. The team is responsible for building a cohesive developer-first API and is tasked with planning, ideating, experimenting, and putting into production the new services, and libraries that overcome some of our greatest technical challenges as we continue to scale rapidly.

We are looking for senior or staff engineers who are keen on providing quality solutions, have great fundamentals, have proven experience building and architecting at scale, and are not afraid of challenging conventions. This demanding team also requires a deep understanding of POSIX-like operating systems, modern infrastructure, and orchestration practices.

Things You Get To Do:

• Influence the overall architecture of Alpaca’s market data systems
• Design highly scalable, mission-critical systems
• Obsess over latency (every nanosecond counts)
• Implement backend services and lead architecture where scalability and resilience matters
• Maintain good software quality and test coverage
• Participate in code reviews
• Troubleshooting on incidents and reported bugs
• You may be asked to be on-call to assist with engineering projects that are timely in nature

Qualifications and Requirements:

• At least 4 years of experience working on systems at scale
• Experience with at least compiled imperative languages (e.g. Go, C, C++, Rust, etc.). Most of our critical services are written in Go
• SQL or relational database skills
• Familiarity with TCP/IP, and UDP networking
• Proficient with Linux/BSD, and shell scripting
• Excited about what we are building at Alpaca
• Proven track record of architecting and leading medium-scale projects involving multiple teams
• Experience with Kubernetes or other workload orchestration and scheduling systems (we primarily use Kubernetes via GKE)
• Experience with major cloud platforms (we primarily use GCP)
• A passion for financial markets

Who You Might Be (Nice-to-Haves):  

• Experience with Market Data 
• Knowledge of microservice architectures
• Knowledge of clean code principles
• DevOps mindset is an asset
• Cloud Networking experience (BGP, VPC peering)
• Experience in building low-latency applications
• Experience with distributed key-value stores
• Experience with CI/CD
• A passion for financial markets or the desire to learn
• Knowledge of Agile/Scrum methodologies
• Experience with observability, tracing, continuous profiling
• Experience with capacity planning and benchmarking

How We Take Care of You:

• Competitive Salary & Stock Options
• Health Benefits
• New Hire Home-Office Setup: One-time USD $500
• Monthly Stipend: USD $150 per month via a Brex Card

Senior Software Engineer – Market Data

Specifications:

• Full Time | Remote
• Eligibility: All Countries
• Location: US | Abroad. See other Remote Jobs
• Category: Tech
• Job Alerts: To receive Job Alerts on WhatsApp, Click HERE

Description:

As a senior software engineer, you will help build and scale the systems and services that form the foundation of Alpaca and empower millions of users who are trading billions of dollars worth of assets.

The market data team is responsible for improving the overall architecture of Alpaca connected to data products such as stocks, options, crypto, and foreign exchange markets. Oversee their public API structure and documentation on both streaming and historical endpoints. The team is responsible for building a cohesive developer-first API and is tasked with planning, ideating, experimenting, and putting into production the new services, and libraries that overcome some of our greatest technical challenges as we continue to scale rapidly.

We are looking for senior or staff engineers who are keen on providing quality solutions, have great fundamentals, have proven experience building and architecting at scale, and are not afraid of challenging conventions. This demanding team also requires a deep understanding of POSIX-like operating systems, modern infrastructure, and orchestration practices.

Things You Get To Do:

• Influence the overall architecture of Alpaca’s market data systems
• Design highly scalable, mission-critical systems
• Obsess over latency (every nanosecond counts)
• Implement backend services and lead architecture where scalability and resilience matters
• Maintain good software quality and test coverage
• Participate in code reviews
• Troubleshooting on incidents and reported bugs
• You may be asked to be on-call to assist with engineering projects that are timely in nature

Qualifications and Requirements:

• At least 4 years of experience working on systems at scale
• Experience with at least compiled imperative languages (e.g. Go, C, C++, Rust, etc.). Most of our critical services are written in Go
• SQL or relational database skills
• Familiarity with TCP/IP, and UDP networking
• Proficient with Linux/BSD, and shell scripting
• Excited about what we are building at Alpaca
• Proven track record of architecting and leading medium-scale projects involving multiple teams
• Experience with Kubernetes or other workload orchestration and scheduling systems (we primarily use Kubernetes via GKE)
• Experience with major cloud platforms (we primarily use GCP)
• A passion for financial markets

Who You Might Be (Nice-to-Haves):  

• Experience with Market Data 
• Knowledge of microservice architectures
• Knowledge of clean code principles
• DevOps mindset is an asset
• Cloud Networking experience (BGP, VPC peering)
• Experience in building low-latency applications
• Experience with distributed key-value stores
• Experience with CI/CD
• A passion for financial markets or the desire to learn
• Knowledge of Agile/Scrum methodologies
• Experience with observability, tracing, continuous profiling
• Experience with capacity planning and benchmarking

How We Take Care of You:

• Competitive Salary & Stock Options
• Health Benefits
• New Hire Home-Office Setup: One-time USD $500
• Monthly Stipend: USD $150 per month via a Brex Card

Senior Site Reliability Engineer

Specifications:

• Full Time | Remote
• Eligibility: All Countries
• Location: US | Abroad. See other Remote Jobs
• Category: Tech
• Job Alerts: To receive Job Alerts on WhatsApp, Click HERE

Description:

As a Site Reliability Engineer at Alpaca, you’ll help keep our brokerage platform reliable, observable, and operable as we grow – working across our cloud infrastructure, Kubernetes platform, observability stack, messaging layer, and data layer. We’re especially interested in candidates with strong PostgreSQL fundamentals who’d like to grow into deeper ownership of our database reliability posture: PostgreSQL sits on the trading-critical path, and we want this person to spend a meaningful share of their time leveling it up while still being a well-rounded SRE the rest of the week.

Things You Get To Do

• Operate production day-to-day – oncall, incident response, postmortems, and the follow-ups that actually close the loop.
• Own reliability practice – define and refine SLIs/SLOs and error budgets, and help product teams live within them.
• Strengthen our observability across metrics, logs, traces, and alerting.
• Ship infrastructure through code in a GitOps workflow – cloud resources and Kubernetes workloads alike.
• Look after PostgreSQL: performance tuning, schema and migration review, online migrations on large tables, HA/DR, and CDC pipelines.
• Mentor engineers on reliability and database fundamentals through code review, design review, and pairing.

Qualifications and Requirements:

• 4+ years in SRE, DevOps, Platform/Infrastructure, or backend engineering with significant production operations ownership.
• Hands-on experience operating production services on Kubernetes, and shipping infrastructure as code in a GitOps workflow.
• Solid working knowledge of PostgreSQL in production — query plans, pg_stat_*, indexing and schema trade-offs, and what a safe online migration looks like on a non-trivial table.
• Cloud networking fundamentals (VPCs, routing, L4/L7 load balancing, DNS, TLS) and comfort debugging cross-service connectivity.
• Comfortable with a modern observability stack and proficient with Linux at the operator level.
• Practiced in incident response – calm under pressure, structured debugging, postmortems that drive change.
• At least working proficiency in Go or Python, plus strong written and verbal communication.
• Genuine interest in databases and in growing your PostgreSQL/DBA expertise.

Who You Might Be (Nice-to-Haves):

• Deeper PostgreSQL experience: large clusters at OLTP load, online migrations on big tables, HA/DR ownership, connection pooling at scale, or change-data-capture pipelines.
• Experience with typed SQL access layers in Go (e.g. pgx, gorm, sqlc).
• Production experience with messaging systems at scale (e.g. RabbitMQ, Kafka, Redpanda).
• Security & compliance experience in a regulated environment (SOC 2, secrets management, audit logging).
• Familiarity with trading, brokerage, or other regulated fintech domains.

How We Take Care of You:

• Competitive Salary & Stock Options
• Health Benefits
• New Hire Home-Office Setup: One-time USD $500
• Monthly Stipend: USD $150 per month via a Brex Card

Incident Operations Lead (EMEA/AMER)

Specifications:

• Full Time | Remote
• Eligibility: All Countries
• Location: US | Abroad. See other Remote Jobs
• Category: Tech
• Job Alerts: To receive Job Alerts on WhatsApp, Click HERE

Description:

Lead the team that commands Alpaca’s most critical incidents. You will build the function and then keep raising its bar: the severity model, the escalation and communication paths, 24×7 follow-the-sun coverage, and the KPIs that prove it is improving. You will do that across boundaries – with the engineering teams who own the services, with SRE on reliability standards and on-call readiness, with Risk on financial and regulatory materiality, with our partner communications teams on what reaches a customer, and with reliability programme management on what happens after.

You will own how well we respond. Not the fix, not the partner communication, and not the reliability standard. Holding that line is a deliberate part of the design and a core part of the job.

Things You Get To Do

• Build the team and stand up 24×7 command. Recruit and certify Incident Commanders, build a follow-the-sun rotation across APAC, EMEA and AMER with warm handoffs at every regional boundary, and carry a rostered slot yourself. Keep the team sharp between real incidents with game days, tabletop exercises and simulations, and coach them through the live ones. Build a blameless review culture that treats an outlier as a process gap rather than a person’s failure.
• Own the process, and keep raising it. Drive severity maturity with Risk on financial and regulatory materiality – in a regulated brokerage a severity call can also start a reporting clock, so the model has to map cleanly onto those thresholds. Own the escalation path and what happens when a page goes unanswered, agree the thresholds for taking an incident to engineering leadership, and keep the service catalogue and its ownership current – time spent working out who owns a failing service is customer impact.
• Own both bridges. Your team connects the engineers and technical support fixing the problem, who need uninterrupted focus, to the partner communications teams, who need a continuous and accurate feed. You open the channel, supply the facts and hold the update cadence to account. Afterwards, your team runs the retrospective with SRE – who own the technical depth – and builds the post-incident package while the room is still warm, every item ticketed, owned and tagged, delivered inside a service level you define and then hold, before reliability programme management drives it to closure. You then synthesise the discussion into short, digestible learnings and publish them to the whole engineering organisation, so one team’s failure becomes everyone’s lesson instead of a document three people read.
• Own the KPIs. Time to respond and time to mitigate end to end, including the definitions and data hygiene beneath them: what separates mitigated from resolved, and whether a timestamp means what it claims. Establish a defensible baseline before committing to targets, then move them by severity. Review and approval, not authorship, is where postmortems stall, so report overdue reviews by team and incident with a next action against each.
• Build it as a product, then automate it with AI. Everything is documented, versioned and deployable, so you can stand up command from the artefacts alone; the process needs to scale considerably faster than the team. The automation we are after is AI workflows and agents rather than scripts and dashboards – agents that set an incident up, assemble the timeline as it runs, draft the RCA and the action package, and chase the update that is due or the review that is overdue. You own that roadmap: what an agent may do unsupervised, what still needs a commander’s judgement, and the decision-tree quality that makes either of them safe.

Qualifications and Requirements:

• You have stood up an incident command or major-incident function, not only worked inside one – you have owned the severity model, built the roster and driven adoption across teams.
• 5+ years in production engineering, SRE or technical operations, including hands-on command of high-severity incidents.
• You have led a distributed team across time zones and run a 24×7 rotation.
• You get engineers you do not manage to do things, and you can defend a severity call to someone who disagrees with it.
• You have built reliability metrics people trust, and you know the difference between improving a number and improving reality.
• You are disciplined about scope. You can say “that is not ours” and route it, in the middle of an outage, without leaving a gap.
• You write well enough that your process documents actually get used, you can hold a bridge calm under pressure, and you can brief an executive mid-incident without either downplaying it or dramatising it.
• You understand FinTech and the trust stakes of API-driven financial platforms.
• You use AI and agentic automation to remove toil rather than to add tooling.

Who You Might Be (Nice-to-Haves)

• Formal incident command training – ITIL, Major Incident Management or crisis management.
• You have run a certification, game day or drill programme, or built a pool of certified responders beyond your own headcount.
• Experience with modern incident management and on-call platforms.
• You have built a service catalogue or ownership registry that people actually maintained.
• You have worked with programme management or reliability functions to convert incident follow-ups into funded roadmap work.
• Familiarity with incident reporting obligations in regulated financial services – DORA, Reg SCI, FINRA or equivalent.
• Online securities trading or capital markets experience, or another regulated, market-hours-sensitive domain.
• You have deployed the same operating model into a second region or entity.

How We Take Care of You:

• Competitive Salary & Stock Options
• Health Benefits
• New Hire Home-Office Setup: One-time USD $500
• Monthly Stipend: USD $150 per month via a Brex Card

Senior DevOps Engineer

Specifications:

• Full Time | Remote
• Eligibility: All Countries
• Location: US | Abroad. See other Remote Jobs
• Category: Tech
• Job Alerts: To receive Job Alerts on WhatsApp, Click HERE

Description:

As a Senior DevOps Engineer you will design, build and operate the infrastructure that lets Alpaca scale globally and run trading-critical systems with confidence. You will have the autonomy to design and implement solutions against clearly defined goals – and a real voice in shaping those goals with the team.

We are not hiring a specialist in any single tool. We are looking for a well-rounded infrastructure engineer who thinks in cloud architecture and Infrastructure-as-Code, with a genuine Platform-as-a-Product mindset: someone who measures success by how quickly and safely the rest of engineering can ship, and who treats manual toil as a bug to be engineered away. You are comfortable operating our data stores (PostgreSQL, Message Brokers) at an operator level, partnering with our SRE and database specialists on the deeper work.

Things You Get To Do

• Design and evolve our cloud architecture on GCP – networking, interconnects, IAM and high-availability topology – and express it entirely as code with Terraform, following GitOps as a first principle.
• Build and own the CI/CD pipelines that plan, review, test and safely apply IaC changes – Policy-as-Code guardrails, drift detection and progressive rollout so infrastructure changes ship as confidently as application code.
• Advance Platform-as-a-Product: build self-serve capabilities and paved paths so engineers can provision what they need, through a golden path rather than a hand-off.
• Strengthen our observability stack – metrics, logs, traces and alerting across Prometheus, Thanos, Grafana, Loki, Tempo and Alertmanager – so the platform is easy to run and reason about.
• Operate our GKE clusters and the infrastructure services that run on them – Helm-packaged workloads, message brokers (RabbitMQ, IBM MQ) and data stores.
• Participate in our Follow-The-Sun on-call model: watch and triage alerts, join and declare incidents, lead structured debugging and escalation, and drive blameless post-mortems and the post-actions that actually close the loop.
• Embed SRE practices – SLIs/SLOs and error budgets, capacity planning – into how Core Infrastructure builds and operates, working closely with our SRE function.

Qualifications and Requirements:

• 5+ years in a DevOps, Platform/Infrastructure, or SRE role, with a proven track record operating large-scale, high-availability, high-performance systems in production.
• Deep hands-on experience designing cloud architecture on Google Cloud Platform (GCP) as the primary cloud – landing zones, networking, IAM and high-availability topology.
• Strong Infrastructure-as-Code skills with Terraform, structuring large codebases across multiple environments, with GitOps as a first principle and least-privilege as a default mindset.
• Proven experience building CI/CD pipelines for IaC – automated plan/apply, code review, Policy-as-Code, drift detection and safe rollout.
• Significant production experience with Kubernetes (ideally GKE) and packaging/deploying workloads with Helm.
• Solid cloud and L3/L4-L7 networking fundamentals (VPCs, routing, load balancing, DNS, TLS, interconnects) and comfort debugging cross-service connectivity.
• Hands-on experience with a modern observability stack – Prometheus, Thanos, Grafana, Loki, Tempo and Alertmanager – across metrics, logs, traces and alerting.
• Operator-level familiarity with data stores such as PostgreSQL and Message Brokers (e.g. RabbitMQ, RedPanda) – able to run and troubleshoot them in production.
• A good understanding of SRE practices – SLOs/error budgets, capacity planning – and a Platform-as-a-Product mindset.
• Strong grasp of incident management end to end: joining and declaring incidents, structured debugging under pressure, escalation, clear documentation, and post-mortems that drive real change.
• Able and willing to take part in a Follow-The-Sun on-call rotation from APAC hours, and to work effectively in a distributed, async-first team with strong written communication.

Who You Might Be (Bonus Points)

You can succeed in this role without all of the below, but any of these will help you ramp faster:

• Policy-as-code and IaC quality tooling (OPA/Conftest, Checkov, tflint, Atlantis, or similar).
• Experience managing Terraform state, module registries and versioning at scale across many teams.
• Experience building self-serve developer platforms and internal golden paths (e.g. with Backstage, Tilt, or similar).
• Experience with the Alloy collector and with incident tooling such as Rootly.
• Working proficiency in Go for automation and tooling.
• Strong Linux (Debian/Ubuntu) and container (Docker/containerd) fundamentals.
• Security and compliance experience in a regulated environment (SOC 2, secrets management, audit logging).
• Familiarity with trading, brokerage, or other regulated fintech domains, and with low-latency systems.

How We Take Care of You:

• Competitive Salary & Stock Options
• Health Benefits
• New Hire Home-Office Setup: One-time USD $500
• Monthly Stipend: USD $150 per month via a Brex Card

Incident Operations Commander

Specifications:

• Full Time | Remote
• Eligibility: All Countries
• Location: US | Abroad. See other Remote Jobs
• Category: Tech
• Job Alerts: To receive Job Alerts on WhatsApp, Click HERE

Description:

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.

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.

Things You Get To Do

• Command incidents end to end. 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.
• Classify and hold the line on severity. Set severity at declaration and re-check it as facts arrive. Risk advises on financial and regulatory materiality; the call is yours.
• Engage the right people, fast. 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.
• Hold the bridge, and protect the people fixing it. 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.
• Run follow-the-sun handoffs. 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.
• Close the loop, on the clock. 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.
• Automate the coordination away. 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.

Qualifications and Requirements:

• 4+ years commanding or co-commanding high-severity incidents in a production engineering, SRE or technical operations environment.
• You direct technical responders under pressure without being the person writing the fix.
• 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.
• You can read a dashboard and judge for yourself whether impact has actually stopped.
• 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.
• You are comfortable holding other teams to account in the moment, across a reporting line that is not yours, without turning it into friction.
• You thrive in a follow-the-sun model with clean cross-region handoffs.
• You understand FinTech concepts and the trust stakes of API-driven financial platforms.
• You use AI tools and agentic automation to reduce manual toil and speed up response.
• You will work a regional coverage window as part of a global 24×7 Incident Commander roster.

Who You Might Be (Nice-to-Haves)

• Formal incident command training – ITIL, Major Incident Management or crisis management.
• Experience with modern incident management and on-call platforms.
• You have written severity rubrics, decision trees, escalation matrices, runbooks or incident playbooks.
• You have commanded in game days, tabletop exercises or incident simulations, not only in production.
• You have partnered with problem management or reliability programme functions to roadmap incident follow-ups.
• Online securities trading or capital markets experience, or another regulated, market-hours-sensitive domain.

How We Take Care of You:

• Competitive Salary & Stock Options
• Health Benefits
• New Hire Home-Office Setup: One-time USD $500
• Monthly Stipend: USD $150 per month via a Brex Card

Jobs Region Alert