Medidata Solutions Interview Questions
& Process

I went through four interviews and a technical test for a role I was clearly overqualified for — only to be told after all that effort that the team had hoped to upgrade the position to a more senior level... but hadn’t actually secured approval. That crucial detail was kept quiet until the very end, when the plan fell through and I was suddenly offered the lower-level role instead. When I tried to negotiate a salary that reflected my experience, the door was slammed shut with no discussion. I asked for a delayed start date — again, instantly rejected. What made it worse was the contrast between the messaging and reality. They spent a lot of time talking about culture, flexibility, and onboarding people the “right way” — but the moment I pushed for even basic flexibility, the corporate mask came off. This wasn’t just a case of poor communication — it felt like a deliberate lack of transparency that wasted my time and left a bad taste. I expected better from a company of this size and reputation. If you’re experienced, be cautious — the process may look collaborative on the surface, but the decision-making is anything but.

The interview process was really thoughtful and efficient, totally aligned with what they expect for the role. First, there was a recruiter call to introduce the company, team, and process. Then, a panel interview with two senior engineers where we talked about my past experience, architectural choices, and how I handle technical challenges. It was in-depth but felt conversational, focusing on how I solve problems and fit into a team. After that, a technical deep dive specifically on React, including live coding and discussions on component design, state management, and performance optimization. The final round was a strategic chat with a senior director about engineering culture, team fit, and aligning with the company's mission for scalable, human-centered tech. We also touched on CI/CD, testing, and agile. It was great because everyone was welcoming, the process was structured and focused on skills, values, and collaboration, and they were transparent throughout. The only small hiccup was a bit of waiting between stages, but communication was good.

The interview process started with an initial meeting with the hiring manager, which was great because I'd met them before for a different position. Next up was a panel interview. It was mostly fine, but one panelist was pretty rude and nobody stepped in. To be honest, I felt some misogyny from one of them who questioned my resume and basically implied I was lying, even though all the info about the job and company was clearly on there. They seemed to think they'd caught me out, but they hadn't. This happened at the beginning, but I still managed to answer every question they threw at me really well, getting positive feedback on each answer. Despite that, I didn't move forward. It also took them 3 weeks to get back to me, and I had to follow up a few times. Apparently, this is a common thing with them, as it took 8 weeks for another role I applied for. Because of this panel interview experience, I won't be applying to any more jobs at Medidata, which is a shame because I'd heard good things before.

It was a pretty unprofessional experience. There were 2 rounds, a week apart. I was given a time and a Google Meet link and rearranged my schedule to make it work. I waited on the link for the entire hour for the interview, but they never showed up. I emailed them and didn't get a response for a while. I still attended the second round and met a nice guy who was interested in what I had to say, but he couldn't ask many questions because I hadn't done the first round yet. When they rescheduled the first interview, the interviewers acted like I was a major inconvenience and were not friendly at all. I did a live Python coding problem while screen sharing, and they said my solution was incorrect because one of them didn't read the prompt correctly. They asked me to do a SQL problem, even though I told them I had no prior experience with SQL and it wasn't mentioned for this role.