Senior Software Engineer — Spatial Analytics & Open Formats
CARTO
Software Engineering, Data Science
Spain
The role
Where you'd sit
- Department
- Engineering
- Employment Type
- Full Time
- Location
- Spain
- Workplace type
- Fully remote
What you'll lead
- The Analytics Toolbox framework. Shape how spatial analytics is packaged, versioned, and pushed down into partner engines — and what it looks like when the consumer is an LLM agent, not a UI.
- Partner-engine SQL strategy. Every engine has its own dialect, optimizer, and idioms. You'll set the direction for how CARTO writes once and runs everywhere, without losing warehouse-native performance.
- The Iceberg / open-format play. CARTO organized the 2021 meeting with BigQuery, Snowflake, Redshift, and Oracle that catalyzed GeoParquet, and authored RaQuet for raster in Parquet. Iceberg is next. You'll define what spatial-first Iceberg looks like — for CARTO and for the ecosystem.
- Community and standards presence. This work happens in the open. OGC working groups, the Cloud Native Geospatial community, FOSS4G, conference talks, RFCs. You'll represent CARTO externally and help move the standards forward.
- AI as a native execution surface. Agentic GIS is where we're going. The Toolbox isn't just a SQL library — it's the substrate AI agents call into. You'll help define that interface.
Who you are
- You've spent a serious chunk of your career in the cloud-native geospatial world. You've built with — and ideally helped shape — some combination of DuckDB, GeoParquet, STAC, Arrow, Iceberg, point cloud formats, MobilityDB, or similar. You don't just use these tools; you have opinions about where they're going.
- You know SQL at the engine level. You can read an execution plan across BigQuery, Snowflake, Redshift, and Databricks, and you have a clear view on what each one does well and badly for spatial workloads — partitioning, clustering, file pruning, pushdown, cost.
- You build with AI seriously. You've shipped LLM-powered features in production, you've worked with agentic patterns, and you have a point of view on what this changes for analytics.
- You're visible in the community — a FOSS4G or CNG talk, a maintained OSS project, a standards working group, a blog post people keep citing. Not vanity; this is how the role gets done.
- You're a low-ego technical leader. You set direction by being right and being persuasive, not by being loud. You give direct feedback in PRs, ask good questions when you don't know something, and make the engineers around you better.
- You're comfortable shipping production code — this isn't an architect-only role — in a cloud-native, serverless environment (GCP or AWS). TypeScript / Node.js experience is a plus since that's our backend, but it isn't the primary signal we're hiring on.
We offer
- Compensation based on experience, discussed transparently during the process plus an annual bonus of up to 10% based on company objectives
- Contribute to a platform used by top companies around the world. Your work will have a direct impact on our users and clients
- Access to our Employee Stock Options Plan
- Private Medical Insurance
- Flexible compensation
- Education stipend
- Remote work stipend
- English classes
About CARTO
Our Hiring Process
Screening
HM interview
Test
Second interview
Not quite right? Register your interest to be notified of any roles that come along that meet your criteria.

