Elastic interview, from the CodeSignal test to the panel.

The stages and durations below are Elastic's own, from its How We Hire page; the CodeSignal detail and the order engineers report are from candidate reports, read as search snippets on 5 October 2026.

Elastic says some roles take a technical assessment of 60 to 90 minutes: an online skills test, a portfolio review, or a coding problem solved in a set time while a proctor observes. Engineers report the online test runs on CodeSignal. A graduate candidate reported four questions in 70 minutes; a senior candidate asked about a 55-minute assessment; another senior candidate reported a hiring manager call, then a coding challenge, then a technical conversation. The questions themselves are rarely reported, so the items below are about how to take the test. Calibrd cannot rehearse a timed CodeSignal test for you. It can prepare the technical conversation and the values interviews that follow it.

• Four questions, rising in difficulty: Candidates describe CodeSignal tests in general as starting easy and getting harder. Bank the first two quickly and cleanly, then spend most of the time on the third and fourth, and submit working code before you try to improve it.
• Read the whole problem before typing: Most lost time comes from a misread input format. Check the constraints for size limits, since they tell you whether a simple loop is enough or you need a hash map, sorting or a heap.
• Practise in Java or your strongest language: Elasticsearch is almost entirely Java and the postings ask for strong core Java, but the test lets you choose. Use the language you are fastest in, and know its standard library for maps, sorting and string handling without looking anything up.
• The observed coding exercise: Where a proctor watches, narrate as you go: restate the problem, say your plan, and test with a small example out loud. Elastic says the exercise is about solving a problem within a time frame, so a working solution with a clear explanation beats an unfinished clever one.
• No AI during the test or the interviews: Elastic's July 2026 policy allows AI for preparation and proofreading and asks that interviews stay human-to-human without AI tools, and it says it uses AI monitoring tools in hiring. Misrepresentation found during hiring means disqualification. Prepare with AI, then sit the test alone.
• Then the technical conversation: Candidates report a technical round with one or two engineers from the team after the test. Expect to discuss your past work and the team's area in depth, such as search, storage, cloud infrastructure or security. This is the round to rehearse aloud.

Practise on a timer: four medium array, string and hash map problems in 70 minutes, twice, in the language you will use. Then rehearse two project stories for the technical conversation and one story for each of three Source Code values.

Elastic's values are called the Source Code, nine short lines written in its own format. Department interviews probe them, and Elastic's interview tips tell you to study them.

• CUSTOMER, 1ST: customers and the community are at the heart of the work
• HOME, DINNER: work fits around life, by design
• SPACE, TIME: room to think and dream takes conscious effort
• IT, DEPENDS: making things simple is complicated, and Elastic expects nuance in answers
• PROGRESS, SIMPLE PERFECTION: an Elastic that moves is an Elastic that survives
• 01.02, /FORMAT: a distributed Elastic is a diverse Elastic, and a better one
• AS YOU, ARE: everyone comes in different shapes and everyone has an accent
• HUMBLE, AMBITIOUS: ambition to do better, held with humility
• SPEED, SCALE, RELEVANCE: fast results that work at scale and matter to users

Candidates report the format more than the questions, so the behavioural rows below are built from the Source Code and from what Elastic's postings ask of a distributed engineer, and the technical rows follow the reported rounds.

Starting ranges from Elastic's own US job ads on its Greenhouse board, read 5 October 2026. Engineering and product ranges are base salary with no variable pay, plus eligibility for Elastic's stock program and a 401k matched up to 6 per cent. In select locations, including Seattle, Los Angeles, the San Francisco Bay Area and the New York City metro area, a higher range applies: $159,900 to $252,900 for senior engineers and $191,900 to $303,500 for principal engineers. The enterprise account executive ad splits its on-target earnings into $113,300 to $179,200 base and $113,200 to $179,100 variable target; inside and territory account executives post $131,100 to $207,300 OTE.

1. Read Elastic's How We Hire page, the July 2026 AI interview policy and the Source Code page; the interviewers expect you to know all three.
2. Do two timed CodeSignal-style sets of four problems in 70 minutes, in the language you are fastest in, without AI.
3. For Elasticsearch roles, refresh core Java, concurrency and the basics of inverted indexes, shards and relevance scoring.
4. Prepare a story for 01.02, /FORMAT about getting work done in writing across time zones, plus stories for CUSTOMER, 1ST and PROGRESS, SIMPLE PERFECTION.
5. Sales and solutions candidates: build a 30-minute discovery-led presentation with a short demo and a clear close, then rehearse it under 45 minutes.
6. Check the pay range in the ad for your location before the recruiter screen; Elastic posts it.

This guide covers Elastic's engineering, product and sales hiring; Elastic says the technical assessment and the panel presentation apply only to some positions, so ask the recruiter which yours includes. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.

Also interviewing at Shopify, PostHog or GitLab? Their guides follow the same format, from the first screen to the offer.

• 01Elastic, How We Hire (read 5 October 2026)the stages and durations: recruiter screen of 30 minutes, department interviews of 45 to 90 minutes, panel presentation of 45 to 90 minutes, technical assessment of 60 to 90 minutes, the proctored coding exercise, and the interview tips.
• 02Elastic, AI guidelines for the interview process (16 July 2026)AI allowed for preparation and proofreading, conversations kept human-to-human without AI tools, AI monitoring in hiring, and disqualification for misrepresentation.
• 03Elastic, Our Source Code (read 5 October 2026)the nine values as named, including 01.02, /FORMAT on distributed work.
• 04Elastic careers (read 5 October 2026)employees working remotely in over 40 countries plus 25 offices, and distributed by design.
• 05Elastic, fourth quarter and fiscal 2026 results (28 May 2026)fiscal 2026 revenue of $1.739 billion, up 17 per cent, for the year ended 30 April 2026.
• 06Elastic, Form 10-K for fiscal 2026 (filed 8 June 2026)4,019 employees in over 40 countries as of 30 April 2026, and the company distributed by design.
• 07Elastic job board on Greenhouse (read 5 October 2026)396 postings under 206 titles, the counts by title and location, the Java and asynchronous collaboration requirements, and the posted US pay ranges.
• 08Glassdoor, Elastic Graduate Software Engineer interview question (snippet read 5 October 2026)reported: a CodeSignal test of four questions in 70 minutes.
• 09Glassdoor, Elastic Senior Software Engineer interviews (review of 19 August 2026, snippet read 5 October 2026)reported: a hiring manager call, then a coding challenge and a technical conversation.
• 10Blind, Elastic senior developer interview thread (5 May 2025, snippet read 5 October 2026)reported: a 55-minute online assessment for a senior developer role.
• 11Reddit r/elasticsearch, Interview at Elastic (snippet read 5 October 2026)reported: three or four interviews, with a technical one with one or two engineers depending on the team.
• 12Glassdoor, Elastic Account Executive interviews (snippet read 5 October 2026)reported: a presentation of about 45 minutes, with the recruiter setting out the process first.

Interview processes change. This reflects widely-reported and sourced conditions as of 2026 — confirm specifics with your recruiter, and treat it as a map rather than a guarantee.