Rockwell Automation Software Engineer Interview Questions
& Process

DON'T WASTE YOUR TIME TO GET INTERVIEWING HERE...!!! Very worst experience with this organization’s interview process. When you apply to this organization with a given salary expectation, you also get a screening call from HR, and you clearly mention the salary expectation. Then the 1st technical round happens, then they ask for another round which will be offline. Then in the managerial round, they ask technical and coding questions as well. Again, after that, the manager's boss takes the interview, and then he asks for the expectation with the negotiation range as well. This whole process happens and as a result, they are offering a salary less than the current salary...LOL............ IS THIS KIND OF JOKEEEE...FROM A REPUTED COMPANY...!!! Although HR was agreed to the salary range expectation, the same HR was saying we have only this much budget........ VERY DISAPPOINTMENTED....!!!!! Negotiation is very low level after wasting this much of time.

I had a good initial phone screen with the recruiting team. But the actual interview was not great. The interviewer didn't seem to be seriously hiring, more like conducting informational interviews which wasn't communicated upfront, making it feel like a waste of my time. I had clearly stated I was looking for software development roles. The interviewer described the IT teams and asked about my interests. When I said software development, they mentioned those teams were full and only Cloud openings were available. They offered to connect me on LinkedIn with someone from the Cloud team, which I declined. It felt like a complete waste of time.

We're going to check out your tech skills, how you solve problems, and your design abilities. You can do this in person or over video, and it'll take about 60-90 minutes. We'll talk about system design stuff, like how to build systems that can scale and be maintained, for example, designing a microservices setup for online shopping. We'll also look at code you've written or a sample project, to see if it's good quality and follows patterns. You'll need to solve a technical problem, maybe on a whiteboard or shared doc, like fixing some buggy or slow code. And we'll dig into advanced .NET concepts like async stuff, dependency injection, or making things run faster, for instance, how you'd process lots of data quickly in .NET.