Do real work

Ditch the algorithms.

Forget about Dijkstra’s and linked lists—they won’t help you when your logs are screaming and something’s breaking in production. You grow as an engineer by debugging, diagnosing, and fixing real issues.
real-swe gives you a place to practice those real-world skills and get better at the work that actually matters.

Practice by Career Track

Choose your path and solve problems tailored to your career goals. Each track focuses on real-world skills you'll use on the job.

Backend

Build APIs, design databases, and handle server-side logic. Master the systems that power modern applications.

Frontend

Create beautiful user interfaces, build responsive designs, and craft seamless user experiences.

Infrastructure

Deploy services, manage cloud infrastructure, and ensure systems scale reliably and securely.

Data Engineering

Process large datasets, build data pipelines, and turn raw data into actionable insights.

fix: resolve race condition in payment webhook

main ← fix/webhook-retry

services/payment_handler.py
42 def handle_webhook(self, event):
43- payment = self.process(event.data)
43+ with self._lock:
44+ payment = self.process(event.data)
45 return PaymentResult(payment)
Your review comment

The lock prevents concurrent webhook processing, but consider using an idempotency key instead for better throughput.

Code Review

Review the PR

Sharpen your code review skills on real pull requests. Read diffs, spot bugs, suggest improvements, and get AI-powered feedback on the quality of your review.

  • Real PR diffs from open-source projects
  • Leave inline comments with severity levels
  • AI scores your review on completeness, accuracy, and communication
Career AI

Know Your Repo

Turn any GitHub repository into a tailored technical quiz. Our AI reads your codebase, identifies patterns and design choices, and generates interview-grade questions with detailed explanations.

  • Role‑aware questions based on your target job
  • Explains answers with code references and architecture context
  • Works for your repos or public GitHub projects

Integration

GitHub Repositories

repo analysis
AI insights

Detected Patterns

  • Modular monorepo layout
  • Clean architecture layering
  • Clear error boundaries

Sample Question

Why does the repo choose dependency inversion for the domain layer, and what tradeoffs does it introduce?