Time since we first saw it
Day 38
Similar jobs usually come down between day 6 and day 47.
From 1,405 similar postings that came down. Coming down is not always a hire.
Staff Analytics Engineer
Remote - EMEA
Live, first seen by us 38 days ago- Pay
- Pay not listed
- Work setting
Remote — work setting source
Listed location: Remote - EMEA
Read the full posting- Employment
- Not stated
What you’ll work on
Full postingSet multi-quarter technical direction for warehouse layering, materialization, and standards for 1,000+ dbt models
Decide which models go to lakehouse queries, real-time OLAP, or a semantic layer
Agree schemas, freshness SLAs, and change notices with source owners; pick CDC or batch per source
Guarantee cent-level accuracy on financial data using tests, reconciliation, and write-audit-publish
Set org-wide modeling, testing, and CI/CD standards and mentor engineers
From the employer’s posting
Set the multi-quarter technical direction for the warehouse.
Decide which models are served through ad hoc OLAP queries on the lakehouse, which belong in a real-time analytics engine for low-latency internal and partner-facing use, and which become governed metrics in a semantic layer.
Agree on schemas, freshness SLAs, and change notification with source owners, and choose CDC or batch for each source based on what consumers need.
Guarantee cent-level accuracy on financial data with tests, reconciliation, and write-audit-publish patterns that keep silent errors from shipping.
Set org-wide standards for modeling, testing, and CI/CD, mentor engineers, and win alignment across teams.
About Alpaca
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.
In the employer’s words · Read in context
Posting record
Report an error- Status in our records
- Live
- First seen by us
- Sep 26, 202638 days ago
- Recorded sightings
- 33
- Last seen by us
- Nov 4, 2026
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
How this job compares
Alpaca is hiring
5 open jobs
Open jobs by the week we first saw them, last 12 weeks.
- Takes jobs down at a usual pace
See how this role fits your experience
Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
- Python
- SQL
- Airbyte
- ClickHouse
- dbt
- Iceberg
- Spark
- Trino
- Airflow
Where the posting names them
- A clear point of view on when a dataset belongs in a lakehouse query engine, a real-time OLAP engine such as ClickHouse, or a semantic layer. - Expert-level SQL and dbt, plus Python for transformations beyond SQL. - Experience defining data contracts and freshness SLAs with upstream producers, and an understanding of the trade-offs between CDC and batch ingestion.
- AI and agentic analytics: making data usable by LLMs and agents, building evals. - Familiarity with Airflow, Airbyte, and CDC tooling such as Debezium or Redpanda. - Brokerage or financial-markets domain experience.
- Deep query-performance expertise on distributed engines such as Trino, Presto, or Spark. This includes reading query plans, partitioning and file layout on Apache Iceberg, and incremental materialization. - A clear point of view on when a dataset belongs in a lakehouse query engine, a real-time OLAP engine such as ClickHouse, or a semantic layer. - Expert-level SQL and dbt, plus Python for transformations beyond SQL.
Nice to Haves: - Production experience modeling data for ClickHouse or another real-time OLAP engine. - AI and agentic analytics: making data usable by LLMs and agents, building evals.
Responsibilities: - Set the multi-quarter technical direction for the warehouse. This covers layering (staging, intermediate, marts), domain boundaries, materialization and incremental strategies, and the standards that keep more than 1,000 dbt models fast, testable, and cost-efficient as we grow 10x. - Decide which models are served through ad hoc OLAP queries on the lakehouse, which belong in a real-time analytics engine for low-latency internal and partner-facing use, and which become governed metrics in a semantic layer.
- Has led an org-level warehouse migration or redesign, such as a mart restructure, semantic layer rollout, or testing and CI overhaul. - Deep query-performance expertise on distributed engines such as Trino, Presto, or Spark. This includes reading query plans, partitioning and file layout on Apache Iceberg, and incremental materialization. - A clear point of view on when a dataset belongs in a lakehouse query engine, a real-time OLAP engine such as ClickHouse, or a semantic layer.
Your next step
Complete your application on job-boards.greenhouse.io. The employer’s form will show what is required.
Applying through Greenhouse
- No account needed: the form is one page, with an “Autofill my application” option that reads your resume.
- Greenhouse doesn’t read resumes over 2.5 MB, or details placed in a header, footer, text box, table or second column. The file still attaches, but a recruiter has to type you in by hand.
Already applied? Track this application
About the role
We file this job under Analytics Engineer, by the work the posting describes.
Analytics engineers turn raw warehouse data into clean, tested and documented tables that analysts and dashboards can rely on, often with dbt.
Expect strong SQL, data modeling, Git, and a warehouse such as Snowflake, BigQuery or Redshift.
A data engineer gets data into the warehouse; an analytics engineer shapes it once it is there and works closer to the analysts who use it.
US government figures for database architects
- Median yearly pay, May 2025
- $139,500
- Expected change, 2025 to 2035
- 9.4% more jobsagainst 3.5% for all jobs
The government has no code for analytics engineers, so these figures are for the closest group, database architects, the same group we use for data engineers.
Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.
Job description
Who We Are:
Alpaca is a US-headquartered, global leader in agent-first brokerage infrastructure for stocks, ETFs, options, crypto, fixed income, 24/5 trading, and more.
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.
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.
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.
Our Team Members:
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!
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.
About the team & role
The Analytics Engineering team builds the warehouse that Alpaca runs on. It turns hundreds of millions of daily events from transactional databases, API logs, CRMs, payment systems, and marketing platforms into the datasets behind partner invoicing, regulatory reporting, executive KPIs, partner-facing products, and a growing number of AI agents.
As a Staff Analytics Engineer, you'll own the future of our warehouse: how it's modeled, how it performs, and how it's served. Working across Data Platform (who own infrastructure & ingestion), Data Scientists and business users (who consume your models), and leadership (who rely on your judgment to prioritize), you won't just build models. You'll define how the whole company models, tests, and serves trusted data, and raise the bar for everyone doing it.
Our team is 100% distributed and remote.
Responsibilities:
- Set the multi-quarter technical direction for the warehouse. This covers layering (staging, intermediate, marts), domain boundaries, materialization and incremental strategies, and the standards that keep more than 1,000 dbt models fast, testable, and cost-efficient as we grow 10x.
- Decide which models are served through ad hoc OLAP queries on the lakehouse, which belong in a real-time analytics engine for low-latency internal and partner-facing use, and which become governed metrics in a semantic layer.
- Agree on schemas, freshness SLAs, and change notification with source owners, and choose CDC or batch for each source based on what consumers need.
- Guarantee cent-level accuracy on financial data with tests, reconciliation, and write-audit-publish patterns that keep silent errors from shipping.
- Set org-wide standards for modeling, testing, and CI/CD, mentor engineers, and win alignment across teams. Your impact should show up in others' work.
- Prioritize work that moves metrics for finance, operations, and partners, and head off scaling, quality, and cost problems before they hit.
Must-Haves:
- 7+ years in analytics engineering or data engineering focused on transformation and warehouse architecture, with Staff-level leadership: setting direction and leveling up teams.
- Has led an org-level warehouse migration or redesign, such as a mart restructure, semantic layer rollout, or testing and CI overhaul.
- Deep query-performance expertise on distributed engines such as Trino, Presto, or Spark. This includes reading query plans, partitioning and file layout on Apache Iceberg, and incremental materialization.
- A clear point of view on when a dataset belongs in a lakehouse query engine, a real-time OLAP engine such as ClickHouse, or a semantic layer.
- Expert-level SQL and dbt, plus Python for transformations beyond SQL.
- Experience defining data contracts and freshness SLAs with upstream producers, and an understanding of the trade-offs between CDC and batch ingestion.
- Thrives in ambiguity. Can take a vague, high-stakes problem from 0 to 1 with minimal oversight.
Nice to Haves:
- Production experience modeling data for ClickHouse or another real-time OLAP engine.
- AI and agentic analytics: making data usable by LLMs and agents, building evals.
- Familiarity with Airflow, Airbyte, and CDC tooling such as Debezium or Redpanda.
- Brokerage or financial-markets domain experience.
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
Alpaca is proud to be an equal opportunity workplace dedicated to pursuing and hiring a diverse workforce.
Source details
Source notes
Source excerptsSelected passages from the saved posting. Check the full description for conditions and exceptions.
- Pay
No pay amount identified in the saved description.
- Location & working pattern
Remote - EMEA
As a Staff Analytics Engineer, you'll own the future of our warehouse: how it's modeled, how it performs, and how it's served. Working across Data Platform (who own infrastructure & ingestion), Data Scientists and business users (who consume your models), and leadership (who rely on your judgment to prioritize), you won't just build models. You'll define how the whole company models, tests, and serves trusted data, and raise the bar for everyone doing it. Our team is 100% distributed and remote. Responsibilities:
- Work authorization
No clear work-authorization passage found. Eligibility is unconfirmed.