Databricks careers run through one place: the open positions page on databricks.com, where every job page carries a standard Greenhouse application form. On 18 October 2026 Databricks' public Greenhouse board listed 898 open jobs, 485 of them with a US location, and 18 intern or new grad postings. This guide walks through that form question by question, breaks the openings down by team and country, sets out the interview loop in Databricks' own words, and shows the company's H-1B record from USCIS data. If you landed here looking for jobs that use Databricks rather than jobs at Databricks, skip to the last section, which covers the roles that list it and how to put it on a resume.
Working at Databricks, or jobs that use Databricks?
Search results for this term mix two different needs.
| You want | Start here |
|---|---|
| A job at Databricks, the company | The next five sections: where it posts, the form, open roles, early careers, interviews and sponsorship |
| A job at another employer that uses the Databricks platform | Jobs that use Databricks, with certifications and sample resume lines |
Where Databricks posts its jobs
Databricks lists every opening at
databricks.com/company/careers/open-positions.
Each job link ends in ?gh_jid= followed by a number, which is the Greenhouse
job ID. We loaded a job page in a browser on 18 October 2026 and confirmed that
the application form is an embedded Greenhouse form served from
job-boards.greenhouse.io/embed/job_app?for=databricks. The Greenhouse-hosted
board at job-boards.greenhouse.io/databricks redirects back to databricks.com,
so there is no second, separate board to check.
LinkedIn, Built In and Indeed show Databricks jobs too, but they are copies. Apply on databricks.com so your application lands in Greenhouse directly. For how Greenhouse boards work in general, see our guide to Greenhouse job boards.
The Greenhouse application, step by step
We pulled the application questions for 40 randomly chosen US postings from Databricks' public Greenhouse board API on 18 October 2026. The core form is short and the same across roles; about a quarter of the postings add a few questions of their own.
| Field | How often it appeared (of 40) | Required? |
|---|---|---|
| First name, last name, preferred first name, email, phone | 40 | Yes, on nearly all |
| Resume/CV (file upload or paste) | 40 | Yes, on 39 |
| Cover letter | 40 | Never required |
| LinkedIn profile | 39 | Required on 17 |
| Website | 31 | No |
| How did you hear about this job? | 35 | Required on 10 |
| Are you legally authorized to work in the country in which you are applying? (Yes or No) | 39 | Yes |
| Do you now or will you in the future need sponsorship for employment visa status? (Yes or No) | 39 | Yes |
| Do you currently or have you previously worked for Databricks? | 39 | Yes |
| Two sanctions and export control questions | 39 | Yes |
| Voluntary EEO self-identification section | 38 | Voluntary |
| Role-specific questions | 10 | Yes, where present |
What to prepare before you click Apply:
- A resume file. The form accepts an upload or pasted text, and a file keeps your layout intact.
- Your LinkedIn URL. It was required on a little under half the postings we checked, so have it ready either way.
- Your work authorization answers, settled once. The two questions are plain Yes or No. Answer them the same way on every Databricks posting.
- The export control answers. The first asks whether you are a citizen or resident of listed sanctioned countries or regions (with "None of the above" as an option). The form notes the information "will only be used to ensure compliance with U.S. sanctions and export controls." A follow-up about your citizenship or residency status applies only if the first answer was not "None of the above."
- For early career roles, transcripts. Every one of the 18 University Recruiting postings asked for a transcript, most also asked for your graduation date, and the US intern and new grad postings for software, product management and research also asked for GPA.
The extra questions are role-specific. Public sector postings in our sample asked whether you hold an active US government security clearance, and a payroll tax posting asked five questions, including long written ones about its work, so read the whole form before you start.
Databricks says you can apply to more than one role: "Yes! We encourage you to explore our Careers page," it says on its interview prep page, adding that you should make sure your resume "highlights the most relevant skills and experience for each position." After you submit, Greenhouse status tracking works the same as at any Greenhouse employer; see Greenhouse application status.
Open roles by team and location (18 October 2026)
All counts come from Databricks' public Greenhouse board on 18 October 2026. The board changes daily. A posting can list more than one office, so regional and country counts add up to more than 898.
By team (top-level department):
| Team | Open postings |
|---|---|
| Field Engineering | 222 |
| Engineering, pipeline postings | 145 |
| Sales | 134 |
| Professional Services | 125 |
| Engineering | 69 |
| G&A | 50 |
| Product | 37 |
| Executive Engineering, pipeline postings | 33 |
| Marketing | 23 |
| IT | 21 |
| University Recruiting | 18 |
| Customer Success | 10 |
| Security | 10 |
By country (top ten):
| Country | Open postings |
|---|---|
| United States | 485 |
| India | 92 |
| United Kingdom | 51 |
| Netherlands | 34 |
| Japan | 29 |
| Singapore | 29 |
| Germany | 29 |
| Australia | 25 |
| France | 22 |
| Canada | 20 |
The most common single locations were Bengaluru (75), "United States" with no city (69), San Francisco (67) and Mountain View (46), plus 37 postings listed for Mountain View and San Francisco together.
Two things the raw counts hide:
- Field roles outnumber engineering roles. Field Engineering, Sales and Professional Services together carry 481 postings, more than half the board. Field Engineering alone includes a Delivery Solutions Architects group with 32 postings.
- Some postings are old. 699 of the 898 were first published in 2026, but 199 were first published earlier, the oldest in 2019. Of the 178 postings in the two "pipeline" engineering departments, 122 were first published before 2026. Databricks does not explain the label publicly. A posting open that long may be filling more than one seat over time, so apply if it fits, but do not read its age as a sign that a decision is near.
Internships and new grad roles
The board listed 18 postings under University Recruiting on 18 October 2026. Searching titles for words like "intern" or "graduate" gives 28, but ten of those are false matches such as "Database Engine Internals" or "International Accounts Payable Manager," so use the University Recruiting department instead.
| Program | US postings | Outside the US |
|---|---|---|
| Software engineering intern (2027) | 2 (one also lists Vancouver; one is a winter start) | Aarhus, Amsterdam, Belgrade, Berlin, London |
| Product management intern (2027) | 1 | Amsterdam, Belgrade, Berlin |
| Product manager or associate PM, new grad (2027) | 1 | Amsterdam, Belgrade, Berlin |
| Product design intern and new grad (2027) | 2 | None |
| PhD GenAI research scientist intern | 1 | None |
Databricks' early careers page answers the timing questions directly:
- When: "The majority of our global interviews take place in line with local academic calendars, typically opening applications in August. We hire on a rolling basis, so we recommend applying as early as possible!"
- Where: interns and new grads are hosted in hub offices "including San Francisco, Mountain View, Bellevue, Amsterdam, Berlin, Belgrade and Bangalore."
- How long: "Most internships are either 12 or 16 weeks."
- Who: the page describes its ideal intern candidates as students "pursuing degrees in computer science or related fields who have a fundamental understanding of deep learning and are proficient in software engineering using PyTorch."
Since the 2027 cycle postings are already live in October 2026, applying now is well inside the window Databricks describes.
Interviews, from Databricks' own pages
Databricks publishes its process on its interview prep page. It lists seven stages: identifying opportunities, applying online, connecting with talent acquisition, skill assessments, interviewing, reference checks, and decision and offer.
| Question | Databricks' answer |
|---|---|
| How long does it take? | "Typically ranges from two to three months, depending on your role, region and the hiring team" |
| What are the rounds? | Recruiter call; a pre-onsite screen that "may include a hiring manager screen, technical assessment or skill evaluation"; an onsite loop that "typically consists of four to six interviews"; a presentation for some roles, "particularly go-to-market and executive positions" |
| In person or virtual? | "All interviews are conducted virtually unless your Recruiter specifies otherwise," on Google Meet |
| When is feedback? | "We aim to share interview feedback within 48 hours of your final interview"; if you hear nothing in a week, contact your recruiter |
The early careers page adds what each common interview tests. For software engineering: "Brush up on data structures and algorithms. We're evaluating code quality and cleanliness." For data science, data science fundamentals and coding "as they relate to data processing and manipulation." For product management, product fundamentals, with Databricks "evaluating your product skills and leadership." Back on the interview prep page, behavioral questions start with prompts such as "Tell me about a time" and "Describe a situation," and every candidate is evaluated "against the same core competencies." That page also links separate prep guides for engineering (including field engineering), product and sales.
One practical warning from the page: do not bring or use anything from your current employer, including for take-home assignments or presentations.
Sponsorship history from public data
We queried the USCIS H-1B Employer Data Hub on 18 October 2026 for the employer name DATABRICKS INC (tax ID ending 2184, San Francisco). The Data Hub counts workers on USCIS's first decision, by the fiscal year of the decision (1 October to 30 September), per its explanation page.
| Fiscal year | New employment | Change of employer | Continuation | Change with same employer | Amended | Total approvals | Denials |
|---|---|---|---|---|---|---|---|
| FY2024 | 81 | 87 | 75 | 2 | 38 | 283 | 0 |
| FY2025 | 70 | 103 | 1 | 45 | 118 | 337 | 0 |
| FY2026 (through Q3) | 83 | 133 | 1 | 34 | 65 | 316 | 1 |
Earlier years from the same source, total approvals only: 58 in FY2019, 58 in FY2020, 151 in FY2021, 230 in FY2022 and 200 in FY2023. In the Data Hub's ranking for FY2026 through the third quarter, Databricks Inc sat at number 72 among employers by approvals.
How to read it:
- New employment covers workers new to H-1B, whether they are abroad or changing from another status such as F-1. That is the column that matters most for students.
- Change of employer is H-1B holders transferring in from another company. It was the largest column in FY2025 and FY2026, so much of Databricks' H-1B activity is people transferring in from other employers.
- Denials are close to zero in all three years.
A sponsorship record does not mean every role sponsors. The form asks the sponsorship question on almost every posting, so answer it truthfully and read the posting. For the method behind this table and how to repeat it for any employer, see companies that sponsor H-1B.
Jobs that use Databricks, and how to show it on a resume
Many more jobs list Databricks as a skill than are posted by Databricks itself. The company's own certification program maps the platform to job families, which is a fair guide to the titles to search (Databricks certification):
| Role | What Databricks says the role does on the platform | Certification |
|---|---|---|
| Data analyst | Creates "queries, data visualizations and dashboards using Databricks SQL" | Data Analyst Associate |
| Data engineer | Builds and maintains "batch and streaming data pipelines" | Data Engineer Associate and Professional |
| Machine learning engineer | Develops, deploys and maintains "machine learning models and pipelines" | Machine Learning Associate and Professional |
| Generative AI engineer | Designs, builds and deploys generative AI solutions | Generative AI Engineer Associate |
| Spark developer | Works with the Spark DataFrame API | Associate Developer for Apache Spark |
The Data Engineer Associate exam costs $200, is multiple choice, can be taken online or at a test center, and is valid for two years (Databricks exam page). Free fundamentals badges are also available through on-demand training.
How to word it
Postings rarely say just "Databricks." They name components. Match the ones you have actually used, in the posting's own words:
- Delta Lake for tables and storage
- Unity Catalog for governance and access
- Lakeflow Jobs and Spark Declarative Pipelines for orchestration and pipelines
- Databricks SQL for analytics
- MLflow for model tracking and deployment
Sample resume lines, written for this post and not taken from a real person:
- Sample: "Built 12 batch and streaming pipelines on Databricks with Delta Lake and Lakeflow Jobs, cutting daily load time from 3 hours to 40 minutes."
- Sample: "Moved 200 tables into Unity Catalog and set row-level access for 4 analyst teams."
- Sample: "Tracked 30 model experiments in MLflow and deployed the selected model as a Databricks serving endpoint."
Put the platform name and the components in your skills section as well as in the bullets. List only what you can discuss in an interview. For how screeners and search use these terms, see resume keyword matching.
Where ApplyEze fits
ApplyEze is a desktop app that applies to jobs for you on your own machine, in a browser window you can watch. It completes applications on Greenhouse, the system behind every Databricks posting, along with Lever, Ashby, Workday, Workable, SmartRecruiters, Oracle Recruiting Cloud, JazzHR, BambooHR, Rippling, Pinpoint and Recruitee (Workday and Oracle need a connected application inbox). It writes a resume for each posting and a cover letter when the form asks for one. The resume mirrors the posting's language, and ApplyEze brings the posting's named skills and tools onto your skills line, even when your own record does not list them. There is no step to remove one before a live run, so use a dry run to see what it writes, and be ready to discuss anything on the page. A certification the posting asks for is not added unless you hold it. Your employers, job titles, dates, schools, degrees and certifications come from your own record, and code rejects a rewrite that adds a figure, employer, school or credential your record does not hold. Saved work authorization answers are reused. When a required question is not covered by them, ApplyEze still fills it rather than stopping the run, so that answer may not come from you. Fill in your saved answers, read your receipts, and start with a dry run, which fills the form without clicking Submit.