Senior Fullstack Engineer - Operational Automations
Alpaca
—
Jul 15, 2026
—
Jul 21, 2026
What this job asks for AI summary
A senior fullstack engineering role focused on eliminating manual work within brokerage operations by building automations, internal tooling, and auditable software systems. The work involves embedding with operational teams to understand workflows end-to-end, then designing and owning backend services and UIs — primarily in Golang and TypeScript/React — that replace those manual processes. Suits engineers with strong full-stack skills who are comfortable reasoning about human workflows as systems and operating what they build in production.
Senior level · 5+ years · Remote · Full-time
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 11,700 people nationally plausibly meet what this posting asks for (software developers). range 7,000–17,500
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $138,970 (middle half $107,524–$175,762).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (7)
The role is fully remote and globally distributed — no specific metro or country is required, though Alpaca is US-headquartered. The posting lists teammates across many countries, so the primary work location is ambiguous; the US-based flag defaults to true per policy.
ArgoCD and Terraform appear in the required 'Own the full lifecycle' section alongside CI/CD, framed as examples ('tools like ArgoCD and Terraform'). Because they sit within a hard-requirements context with firm ownership language, they are treated as hard gates; the 'like' qualifier signals substitutability but not optionality.
PostgreSQL is listed as 'preferably PostgreSQL' within the required SQL/relational-database bullet — the preference qualifies the specific flavour, not the SQL requirement itself. PostgreSQL is retained as a required skill reflecting the stated preference, with the understanding that strong SQL experience is the firm gate.
Observability/tracing/continuous profiling is listed as a single required bullet; 'observability' is used as the canonical skill name to cover all three.
GCP is mentioned only in a parenthetical aside ('we primarily use GCP') inside the nice-to-haves section, so it is marked preferred.
No compensation figures are disclosed beyond equity and benefits descriptions.
This posting reads as a fully-remote role, so it was scored against the national candidate pool rather than a single metro.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.