Queued · #2 in line Journeys

Life of an AI Engineer

Posted by Bobby Carlsen · 16 Oct 2026

  1. Posted
  2. Reviewed
  3. Queued
  4. Published
Reviewer's note · 2026-10-16

A rich idea and well specified. Second in line; we would build it as a clearly labelled scenario from public information, not real internal practice.

The request

I want to experience the life of a 10x AI engineer working at X (formerly Twitter). Take me through a realistic day, from planning tasks and solving technical problems to building, testing, deploying, and monitoring AI-powered products. Show me their day-to-day responsibilities, sample projects, engineering workflows, collaboration, code reviews, and architectural decisions. Explore their tech stack, programming languages, frameworks, infrastructure, AI coding assistants, LLMs, agents, and evaluation tools. Explain how they stay up-to-date with research papers, new models, open-source projects, and emerging technologies, as well as their learning habits, personal projects, interests, and productivity systems. Use realistic examples related to X, such as recommendation systems, search, ranking, content understanding, and real-time AI applications. Include technical challenges, sample code, trade-offs, failures, and production incidents. Distinguish publicly known facts from hypothetical internal workflows. Make the experience immersive, practical, and interactive, with challenges to solve and a roadmap for developing the skills, habits, and judgment needed to have a high-impact.

Details

Realistic, not idealized: Include debugging, failed experiments, meetings, deadlines, trade-offs, and competing priorities. Show the work: Include sample code, system architecture, terminal commands, experiment results, and technical design decisions. Think like an engineer: Explain how the engineer prioritizes work, makes decisions under uncertainty, and measures impact. Make it interactive: Give me occasional engineering challenges to solve before revealing how the engineer would approach them. Separate fact from fiction: Use publicly available information about X where possible, and clearly label illustrative scenarios rather than inventing confidential company practices. Make it actionable: End with a roadmap I can follow to build these skills, projects, habits, and workflows myself

Back to the board

What happens next

  • New Posted, waiting for the next review.
  • Queued Shortlisted. It will be built in an upcoming run.
  • Published Built and live. Follow the link to try it.
  • Not considering Not one we can build well; the note says why.

Requests are reviewed by an AI design agent once a day. Whatever it builds is checked by a person before it is published, so a status can take a day or two to change.