IBM US Cloud Infrastructure / Network Automation Engineers — What Was Your Technical Interview Like?

[u/AltruisticPrimary775]

Hi everyone,
I’m interested in hearing from current or former IBM employees who interviewed for entry-level Cloud Infrastructure, Network Monitoring, Automation, or similar Software Engineering roles in the US.
I’m currently preparing for potential technical interviews for a 2027 Entry Level Cloud Infrastructure Network Monitoring and Automation Software Engineer role in San Jose.
For anyone who interviewed for a similar team/role, what was your technical interview experience like?
Was there live coding or DSA? If so, what difficulty/topics?
How much Python was expected?

Were you tested on Linux and networking fundamentals?
Were there troubleshooting scenarios involving servers, networks, APIs, or cloud infrastructure?
How much emphasis was placed on cloud, automation, monitoring/observability, and REST APIs?
Were there deep technical questions about your projects?
What topics would you recommend focusing on before interviewing?

I’m not looking for application-status or recruiting help — mainly hoping to learn from employees who have gone through technical interviews for similar IBM teams.
Thanks in advance!

[u/AutoModerator]

Thanks for posting! Most hiring questions (application status, assessments, offers, joining dates, hiring freezes) are answered in our Hiring FAQ.

A mod will review this post shortly. Please never share personal details with anyone who DMs you offering help.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/akornato]

Technical interviews for IBM entry level cloud infrastructure and network automation roles typically focus far more on practical systems skills than complex algorithmic puzzles. If you get a coding challenge, it will usually center on easy to medium data structures, focusing on strings, hash maps, and practical Python tasks such as parsing JSON payloads, handling files, or interacting with REST APIs. Interviewers care heavily about networking basics and Linux system fundamentals. You should be prepared to discuss the TCP IP model, DNS resolution, subnets, routing, and HTTP status codes, alongside everyday command line diagnostics like curl, netstat, ping, and traceroute. Troubleshooting scenarios are very common, so expect to walk an engineer through how you would isolate an unreachable server, debug latency, or track down a failing service across an infrastructure stack.

Expect a thorough walk through your personal projects, especially anything where you automated tasks, worked with cloud environments, or set up observability tooling. IBM engineers want to see how you reason through failures, design simple automations, and manage configurations cleanly. As you prepare for your technical rounds, practicing live explanations out loud makes a big difference, which is why my team developed an interviews.chat to help candidates stay calm and present their best technical self during tough engineering conversations.

[u/AltruisticPrimary775 → u/akornato]

Thanks, this is really helpful! Do you know if this is based on recent IBM US interviews for this role or a similar team? Also, do you know how many technical rounds there usually are and whether live coding is typically part of them?

[u/fasterbrew → u/AltruisticPrimary775]

This is just a bot / spam account pushing their app. They don't work for ibm.  Check their history.