eClinicalWorks Interview Questions
& Process

The interview was a 1st round technical screen that covered Solid principle, Eager and lazy, Spring data Jpa Procedure, fetching millions of records, Map vs flatmap, Java 8 features, Final keyword over method & class, counting words in a sentence, security implementation, profiles, using multiple profiles, Jpa n+1 problem, API gateway, and microservices communication.

I wanted to share my experience with eClinicalWorks' hiring. I passed all the interviews and they told me I got the job. The HR even gave me a start date. Because they confirmed it, I turned down another job offer I had. But, I didn't get my offer letter even though my start date was coming up. I followed up with HR for about 15 days. Right at the last minute, they told me my profile was on hold due to some basic document issues and the job was also on hold. Because of this, I lost my other job offer and ended up with no job. It was super stressful. My advice to others: if you get selected, make sure you get the official offer letter right away before you reject any other offers. In my case, even after being selected and given a joining date, there was no guarantee.

I went for a walk-in interview at eClinicalWorks for a QA role. It felt pretty disorganized, with a lot of candidates and not enough interviewers, so there were long waits. I did two rounds and was told HR would contact me for a remote round. But the next day, I got a message saying I wasn't selected. It was weird because the interview implied more steps. The actual interview was okay, but the coordination and communication weren't great. They should plan walk-ins better with more interviewers and be clear about decisions.

The interview process was a walk-in, but HR also called referred candidates. Although there were only 15 openings, about 120-150 people showed up. Since interviewing everyone in 5 hours wasn't possible, they decided on multiple assessment rounds. The first round was technical, with paper and pen for everyone. They planned 10 questions, mostly about SQL and networking, like the MySQL port, a query for the highest salary, and how to troubleshoot a slow system, including prioritization in hypothetical scenarios. Clearing this round meant getting at least 5-6 out of 10 correct. About half the people were eliminated here. They also emphasized that English fluency is crucial (80% of the job) for interacting with US clients. The second round was with the Team Leader, who asked questions from 'about yourself' to career choices, mainly checking for genuine interest and potential to stay long-term, and again, English fluency through random questions. Passing this led to the Manager round. The manager asked both technical and other questions. Referred candidates skipped the Team Leader round but still had the technical assessment. In the manager round, I was asked about mistakes in SQL queries and a mess-up with DELETE, DROP, and TRUNCATE, which led to my rejection. Other technical questions included a query to show the schema (DESCRIBE). Overall, the process was quite easy. I was new to SQL and made a silly mistake due to the short answer time (20-30 seconds per question) during the technical round, but the questions themselves were simple. If your English is good, you're genuine, and you know basic OOPS, Networking, and SQL, you should be fine.