# Beyond Interviews
## Real Engineering Problems

---

## What is this?

This project is about one simple question:

> Do typical coding interview problems reflect real engineering work?

Short answer: not really.

But instead of complaining about it, this project tries to **understand why**.

---

## Why this exists

Many interview processes rely on:

- LeetCode
- Codility
- algorithmic puzzles

These tasks are:

- abstract
- isolated
- time-pressured

Real engineering is not.

---

## What this project does

For each interview problem, we:

1. Look at the original task
2. Show the typical “interview solution”
3. Explain what it actually tests
4. Compare it with real-world engineering
5. Find (if possible) a real equivalent

---

## Core idea

There is a gap:

```
Interview problems ≠ Real engineering work
```

This project explores that gap.

---

## Not a rant

This is **not** about:

- complaining
- mocking interviews
- saying "everything is useless"

Instead:

- understand what these problems measure
- show where they help
- show where they don’t

---

## Engineering focus

Special attention is given to **systems and embedded development**, where reality looks very different:

- imperfect data
- hardware constraints
- memory limits
- timing issues
- debugging real systems

---

## Repository structure

```
analysis/
  01-.../
  02-.../
```

Each analysis contains:

- explanation
- comparison
- conclusions
- sometimes code

---

## How to read this

Start with any analysis.

Each one answers:

> Would this problem appear in real engineering?

---

## Why it matters

Because solving puzzles ≠ building systems.

And understanding the difference makes you a better engineer.

---

## Status

Work in progress.

Problems are added when ready — no fixed schedule.

---

## Author note

This project started as a personal attempt to make interview preparation meaningful.

If it helps someone else — even better.