Wolfram Research logo

Wolfram Research Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 74 interview experiences · FREE TO READ

2.6 Rounds average
Average Typical difficulty
52.1% Positive experience

Which role are you interviewing for?

25 roles · 74 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Wolfram Research.

Showing 4 of 74
Wolfram Research logo
Wolfram Research

Technology Engineer

Engineering · more than a year ago

Mid Difficult Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Take home
Interview formats
Technical Coding

The first interview went well, but I was informed about several upcoming rounds and a technical challenge. The second round was very technically demanding. The challenge itself was manageable if you were already familiar with their coding language; otherwise, it would be nearly impossible given the one-week deadline. The challenge involved several questions that were heavily focused on coding, math, and research. After waiting for the results, I had to follow up multiple times with the team to get an update. Unfortunately, I was not selected, and when I asked for feedback, they were unhelpful, just reiterating their decision. Given the low compensation for an independent contractor role (with only salary and no other benefits), I don't think it's worth your time.

Confirmed questions1 question
  • Can you describe the time complexity of your process, such as if it's linear or squared?
Wolfram Research logo
Wolfram Research

Technology Engineer

Engineering · more than a year ago

Entry Average Positive experience No offer 1 round
Interview process
Recruiter call Phone screen
Interview formats
Behavioral Technical

The interview was on the phone and started exactly on time. It was pretty straightforward, mainly asking about past work, projects, and schooling. Even though it seemed like a few questions, they really wanted to hear about customer service experiences too, based on what the job needs.

Confirmed questions3 questions
  • Could you share details about projects you've completed that showcase your coding abilities?
  • Can you elaborate on your past employment, projects, and educational background?
  • Do you have any experiences related to customer service you'd like to share?
Wolfram Research logo
Wolfram Research

Math Developer

Engineering · more than a year ago

Mid Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical Coding

I had three meetings with them. First two were with HR and the manager I'd be working with. The third was a technical meeting where I had to do a coding challenge and then review it with the manager. Everything went pretty well, the manager seemed impressed with my coding work. After that, HR just went radio silent. It's been 3 months and I still haven't heard anything, no clue why. Not even an automated rejection email after three interviews.

Confirmed questions3 questions
  • What were the usual questions asked?
  • Could you complete a coding challenge?
  • Would you be able to review the coding challenge with the manager?
Wolfram Research logo
Wolfram Research

Software Engineer

Engineering · more than a year ago

Entry Easy Negative experience No offer 3 rounds
Interview process
Technical screen Take home
Interview formats
Coding Technical Behavioral

For software engineering jobs, you'll do coding challenges, which is pretty standard. After that, there are usually 2-3 more interviews that can stretch out over a month. They might not hire you in the end, not because your code wasn't good, but due to shifts in their project roadmaps. So, the Wolfram Language and Java coding you did could be a waste. The interviews themselves aren't too hard, but they can easily change their minds and pull your application. I'd recommend looking at companies with faster hiring processes. For me, it actually worked out better since I got a job offer from Qualcomm two weeks later, so no regrets. I'm definitely not considering Wolfram for future employment.

Confirmed questions6 questions
  • Could you discuss some behavioral questions?
  • How do you approach solving problems?
  • Can you describe your experience with debugging code?

Wolfram Research Interview Questions

Quoted word for word from Wolfram Research interview reports.

Can you tell if two strings are permutations of each other?

Read reports

Write code to create a set of JavaScript buttons, attaching event handlers to them programmatically within a loop.

Read reports

How would you determine if a number is prime given a very large range, such as from 1 to 1001?

Read reports

Can you compare two strings and identify which one has a greater number of unique characters?

Read report

Can you write a program to check if a tree is a sum tree?

Read report

Can you explain how to use SVD to build a neural network for classifying hand-written digits?

Read report

How would you verify if a solution to a heat equation is correct?

Read report

Formats, difficulty and experience

Across all 74 Wolfram Research interview reports.

Interview formats

Behavioral 39.3%
Technical 33.1%
Coding 18.6%
Presentation 5.5%
Other 2.1%

Interview difficulty

Easy 33.8%
Average 56.8%
Difficult 9.5%

Candidate experience

Negative 19.2%
Positive 52.1%
Neutral 28.8%

Reports by job function

Engineering 51
Operations 5
Research 4
Other 4
Design 3
Sales 3