← Interview experiences
HTRejected

SDE at Hexaview Technologies

Difficulty
Process took
3-4 Weeks
Rounds
4
Format
Remote
Applied via
Email

How it went

  • Even though I didn’t make it, the interview experience was invaluable. It gave me great insights into areas I need to work on and what top companies like Hexaview Technologies expect from candidates. I’m grateful for the experience and looking forward to better preparation in future interviews.
  • Good luck to everyone preparing, the process is tough, but it’s a great opportunity to learn and grow. Keep pushing forward!

What they would tell you

  • Even though I didn’t make it, the interview experience was invaluable. It gave me great insights into areas I need to work on and what top companies like Hexaview Technologies expect from candidates. I’m grateful for the experience and looking forward to better preparation in future interviews.
  • Good luck to everyone preparing, the process is tough, but it’s a great opportunity to learn and grow. Keep pushing forward!

How to prepare

  • The online assessment often tests problem-solving and algorithm efficiency. Practice LeetCode-style problems, especially in arrays, strings, and dynamic programming. Time management is key, so ensure you can optimize solutions and handle edge cases effectively.
  • Prepare for questions on ACID properties, normalization, and SQL optimizations. Make sure you’re clear on database indexing and query performance. Practice writing efficient SQL queries with joins and subqueries.

Round by round

  1. 1

    Online Assessment Round60 min

    I recently went through the interview process for the Software Development Engineer (SDE) role at Hexaview Technologies, and while I didn’t make it to the final stage, the experience was incredibly enriching. It was a solid test of my problem-solving skills, coding proficiency, and understanding of key concepts in data structures, databases, and object-oriented programming (OOP). Here’s a detailed breakdown of each round. The assessment started with two DSA problems, and I was pretty comfortable with both: Roman to Integer

    • I had solved this type of problem before, so it was quick to complete. String subsequence-based problem

    • This one was a bit more complex, and I can’t recall the exact problem, but it involved understanding subsequences and dynamic programming. I finished both, As the questions weren’t entirely new to me, I made sure to test my solutions thoroughly before submitting them.

  2. 2

    Technical Interview90 min

    This round was a mix of DSA, DBMS, and OOPs. It was pretty straightforward, with the interviewer being supportive throughout. DSA: Two Sum

    • I explained my approach for solving the Two Sum problem, coded it live, and passed all test cases.The interviewer was happy with the solution and asked me to briefly discuss the time and space complexity. Length of Last Word

    • Another problem where I live-coded and explained the steps as I went. I solved this one as well, and we discussed its time complexity. DBMS:

    • The interviewer asked some theoretical questions related to ACID properties, Normalization, and SQL queries.

    • One tricky part was when we got into LIMIT and OFFSET. I stumbled a bit here, but the interviewer was patient and explained it, which helped me understand it better. OOPs:

    • I explained the four pillars of OOP (Encapsulation, Abstraction, Inheritance, Polymorphism) with examples.

    At the end of the interview, the interviewer gave me a puzzle, but unfortunately, due to internet issues, the call dropped before I could complete it. However, I followed up via email, and the interviewer was satisfied with my performance, so no re-interview was needed.

  3. 3

    Technical Interview60 min

    This round was entirely focused on OOPs concepts. The interviewer gave me a mix of conceptual questions and live coding tasks. OOPs Implementation:

    • I was asked to explain each OOP concept and then implement the logic in code.

    • I did get a little mixed up with Java and C++ syntax (the interviewer was a Salesforce dev), but I managed to impress him by adapting quickly. Task:

    • The final coding task was to find the frequency of characters in a given string.

    • I explained the approach and successfully coded it live.

  4. 4

    Technical Interview60 min

    This round was definitely the toughest for me. There was some travel confusion that almost made me miss the interview, but I made it just in time. The Tech Lead wasn’t onsite, so we connected over Google Meet, which made things feel a bit more distant. Problems Covered: Linked List Problem

    • This was a real challenge since I had never implemented a Linked List from scratch before, I was used to solving function-based problems on LeetCode. I struggled a bit, but I managed to explain my thought process clearly and eventually completed the task. Array Problem

    • The next problem was about checking if two sorted arrays are equal. While I got the correct results and passed the test cases, I couldn’t optimize the solution. I used three loops, which wasn’t the most efficient approach. DBMS

    • The interviewer dug into normalization again, focusing on LIMIT and OFFSET. I also had to answer a design question regarding database schema, which I struggled with since I hadn’t revisited DBMS theory in a while. I think nervousness played a huge role here. Since I hadn’t practiced full implementations like the Linked List problem in a while, I struggled. I also couldn’t optimize my array solution, which I felt could have been better. The DBMS theory tripped me up because I didn’t review it in-depth before the interview, which definitely showed.

What came up

MediumRemote1 2 years

A candidate-reported account, lightly edited. Interview processes change by team and date.

Sources