Seismic Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 124 interview experiences · FREE TO READ
Which role are you interviewing for?
30 roles · 124 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Seismic.
Seismic
Enterprise Account Director
Senior Difficult Positive experience Accept offer 5 rounds
Interview process
Recruiter call Phone screen Panel Presentation Offer
Interview formats
Behavioral Presentation Other
This hiring journey was pretty smooth and focused, taking about 2 weeks total from talking to HR to getting the contract signed. First, I chatted with the HR recruiter. Then, I spoke with the hiring manager, followed by the Regional Managing Director and the RVP of Customer Success. After that, there was a panel discussion with five topics to prepare for, including presenting Seismic's new narrative and sharing insights from my current role, like demonstrating a deal with a framework I prefer.
Confirmed questions1 question
- How can I prove my readiness?
Seismic
Implementation Engineer
Entry Average Neutral experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical Coding
First, there was a phone call with HR where they asked general questions about the role, my fit, the company's business, and expectations. Then, a technical round happened, which included SQL questions like finding users who opted out in the last 30 days. We also discussed REST vs GraphQL APIs, API versioning, and HTML status codes. Finally, there were behavioral questions focusing on client escalations and feedback.
Confirmed questions7 questions
- Phone call with HR involved asking generic questions about the role, role suitability, what the company does, what it is expecting, etc.
- Technical Round. Questions involving SQL (JOINS, INTERVAL, etc.). Ex question: Find the list of users who opted out in the last 30 days.
- REST APIs vs GraphQL APIs.
Seismic
Software Engineer
Mid Difficult Positive experience Accept offer 6 rounds
Interview process
Recruiter call Phone screen Technical screen Take home Technical screen Onsite
Interview formats
Behavioral Technical Coding System Design
The interview process was pretty long but felt fast, with about six or seven stages. It started with an HR chat to go over my application. Then, I talked to the team manager about my resume, projects, skills, achievements, and future goals. After that, the project manager and another engineer asked mostly behavioral questions. Then there was a timed online coding test, which I can't say much about. That was followed by a harder technical test with whiteboard questions, where I had to explain how I'd solve a problem from a broad and detailed perspective. It was tough but good. The last part was a quick chat with a senior technical manager.
Confirmed questions6 questions
- What are your technical skills?
- Can you complete this online coding assessment?
- Can you describe your approach to solving this problem at a high level?
Seismic
Software Development Engineer in Test
Senior Average Negative experience No offer 5 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Presentation
Interview formats
Behavioral Technical Presentation
So, Seismic's interview process was pretty long, with five rounds total. It started with a 30-min chat with the recruiter, then an hour with the hiring manager. After that, I talked to two team members for a 30-min technical round and another 30-min general interview. The last part was an hour with the director. Honestly, it was a mess. It felt super unorganized, and I couldn't get a clear picture of the role or what they really needed from QAs. The recruiter had no clue about the salary range, which was weird. And the director kept canceling and rescheduling our meeting, then totally ghosted me without even a sorry. Super unprofessional, made me feel like it wasn't the right place for me.
Confirmed questions1 question
- Can you describe a time when...
Seismic Interview Questions
Quoted word for word from Seismic interview reports.
“Can you code a simulation for two players playing the "War" card game, using any programming language?”
Read reports →“Can you explain what a terraform state file is and how one should be maintained?”
Read reports →“What would be involved in migrating from Azure to AWS or GCP, and what are the pros and cons of each choice? Also, what if we decided to use multiple cloud providers simultaneously?”
Read reports →“Would you say a micro-service architecture is superior to a monolithic one?”
Read reports →“What would you do if we ghosted you and wasted your time?”
Read report →“Can you detail the metrics you track for clients and the frequency of your reporting?”
Read report →“Can you tell me about an app with great UX and one with poor UX?”
Read report →“How do you decide what features to build next for a product?”
Read report →“Could you design a basic system based on the use cases provided?”
Read report →Formats, difficulty and experience
Across all 124 Seismic interview reports.