Straive

The worst experience! Playing with candidates time and emotions.. After attending 4 rounds of interview they say waiting for hiring manager slots Post which they said org restructure happening internally and then ask us to wait for a month Then they say position is kn hold will process for some other team You have your hopes and then ghosted.. the ignore you as you're their ex! 😂

there was a total of three rounds. two rounds of interview with straive and one with client round. i would say the difficult was moderate and based on the requirements and sill set the interview is processed further.

One of the most unprofessional interview experiences I have had in my career. The role was for an AWS Data Engineer. I have more than 5 years of hands-on AWS experience and hold both the AWS Solutions Architect Associate and AWS Data Engineer Associate certifications. L1 (FloCareer): The first round covered SQL, data engineering fundamentals, optimization techniques, and two coding questions (Python and SQL). Everything went smoothly. L2: This round focused extensively on Amazon Redshift, including distribution keys, sort keys, compression encodings, workload management (WLM), storage optimization, and performance tuning. I was able to answer almost every question with practical examples from production projects. L3 (VProple – Interview as a Service): Another deep technical discussion around Redshift architecture and optimization. Although the questioning felt repetitive and lacked depth compared to the previous round, I answered confidently and explained the reasoning behind my design decisions. L4 (Client Preparation Round): This was described as the final internal round before the client interview. Two members of the leadership team joined the discussion. We spent considerable time reviewing my projects, AWS expertise, architecture decisions, and overall technical experience. At the end of the call, I was told the discussion had gone well and that HR would schedule the client interview. That interview never happened. Instead, I was left waiting for over a month with virtually no communication or closure. After investing time and effort into four interview rounds, the company couldn't even provide a proper update or a final decision. This isn't just disappointing—it's disrespectful to candidates' time. If a position is put on hold, cancelled, or the client changes their requirements, simply communicate that. Keeping candidates waiting indefinitely after multiple rounds reflects very poorly on the organization's hiring process. Ironically, during the same period I received two other offers, both with approximately 20% higher compensation than what Straive had indicated. Advice to candidates: Treat every positive response from this company with caution until you have a written offer and a confirmed joining date. No matter how well your interviews go, continue pursuing other opportunities because clearing multiple rounds here does not necessarily lead to a client interview—or even a final outcome. Straive should seriously improve its recruitment process. Technical interviews are a significant investment for experienced professionals, and candidates deserve transparency, timely communication, and basic professional courtesy.

3 rounds of interview. 1st - sql,pyspark,data related concepts. All theory. 45 mins, 30 questions, like a college viva 2nd - project dicussions and situation based questions. 3rd - spark architecture, pyspark depth, 2 scripts writing.

I was referrer by an external hiring consultancy. I underwent two rounds of interviews. L1 was conducted by a third party, scheduled for 30 minutes, but went over 50 minutes since the interviewer was late. I shared my screen for the interview where they asked simple questions on past experience, then on SQL and Python where I had to write the solutions out on a notepad. L2 was a 30 minute interview scheduled with the Straive team itself. The main interviewer joined 12 minutes late. No real apology either. Asked me to introduce myself. Then told me he will give me SQL and Python problems. He wasn't even prepared for the questions, he had to look up the questions, and that took another 5-7 minutes. I answered two SQL questions and we were obviously out of time by then. So he quickly wrapped up, despite him being the reason for the delay. After the interview I sent a follow up email to the HR. After not hearing back, I called them twice to be ghosted. Absolutely abhorrent experience.