← AT&T Interview Insights

AT&T·Software Engineer·Hiring Manager Screen·Intermediate

IntermediateRejected
Apr 2026

Summary

One-on-one with a hiring manager that was supposed to be mostly behavioral but surprise, there was a live coding problem. Solved it fine but barely said a word while doing it, and got rejected two days later.

Questions Asked (1)

Q1

Solve a coding problem live during the interview session.

Algorithms & Data Structures
Author's notes

I actually got through most of it.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying the problem requirements and constraints, then discuss possible approaches and their trade-offs before coding. Implement a clean solution while explaining your thought process, and test with examples to verify correctness and edge cases.

Pro tip: Communicate constantly—interviewers evaluate your problem-solving and collaboration skills as much as your coding ability. If you get stuck, verbalize your reasoning and ask for hints rather than sitting in silence.

1. Understand and Clarify

Ask questions to confirm input/output formats, constraints, and edge cases. Restate the problem in your own words to ensure alignment.

2. Plan and Discuss Approaches

Brainstorm multiple solutions, analyze time and space complexity, and choose the most efficient one. Explain your reasoning to the interviewer.

3. Implement with Narration

Write clean, modular code while explaining each step. Use meaningful variable names and handle edge cases as you go.

4. Test and Debug

Walk through your code with sample inputs, including edge cases. Identify and fix any bugs, and verify the solution meets the requirements.

5. Reflect and Optimize

If time permits, discuss potential optimizations or alternative approaches. Summarize the solution and its complexity.

Key Points to Mention

  • Time and space complexity analysis of your solution
  • Edge cases such as empty inputs, large inputs, and duplicates
  • Trade-offs between different approaches (e.g., brute force vs. optimized)
  • Modular and readable code with meaningful variable names
  • Testing strategy including unit tests and manual walkthroughs
  • Communication and collaboration with the interviewer

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.