Swish Analytics logo

Swish Analytics Interview Questions
& Process

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

Based on 32 interview experiences · FREE TO READ

2.6 Rounds average
Average Typical difficulty
25% Positive experience

Which role are you interviewing for?

7 roles · 32 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Swish Analytics.

Showing 4 of 32
Swish Analytics logo
Swish Analytics

Software Engineer

Engineering · a year ago

Staff Average Negative experience No offer 3 rounds
Interview process
Recruiter call
Interview formats
Behavioral

I applied online at Swish Analytics, and then a recruiter emailed me to schedule a call. He sent his calendar, but the interview never happened because he canceled last minute, within 5 minutes each time, saying he was out of office. This happened three times, and each time he asked to reschedule. While I get that things happen, canceling three times after giving availability is pretty unprofessional and disrespectful of my time. If this is how the company culture is, I'm going to pass on interviewing.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

Swish Analytics logo
Swish Analytics

Frontend Developer

Engineering · more than a year ago

Entry Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Take home
Interview formats
Technical

The interview process was pretty bad. I got a call about a week ago and we set a time, but the interviewer rescheduled about 3 times on the same day. He was usually responsive though and communicated well, answering most of my questions. They gave me a take-home assignment to create a table from some JSON data. The assignment itself wasn't hard, but the documentation had an error. When I emailed to point out the error, the response seemed like they didn't read or understand my message, so I dropped it. After I submitted my project and asked about next steps, their responsiveness completely stopped. No reply, no call, nothing. The abrupt stop in communication after I submitted the project makes me think this is intentional and just how they operate, which is unprofessional. This pattern of rescheduling and then ghosting seems common based on other reviews. I wouldn't recommend interviewing with them. It feels like they're just collecting projects.

Confirmed questions1 question
  • Could you create a table using the provided JSON data, being mindful that the accompanying documentation might contain an error?
Swish Analytics logo
Swish Analytics

Data Scientist

Analytics · more than a year ago

Entry Average Negative experience No offer 2 rounds
Interview process
Take home Recruiter call
Interview formats
Technical

Recruiter reached out, had me do the same thing everyone else is posting about, predicting the next pitch from an MLB data set. I built a top notch jupyter notebook, then after, came here and saw that no one makes it past this stage. Made me regret putting in 8 hours of solid work into this notebook. The recruiter reaches out, says they are moving on with other candidates. Im fairly sure that they are just idea farming. Regardless the company is extremely disrespectful towards others time as they ask you to do a test and move on with pretty much no one. Don't waste your time on the test.

Confirmed questions1 question
  • Can you predict the next MLB pitch from 2011 data?
Swish Analytics logo
Swish Analytics

Data Engineer

Engineering · more than a year ago

Entry Average Positive experience No offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Behavioral Coding

I went through two interviews and had to do a coding assignment. The first interview was more about general fit and personality to see where I would fit technically within the company. After that, I was given a take-home coding assignment that was pretty cool. They said they'd review it and let me know in a few days, and they did, about 4-5 days later, calling me for a second, more technical interview. Unfortunately, I didn't get an offer because my experience wasn't quite what they needed at the moment. They were really professional though, and gave me feedback on my interview. Even though it didn't work out, I'd still recommend applying; they were fast, honest, and seem like good people to work with.

Confirmed questions1 question
  • Can you tell me about your experience with MySQL databases?

Swish Analytics Interview Questions

Quoted word for word from Swish Analytics interview reports.

Create a table that displays an array of objects from a given file, with filtering capabilities for three different variants and a search bar for two variants, along with an indicator for suspended values.

Read reports

Could you build a model to predict pitch type from MLB pitch data?

Read reports

Can you predict what type of pitch will be thrown next in Major League Baseball?

Read report

Build a production-ready modeling pipeline for predicting a certain event.

Read report

Could you explain the concepts of L1 vs. L2 regularization?

Read report

Could you create a table using the provided JSON data, being mindful that the accompanying documentation might contain an error?

Read report

Could you create a predictive model for pitching type in baseball?

Read report

Formats, difficulty and experience

Across all 32 Swish Analytics interview reports.

Interview formats

Technical 40%
Coding 26.7%
Behavioral 25%
Case 3.3%
Presentation 3.3%

Interview difficulty

Easy 12.5%
Average 68.8%
Difficult 18.8%

Candidate experience

Positive 25%
Neutral 18.8%
Negative 56.2%

Reports by job function

Analytics 15
Engineering 14
Operations 2
Product 1