From the outset, the interview raised red flags. The job description—vague and sparse—listed a handful of Azure cloud services but offered no insight into actual responsibilities. I came prepared with many questions, especially since both the recruiter and the job listing emphasized Azure expertise as a mandatory requirement. However, it quickly became clear that the company wasn’t using Azure—or any cloud services—at all. The hiring manager admitted that CareSource “hoped” to adopt cloud technology someday, but there was no roadmap, timeline, or even a basic strategy in place. The real need was for a big data engineer, not a cloud engineer. The title and description felt like a bait-and-switch. The hiring manager struggled to articulate the department’s objectives and couldn’t provide clarity on what success in the role would look like. His tone throughout was sarcastic, occasionally veering into self-righteousness. It felt less like a collaborative opportunity and more like being asked to parachute into a chaotic environment with no clear mission. The lead developer was more grounded but offered little additional clarity. Overall, the interview left me with the impression that the company was hiring for a future that hadn’t been planned—and expecting someone to build the bridge without blueprints. This position will fail since it is three (3) positions rolled into one. 1) Azure Architect 2) Full Stack Engineer and 3) Big Data Engineer / Architect