Swish Analytics logo

Swish Analytics Frontend Engineer Interview Questions
& Process

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

Based on 6 interview experiences · FREE TO READ

2.3 Rounds average
Easy Typical difficulty
16.7% Positive experience

Candidate interview experiences

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

Showing 3 of 6
Swish Analytics logo
Swish Analytics

Frontend Developer

Engineering · more than a year ago

Entry Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical Coding

The first call with the recruiter was okay, they asked me some questions to see if I knew React. Then, for the technical interview, I had to build a data table component and work with some data from JSON files. It was a pretty long task, taking about 4-5 hours. There was a mistake in the instructions, and I didn't hear back for 7 days after asking for help. When they finally responded, I asked if I could still get clarification, and also mentioned that I had already submitted the assignment because of the 1-week deadline. I got an email saying I didn't get the job the next morning, with no explanation.

Confirmed questions1 question
  • Can you tell me about the charting libraries you've used?
Swish Analytics logo
Swish Analytics

Front End Developer

Engineering · more than a year ago

Entry Easy Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Background check
Interview formats
Technical Coding

The interview process was extremely unsatisfactory. It took four emails to finally schedule the initial interview. On three separate occasions, my interviewee was either late or failed to show up. Following that, they sent me a "3-hour" developer assessment, which actually took much longer to complete due to inadequate instructions and poor communication skills within the team. After I submitted the assessment, I received no response; I was essentially ghosted. When I sought feedback, I received an automated response. Overall, this process was highly inhumane, unprofessional, and disrespectful.

Confirmed questions1 question
  • 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.
Swish Analytics logo
Swish Analytics

Front End Developer

Engineering

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

Had a screening call, pretty easy. Then a take-home project, also easy. After that, an interview with the engineering team, which was more behavioral. Finally, a technical interview to wrap things up.

Confirmed questions2 questions
  • What kind of engineering do you find enjoyable?
  • Which projects do you prefer working on?

Swish Analytics Frontend Engineer 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 create a table using the provided JSON data, being mindful that the accompanying documentation might contain an error?

Read reports

Can you introduce yourself and walk me through your experience?

Read report

Formats, difficulty and experience

Across all 6 Swish Analytics interview reports.

Interview formats

Behavioral 36.4%
Technical 36.4%
Coding 18.2%
Other 9.1%

Interview difficulty

Easy 50%
Average 50%
Difficult 0%

Candidate experience

Positive 16.7%
Negative 66.7%
Neutral 16.7%