2

Remote Databricks Developer Jobs in Georgia (NOW HIRING)

Data Engineer

Atlanta, GA ยท On-site +1

$110K - $132K/yr

... DevOps, and Dynamics 365 data integration initiatives. The Exponential Technology Group (XTG) is a ... This opportunity is remote with the ideal candidate being located in DFW, Phoenix, Atlanta or ...

... Developer solutions to industry giants including Delta, Google, Apple, Spotify, US Bank, FedEx, and ... Support, even from afar, with our remote assistance. Regular salary reviews? You betcha! Ready to ...

... Developer solutions to industry giants including Delta, Google, Apple, Spotify, US Bank, FedEx, and ... Support, even from afar, with our remote assistance. Regular salary reviews? You betcha! Ready to ...

Staff Machine Learning Engineer

Atlanta, GA ยท On-site +1

$220K - $280K/yr

... Databricks, or SageMaker. * Strong Coding Skills: Expert in Python and SQL; proficiency in Go, C ... S. and are willing to consider remote candidates. #LI-Remote Working at PrizePicks: The typical ...

Staff Machine Learning Engineer

Atlanta, GA ยท On-site +1

$220K - $280K/yr

... Databricks, or SageMaker. * Strong Coding Skills: Expert in Python and SQL; proficiency in Go, C ... S. and are willing to consider remote candidates. #LI-Remote Working at PrizePicks: The typical ...

$125K - $130K/yr

Experience with Databricks, Snowflake, Redshift, dbt, or other similar data engineering tools The ... Remote At Astronomer, we value diversity. We are an equal opportunity employer: we do not ...

Data Platform Engineer

Atlanta, GA ยท On-site +1

$110K - $132K/yr

... BigQuery, Databricks) * Familiarity with DevOps practices: CI/CD, containerization (Docker ... All Remote Hires - will be required to travel to Orlando, Florida at least twice per year for Town ...

next page

Showing results 1-20

Remote Databricks Developer information

What are the key skills and qualifications needed to thrive as a Remote Databricks Developer, and why are they important?

To thrive as a Remote Databricks Developer, you need strong expertise in data engineering, programming languages like Python or Scala, and experience with big data frameworks, typically supported by a degree in computer science or a related field. Proficiency with Databricks platform, Apache Spark, cloud services (such as AWS or Azure), and relevant certifications like Databricks Certified Associate Developer are commonly required. Strong problem-solving, communication, and self-motivation are crucial soft skills for remote collaboration and project delivery. These skills and qualities ensure efficient development, scalable data solutions, and effective teamwork in distributed environments.

What is the difference between Remote Databricks Developer vs Data Engineer?

AspectRemote Databricks DeveloperData Engineer
Required SkillsProficiency in Databricks, Spark, Python, SQLProficiency in data pipelines, ETL, cloud platforms, SQL
Work EnvironmentCollaborates on data projects using Databricks platformBuilds and maintains data infrastructure across cloud environments
CertificationsDatabricks certifications often preferredCloud certifications (AWS, Azure), data engineering certifications

While both roles involve working with data and cloud platforms, a Remote Databricks Developer specializes in developing solutions within the Databricks environment, focusing on Spark and data analytics. A Data Engineer has a broader scope, designing and maintaining data pipelines and infrastructure across various platforms. The roles overlap in skills like SQL and cloud knowledge, but their primary focus and tools differ.

How does a Remote Databricks Developer typically collaborate with cross-functional teams while working from different locations?

Remote Databricks Developers often work closely with data engineers, data scientists, and business analysts through virtual collaboration tools like Slack, Jira, and Zoom. Since team members may be distributed across various time zones, clear communication, regular stand-up meetings, and thorough documentation are essential for ensuring alignment on project goals and deadlines. Developers are also expected to participate in code reviews and shared knowledge sessions to maintain coding standards and support a collaborative environment. This structure helps ensure that complex data solutions are delivered efficiently and meet business requirements.

What is a Remote Databricks Developer?

A Remote Databricks Developer is a software professional who specializes in building, managing, and optimizing data pipelines and analytics workflows on the Databricks platform, while working from a remote location. They use Databricks, which is based on Apache Spark, to process large datasets, develop ETL processes, implement machine learning models, and collaborate with data teams. Their responsibilities often include writing code in languages like Python, Scala, or SQL, integrating with cloud services, and ensuring data quality and security. Working remotely, they communicate with teams online and use cloud-based tools to complete their tasks efficiently.
What are the most commonly searched types of Databricks Developer jobs in Georgia? The most popular types of Databricks Developer jobs in Georgia are:
What job categories do people searching Remote Databricks Developer jobs in Georgia look for? The top searched job categories for Remote Databricks Developer jobs in Georgia are:
What cities in Georgia are hiring for Remote Databricks Developer jobs? Cities in Georgia with the most Remote Databricks Developer job openings:
Senior Software Engineer - Spatial Analytics & Open Formats

Senior Software Engineer - Spatial Analytics & Open Formats

Carto

Spain, SD โ€ข Remote

$100K - $131K/yr

Full-time

Medical

Re-posted 13 days ago


Job description

Everything happens somewhere - which is why spatial analytics is fundamental to companies trying to understand the "where" and the "why" of their business. CARTO is the world's leading cloud-native spatial analysis platform, trusted by data scientists, analysts, and developers from global brands like IKEA, Coca-Cola, T-Mobile, Swiss Re, and AXA to run scalable spatial analysis directly on their cloud data warehouses and lakehouses.
Built by a diverse team of over 150 people across the US, APAC, and Europe (backed by Insight Partners, Accel Partners, Salesforce Ventures, and Earlybird Ventures), CARTO is fundamentally changing how location data is analyzed - making it an integrated, accessible, AI-native part of modern data infrastructure.

The role
Spatial analytics is moving out of the GIS silo. It's moving into the warehouse, then into the lakehouse, then into Iceberg and open formats, and increasingly into agentic workflows where the consumer is no longer always a human. We're looking for an engineer who has been part of building that shift, to come help us lead where it goes next at CARTO.
This role sits across CARTO's Analytics Toolbox and Workflows - the two surfaces through which our spatial analytics runs on partner engines (BigQuery, Snowflake, Redshift, Databricks, Postgres, Oracle) and, increasingly, on open formats consumed by external agents and applications. You'll define how the Toolbox framework evolves, how analytics capabilities are deployed across heterogeneous engines, and how CARTO plugs into the cloud-native geospatial stack - GeoParquet, STAC, Arrow, Iceberg, RaQuet, and what comes next.
We don't think of this as a feature-shipping role. We think of it as a vision-and-execution role: someone who can write the strategy doc and own the PR that proves it works.

Where you'd sit
You'd work alongside the Workflows team (backend, frontend, data engineering, QA - six people today, growing) and the broader Spatial Analytics group, with significant scope to shape the technical direction of both.
This is a remote-first role open to candidates based anywhere in EU or USA.ย 
  • 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.

  • 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.

  • 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