What three candidates report about interviewing for engineering roles at Swish Analytics: scheduling problems, a JSON-to-table take-home, a sports-interest question, and silence after submission.
$143K
Avg. Base Comp
$180K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidate reports on Swish Analytics engineering interviews are few, and they cover different roles. One is a software engineer, one a frontend developer and one a staff software engineer. Treat them as separate accounts rather than one standard process.
Scheduling is the most repeated theme. The software engineer candidate says their first interview was missed entirely and was rescheduled after about three days. The staff-level candidate says an interviewer cancelled three times, each within about five minutes of the start, and they withdrew before any interview took place. The frontend candidate also describes a phone screen rescheduled several times on the day. Confirm times in writing and keep your availability flexible.
The content that was reported is fairly light. The software engineer candidate says the rescheduled call covered a range of topics they felt comfortable with. It also included a question about whether they follow sports, so being able to say why the sports-analytics domain interests you is sensible preparation. That candidate also asked about bonus structure and got no details, so ask the recruiter about compensation and benefits early.
The frontend candidate describes a take-home that involved building a table from a provided JSON dataset. The written description of the expected output did not match the data. They built to the data and suggest stating your reasoning clearly in the submission. Expect to practice rendering and shaping JSON into tabular views.
After the interview or take-home, two candidates report little or no follow-up. One got a canned rejection after chasing, and the other got no reply after submitting. Send a polite follow-up, but don't count on a quick answer.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Swish Analytics process.
I never made it past scheduling with Swish Analytics, so this is more of a warning than an interview recap. After I applied online, an interviewer emailed me his calendar to set up a call. He canceled three times, each time within about five minutes of the start, and each time said he was out of the office. After every cancellation he asked me to reschedule. I understand that something urgent can come up once. But after I had already given my availability, three last-minute cancellations made it feel like my time wasn't being respected, so I decided to pass on interviewing there. If you're considering this company, I'd ask early how interviews are scheduled and whether the interviewers are reliably showing up.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Swish Analytics
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Top 3 Users | |
| String Shift | |
| Find Bigrams | |
| Total Spent on Products | |
| Last Transaction | |
| Raining in Seattle | |
| Size of Joins | |
| Minimum Change | |
| First Touch Attribution | |
| Job Recommendation | |
| P-value to a Layman | |
| Find the First Non-Repeating Character in a String | |
| Daily Retention Summary | |
| Find the Index with Equal Left and Right Sum | |
| Google Maps Improvement | |
| Type-ahead Search | |
| Delivery Estimate Model | |
| Detecting ECG Tachycardia Runs | |
| Decision Tree Evaluation | |
| Friendship Timeline | |
| Ranking Metrics | |
| Hurdles In Data Projects | |
| Type I and II Errors | |
| The Brackets Problem | |
| Third Purchase |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report unreliable scheduling: a missed first interview that took about three days to reschedule, an interviewer who cancelled three times within minutes of the start, and a phone screen rescheduled repeatedly on the day. Confirm the time in writing and expect that you may need to reschedule.
The software engineer candidate says the rescheduled interview covered a range of topics they were comfortable with, and included a question about whether they follow sports. The frontend candidate describes a friendly, responsive recruiter on the phone screen. Prepare to explain your background and your interest in sports analytics.
One candidate was sent a take-home asking them to build a table from a provided JSON dataset, with a write-up of the expected output. The task itself was not hard, but the documentation disagreed with the data. They built to the data and recommend noting any discrepancy and your reasoning in the submission. Other candidates did not mention a take-home.
Candidates report no offers. The software engineer candidate heard nothing for four days, then received a canned rejection after emailing. The frontend candidate says communication stopped after submission. Plan to send a follow-up message, and ask about compensation and benefits early, since one interviewer could not answer a bonus question.
