# LinkedIn Recruiter Packet

Public route: https://alexgerlitz.github.io/AlexGerlitz/linkedin-recruiter-packet.html

Use this page for a fast LinkedIn screen: role lane, first proof, safe first task, and contact path.
Open proof before messaging if a quick yes/no decision is needed.

## 30-Second Decision

- Primary target: Junior Python Backend / API Automation.
- Secondary lanes: QA/API Python, CRM/API Integration, Internal Tools.
- Best first assignment: one FastAPI endpoint, data model, admin queue step, API/CRM mapping, API test, or runbook gap.
- Best fit: junior Python backend/API automation, internal tools, QA/API Python, and CRM/API integration roles with clear first-month ownership.
- Useful signal: messy business workflows become backend-owned state, tests or smoke checks, privacy boundaries, docs, and handoff notes.

## Screening Decision

| Recruiter question | My answer |
| --- | --- |
| First paid-role screen | Screen me first for a reviewed junior backend/Python, QA/API Python, internal-tools, or CRM/API integration role where one working slice proves value. |
| Fastest proof | Start with First Backend Role Fit and Autoschool Intake/Admin; they show intake, validation, stored state, admin queue, operator status, evidence, and privacy boundary. |
| Distributed async signal | Written English docs, async review paths, CI/live smoke, Docker Compose handoff, API contracts, SQL/PostgreSQL, and privacy-safe evidence. |
| No-fit screen | Senior platform/DevOps ownership, Kubernetes/Terraform-first roles, onsite-only roles, pure prompt/content work, or vague roles without a first-month success condition. |

## Role Lanes

| Lane | Why it fits | Work sample to open |
| --- | --- | --- |
| Python backend / internal tools | FastAPI/PostgreSQL workflow slices, endpoints, data models, validation, admin queue steps, docs, and handoff. | [First Backend Role Fit](https://alexgerlitz.github.io/AlexGerlitz/first-backend-role.html) -> [Autoschool work sample](https://alexgerlitz.github.io/AlexGerlitz/autoschool-intake-admin.html) |
| QA Automation Python / API Testing | pytest, REST/OpenAPI checks, SQL/data checks, smoke routes, logs, issue notes, and repeatable verification. | [Backend Role Fit](https://alexgerlitz.github.io/AlexGerlitz/backend-first-screen.html) -> [Skill Evidence](https://alexgerlitz.github.io/AlexGerlitz/skill-evidence.html) |
| CRM/API integration | Adapter contracts, mappings, validation, retries, idempotency, audit logs, and privacy boundaries. | [Autoschool work sample](https://alexgerlitz.github.io/AlexGerlitz/autoschool-intake-admin.html) -> [Case Studies](https://alexgerlitz.github.io/AlexGerlitz/case-studies.html) |
| AI workflow / RAG | Retrieval, structured output, approval states, citations/evals, CRM-safe handoff, runbooks, and backend ownership. | [DriveDesk AI Operator](https://alexgerlitz.github.io/AlexGerlitz/drivedesk-proof-route.html) -> [AI Backend Review Pack](https://alexgerlitz.github.io/AlexGerlitz/ai-backend-proof-pack.html) |

## Role-Aligned Fit

- First screen: lead with Python, FastAPI, PostgreSQL, REST/OpenAPI, pytest, SQL checks, admin workflows, and integrations.
- Distributed fit: show English-first docs, async review paths, privacy boundaries, CI/live smoke, SQL/API contracts, Docker Compose handoff, runbooks, and handoff quality without making geography the public headline.
- AI positioning: AI is a delivery accelerator and workflow differentiator, not a replacement for engineering ownership.

## Scope Boundaries

- I can handle Docker Compose, GitHub Actions, health checks, smoke checks, logs, and runbooks as backend delivery support.
- Docker/CI is backend delivery handoff evidence: Compose, CI, health checks, logs, runbooks, and recovery notes.
- Public work samples use synthetic or redacted evidence only: no real names, phones, chat IDs, admin URLs, logs, dumps, tokens, or credentials.

## Best First Message

Send one remote role or one workflow plus one success condition. Helpful extras: systems involved, ownership boundary, timeline, and compensation band if shareable.

```text
Hi Alex, I am hiring for a remote Python/backend, QA/API, internal-tools, CRM/API integration, or backend-owned AI workflow role. Role: ... Stack/systems: ... First-month ownership: ... Can you send the best review path and smallest first slice you would own? Please include fit risks.
```

## Review Order

Fast screen: Autoschool Intake/Admin work sample -> PDF Resume -> First Backend Role Fit. Use Recruiter Review Pack for forwarding after role fit is clear.

1. [Autoschool Intake/Admin work sample](https://alexgerlitz.github.io/AlexGerlitz/autoschool-intake-admin.html): bot intake -> backend validation -> database state -> admin queue -> operator status.
2. [PDF Resume](https://alexgerlitz.github.io/AlexGerlitz/output/pdf/alex-gerlitz-python-backend-automation-resume.pdf): two-page shortlist and evidence handoff.
3. [First Backend Role Fit](https://alexgerlitz.github.io/AlexGerlitz/first-backend-role.html): bounded first-task sample.
4. [Recruiter Review Pack](https://alexgerlitz.github.io/AlexGerlitz/output/pdf/alex-gerlitz-recruiter-proof-pack.pdf): two-page fit and handoff for forwarding after fit.
5. [Skill Evidence](https://alexgerlitz.github.io/AlexGerlitz/skill-evidence.html): skill-to-evidence map across Python, FastAPI, PostgreSQL, QA/API, integrations, RAG, and Docker/CI handoff.
6. [Verification Pack](https://alexgerlitz.github.io/AlexGerlitz/verification-pack.html): CI, live smoke, public routes, and evidence freshness.