Cray Interview Questions (2026)
1 experiences · GeeksforGeeks (1)
Top topics
1 entry
Interview Experience
This article will give you information about the company, their recruitment process,
sample questions that have been asked previously, lots of experiences shared by other aspirants, and the portal where you can apply. Cray Recruitment Process Table of Content About Company: Recruitment Process: Cray Eligibility Criteria:
Online Assessment
Coding Technical Round:
HR About Company: Cray Inc. was acquired by Hewlett-Packard Enterprise in 2019. We are inspired by visionaries' insatiable curiosity, which never stops them from asking questions that push the boundaries of what is imaginable. Cray is willing to work with anyone who is willing to see beyond the apparent in order to push the boundaries of what can be accomplished, learned, or solved. Cray offers the most advanced and creative supercomputing capabilities for people who question what if, why not, and what's next. Recruitment Process: Online Assessment Coding Round Technical Round HR Cray Eligibility Criteria: Graduation (B.E B.TECH)CS/ IT/ ECE
Online Assessment Aptitude, Verbal, Technical, Coding, etc.
Coding 2 -3 Coding Questions on Data Structures and Algorithms and Discuss Projects.
Technical Round: Questions on Computer Science Concepts etc.
HR Why did you decide to apply to this role? Tell me about this gap in your resume. What are your salary expectations? What did you like most about the job description? Interview Experience: It is always beneficial if you know what it is to be there at that moment. So, to give you an advantage, we provide you with Interview Experiences of candidates who have been in your situation earlier. Make the most of it. Cray Interview Process Questions Asked in Cray: Remove loop in Linked List Detect cycle in a directed graph Mirror Tree Minimum number of jumps to reach end Quick Sort Where to apply: Cray LinkedIn Cray Career Page
Topics
Related companies
Cray Interview Process Overview
The Cray interview process typically includes a recruiter screen, one to two technical phone screens, and a 4-6 round on-site or virtual on-site loop. Each round serves a distinct calibration purpose: coding rounds measure correctness, code quality, and complexity reasoning; system design rounds measure architectural judgment at the appropriate level; behavioral rounds measure ownership, leadership scope, and collaboration. Reports tagged on LeakCode from 2024-2026 show Cray runs a calibrated process consistent with industry norms for companies of its tier.
Difficulty calibration: Cray coding rounds typically run medium difficulty with follow-up depth as the senior discriminator. System design rounds expect production-grade trade-off articulation at L4+ levels. Behavioral rounds expect quantified outcomes ("reduced p99 latency from 800ms to 120ms") rather than vague impact claims. The candidates who advance consistently demonstrate clear thinking out loud rather than perfect final answers.
How To Use Cray Question Reports
Real candidate-reported interview questions are a calibration tool, not a memorization target. Cray updates its question pool every 2-4 months; memorizing exact problems risks misleading you when the interviewer uses a variant. The high-leverage approach: identify the patterns that appear repeatedly in Cray reports, practice those patterns on similar (not identical) problems, and use the reports to understand the interviewer's typical follow-up depth.
Filter the questions above by round type, difficulty, and recency. Focus first on reports from the past 6-12 months; older reports may reference questions that have since rotated out of Cray's pool. Reports tagged with quantified difficulty and explicit round type are higher-signal than reports without those tags. The metadata filters help you build a focused study plan in 1-2 hours rather than 8-10 hours of unstructured browsing.
Common Cray Interview Mistakes
Reports tagged "no hire" at Cray consistently surface a few patterns: jumping into code without clarifying requirements, coding silently for extended periods, missing edge cases (empty input, single element, large input, overflow), producing working code the candidate cannot refactor when probed, and behavioral stories that use "we" instead of "I" diluting individual signal. Strong candidates explicitly avoid these patterns by following a consistent round template.
The single most predictive failure mode in recent reports: not asking clarifying questions. Interviewers are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into implementation immediately. Strong candidates also verbalize their approach before writing code; weak candidates code in silence and lose the communication dimension of the round's calibration.