Real, anonymous reports from people who interviewed for Software Engineer at AT&T, newest first and distilled into what to expect across the loop.
My interview process felt organized and professional from the start. Recruiters were responsive and the whole journey felt structured, with each stage sounding and acting like it was designed for the role instead of random checkpoints. The questions focused on both technical knowledge and general fit, and I never felt like I was being tested on unrelated material.
After applying, I was pulled into an online HackerRank-style technical assessment with a few algorithm problems and REST/API knowledge mixed in. The test ran for about 3.5 hours, and it included multiple LeetCode-style coding questions plus a REST API–focused prompt. Some of the questions were written in a way that felt a little odd at first, but once I figured out what they were actually asking, a few became more reasonable.
Candidates typically start with an online assessment that includes a mix of coding problems, often in a HackerRank or Codesignal format, focusing on algorithms, REST/API knowledge, and SQL. The assessment can be challenging, with questions varying in difficulty and time pressure being a significant factor.
Following the assessment, candidates engage in technical interviews that often include discussions on data structures, algorithms, system design, and practical coding tasks. The interviews are generally conversational but expect candidates to demonstrate a solid understanding of technical concepts and real-world applications.
Behavioral interviews are a key component, focusing on cultural fit and communication skills, often using the STAR method for responses. Candidates should prepare to discuss past experiences and how they align with the company's values and team dynamics.
The overall timeline can be lengthy and inconsistent, with candidates experiencing significant waiting periods between stages. Communication about status and next steps can be vague, leading to uncertainty and stress throughout the process.
The interview atmosphere varies, with some candidates describing it as relaxed and friendly, while others felt pressure from the technical demands. Overall, a supportive environment is often noted, but the intensity of the technical assessments can create stress.
Candidates often reflect on the importance of thorough preparation, not just in technical skills but also in articulating their experiences and maintaining confidence during discussions. A clear understanding of past projects and how they relate to the role is crucial.