# Backend Role Fit

Public HTML route: https://alexgerlitz.github.io/AlexGerlitz/backend-first-screen.html

Use this page when a recruiter or hiring manager needs a fast backend/internal-tools fit before
opening the full portfolio.

## 30-Second Fit

Best-fit roles:

- Back End Developer
- Python Developer
- Backend Engineer
- Internal Tools Engineer
- Integration Engineer
- CRM/Admin Tools Developer
- Internal Tools Engineer when the first month is a concrete backend slice

Fastest review path:

1. [Autoschool Intake/Admin work sample](./AUTOSCHOOL_INTAKE_ADMIN.md)
2. [Synthetic demo seed](./data/autoschool-intake-admin-demo.json)
3. [DriveDesk Core](https://github.com/AlexGerlitz/drivedesk-core)
4. [AI Backend Review Pack](./AI_BACKEND_PROOF_PACK.md)
5. [Skill Evidence](./SKILL_EVIDENCE.md)
6. [Decision-Ready Contact](./DECISION_READY_CONTACT.md)
7. [PDF Resume](./output/pdf/alex-gerlitz-python-backend-automation-resume.pdf)

## What This Shows

| Review question | Work-sample answer |
| --- | --- |
| Can I build a practical API/data workflow? | Telegram-style request becomes API payload, validated business state, database record, and admin queue row. |
| Can I work with backend state instead of only UI scripts? | The work sample centers on records, statuses, timestamps, review state, operator action, and audit events. |
| Can I handle internal tools and CRM/admin workflows? | The Autoschool slice maps user intake to an operator queue and status workflow. |
| Can I avoid leaking private business data? | The public evidence uses only synthetic data and an explicit privacy boundary. |
| Can a team review my work async? | The route includes markdown, HTML, JSON seed, CI/live smoke, and handoff links. |

## Stack Match

Search and screening keywords: Python, FastAPI, PostgreSQL, REST APIs, OpenAPI, Docker, GitHub
Actions, Telegram intake, admin workflow, internal tools, CRM/API integration, validation, audit,
status workflow, runbooks, and handoff docs.

## First Working Slice I Can Own

Given one messy request workflow, I can own the first responsible backend slice:

1. Map the user-facing input and operator action.
2. Define a small validated payload.
3. Persist it with status, source, timestamp, review state, and audit event.
4. Expose it to an admin/operator queue.
5. Add smoke checks, docs, privacy notes, and handoff path.

## Boundary

This page intentionally uses public-safe evidence only. It does not use live admin screenshots,
real names, contact details, Telegram IDs, chat IDs, private URLs, raw logs, credentials, database
dumps, or private repository code.