← AT&T Interview Insights

AT&T·Software Engineer·Onsite - System Design / Architecture·Senior

Senior
May 2026

Summary

System design round for a software engineer role, one question about building an agent-facing support tool with some awkward constraints baked in. Not the most straightforward setup I've seen.

Questions Asked (1)

Q1

Design a support ticket system for agents, where the ticket data is only accessible via a browser (no API), and user data is available through an API that can be used to generate chat responses.

System DesignAPI & IntegrationsTechnical Trade-offs
Author's notes

The no-API constraint on the ticket system is what tripped me up at first.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements and constraints, then propose a hybrid architecture that separates the browser-only ticket data from the API-accessible user data. Focus on how to integrate these sources securely and efficiently, and discuss trade-offs like caching, data consistency, and real-time updates.

Pro tip: Emphasize the importance of decoupling the ticket system from the user API to avoid tight coupling and enable independent scaling. Also, mention the need for a secure proxy or backend-for-frontend to handle browser-only data and API calls, ensuring compliance and performance.

1. Clarify Requirements and Constraints

Ask questions to understand the scale, real-time needs, security requirements, and why ticket data is browser-only. Confirm that user data API is the only way to fetch user info and generate chat responses.

2. High-Level Architecture

Propose a system with a frontend for agents, a backend service (BFF) that interacts with the browser-only ticket data (e.g., via scraping or browser automation) and the user API. Consider using a message queue for asynchronous processing.

3. Data Integration and Chat Response Generation

Design how the backend will combine ticket data (from browser) and user data (from API) to generate chat responses. Discuss using a template engine or AI model, and how to handle latency and failures.

4. Scalability, Reliability, and Security

Address scaling the browser automation (e.g., headless browsers), caching user data, rate limiting, and securing access to both data sources. Mention monitoring and logging.

5. Trade-offs and Alternatives

Discuss trade-offs of browser automation vs. asking for API access, caching vs. real-time, and monolithic vs. microservices. Suggest potential improvements if constraints change.

Key Points to Mention

  • Browser automation tools like Puppeteer or Selenium for accessing ticket data
  • Backend-for-frontend (BFF) pattern to aggregate data from multiple sources
  • Caching strategies for user data to reduce API calls and improve performance
  • Asynchronous processing with message queues for chat response generation
  • Security considerations: authentication, authorization, and data privacy
  • Trade-offs between real-time updates and system complexity

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