Taro Logo

Senior Software Engineer Interview Experience - Remote, Oregon

March 1, 2019
Negative ExperienceNo Offer

Process

I was recruited to interview for the Senior Software Engineer and it was with an eye to my SRE and my leadership skills. They said many times they were looking for an SRE lead/Manager developer to join them and help flesh out an aspect of their team they were lacking in. Good news, that's me and I've done that before.

Thing is, that's not what I was actually applying for and the entire process was a waste of my time. I've read lots of negative reviews of their process that echoes mine and I want to hit a few points here to help you decide if Doximity is right for you to apply for. Reason being Doximity seems like a nice company with a very broken interview process such that it might be a complete waste of your time.

  1. You will be asked interview questions that are largely what I'd call "stump the nerd." They aren't questions that try to get at how you go about solving problems or how you've solved problems, they are questions about your ability to memorize tech minutiae.

For instance one question I got was "Do you know what Composite is?" My answer, was yes, it's a gang of four pattern, it's been a while since I thought about it can I google it. Answer: No, it's fine. That was A LOT of the questions. Frankly a better question is, "Have you heard of the software pattern Composite and can you tell me a time you've implemented it and why it was a good choice?" The reason why that is better is because you can know if they know what it is AND if they don't they can Google it and then let you know if they ever practically applied it to a scenario and why it was a good choice. Because at the end of the day if all your questions can be easily searched in Google as a definition of a term, you're simply testing if someone can take a simple test, not get at how they build maintainable software. I'll write out all the questions they asked me below and if you memorize them, you'll do well.

  1. The tech code challenge isn't related to the job in any fashion it seems and it takes way too long to do and no one reviews it or bases your interview performance on it. When I set out to finish a code challenge I set out to make it great, which often means spending a bit more time on it to make it shine. That said, the coding challenge isn't well defined and because of that you can spend a ton of time on it. The challenge was to design a game in Ruby and you had to reverse engineer some text output to figure out how it would work. That said, based on the focus of the interview questions it should be in JavaScript because they didn't really seem to interview me for a Ruby job, the majority of tech questions were JavaScript and the Ruby questions I was asked were very light. This sucks because my resume clearly shows I have been using Ruby since Rails 0.9. I really don't have a lot of JavaScript and that seems the clear focus of the job.

Another problem with the code challenge is that no one in the series of in-person video interviews reads it so when you want to come back to a question they are asking practically based on your work you can't. In the end, it seems none of their choice is based on the code you write simply your ability to memorize tech facts (Mostly JavaScript) and repeat them.

My suggestion here is to design a code challenge that tests what you are looking for. If you want to focus on JavaScript, don't make the code challenge in Ruby then ignore Ruby in the interview questions. If the code challenge was in JavaScript I would have passed on the job, as that's not my career focus to date.

  1. What they were interested in me for wasn't what I was interviewing for. The job description I was given was "Senior Software Engineer" but numerous people in the pipeline wanted me for my SRE background and leadership and former Management ability. I focused my interview from this perspective and during my discussion with the VP it entirely tanked me.

By the last interview the VP literally told me they couldn't place me based on the fact I was previously a Manager and "Doximity doesn't hire Managers." I don't have a problem with this statement or thought, but to get an interview process that takes SO much time and be tanked in the end by something written all over my resume is frustrating. I also talked about wanting to continue with SRE as a career focus and the VP said they weren't hiring for that when literally I was told they were by HR and later by others I directly talked to in the interview process.

Questions I got in the interview:

What is a left inner join? What are key characteristics of OOP? What is a Prototype language? What is an asset pipeline? What is Vue.js? What are the pros and cons of a monolith VS micro-service? What is something you don't like about Rails? What is something you'd add to Rails? What is the Composite software pattern? What is the SQL Group By function? What do I want to spend the next two years doing? How do I think about tests?

Questions

Here is how I would design an API.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Doximity Senior Software Engineer role in Remote, Oregon.

Success Rate

0%
Pass Rate

Doximity's interview process for their Senior Software Engineer roles in Remote, Oregon is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for Doximity's Senior Software Engineer interview process in Remote, Oregon.

Doximity Work Experiences