Delta Air Lines Software Engineer Interview Guide

The process was more drawn out than I expected, but still pretty straightforward overall. I first went through a recruiter screen, and then a manager scheduled a 30-minute virtual interview. After that, there was another virtual round, and the whole thing stayed remote over Zoom/Webex. The first conversations were mostly about my background and what I’d done on my resume, rather than deep algorithm work. One of the more specific questions I got was about my experience with Red Hat Linux system servers, and another was how to access a server using a jumphost, so it definitely leaned toward practical systems knowledge. I also got asked about AWS services and tooling like EC2, S3, API Gateway, REST APIs, CDK deployment, Pylint, and Pydantic, which made it feel like they cared a lot about whether I had actually worked in that stack rather than just knowing it in theory.

The behavioral side was pretty prominent too. I was asked why I was looking for a change, and there were questions about how I mentor and upskill SDETs on my team, plus how I handle conflicts between developers and testers. That part felt easy and conversational, and the interviewers were friendly. I also heard that there can be coding assessments up front that are LeetCode-style, so I’d be ready for that even if the later rounds are more resume- and systems-focused. In my case, the process ended without an offer, but it never felt overly aggressive or trick-heavy. My main takeaway is to be ready to talk through your actual production experience with Linux, AWS, and deployment tools, and not just generic software engineering concepts.