Target: remote Junior Python Backend / API Automation. Adjacent lanes: QA/API Python, CRM/API Integration, Support Engineer with Python, and Internal Tools when the work is backend/API-heavy.
Experience base: Autoschool54 / DriveDesk backend and application-support work since March 2024, turned into public-safe work samples without exposing live production data.
First proof: Autoschool Intake/Admin shows request intake -> backend validation -> database record -> admin queue -> operator status, with private production data replaced by synthetic evidence.
First useful result: one FastAPI endpoint, data model, admin queue step, API/CRM mapping, pytest/API smoke check, SQL/data check, or runbook gap shipped as a reviewed slice with docs and handoff notes.
I build Python backend/API automation for messy business workflows: FastAPI/PostgreSQL services, admin queues, REST/OpenAPI boundaries, API/CRM integrations, QA/API checks, and handoff docs. DriveDesk and RAG/AI workflow evidence stay visible only after the backend/API fit is clear.
Delivery boundary: the useful signal is not "AI can write code"; it is that one real workflow can become a reviewed FastAPI/PostgreSQL/Telegram/admin slice with tests, logs, docs, and handoff. Stack fit: Python, FastAPI, PostgreSQL, REST/OpenAPI, SQL, pytest/API smoke checks, Docker/Compose boundaries, GitHub Actions, docs, runbooks, and recovery notes.
| Open in this order | Why it matters |
|---|---|
| Hiring Decision | 30-second yes/no screen: best-fit role lane, first safe task, first proof, and no-fit boundaries. |
| LinkedIn Recruiter Packet | 30-second role lane, first work sample, scope boundary, and recruiter prompt. |
| First Backend Role Fit | The practical first-job question: what can a team safely give me first? |
| Autoschool Intake/Admin work sample | First-role backend/internal-tools proof with synthetic public evidence only. |
| PDF resume | Two-page shortlist and evidence handoff for application upload or internal forwarding. |
Forwarding after fit is clear: Recruiter review pack. Deeper technical review: DriveDesk AI Operator and AI Backend Review Pack. For application parsers and plain-text uploads: ATS plain-text resume.
Message me first when there is one messy workflow, one risky integration boundary, or one Python/backend automation, API/CRM, QA automation, AI workflow, or reliability slice that should become testable, logged, documented, and handed off.
First reply promise: I will answer with a fit read, risky assumptions, the smallest responsible first slice, the work sample to inspect, and the right next path: remote full-time screen, technical review, scoped project, or no-fit.
Suggested recruiter path: Hiring Decision -> LinkedIn Recruiter Packet -> First Backend Role Fit -> Autoschool Intake/Admin work sample -> PDF resume. Use the recruiter review pack only after the role fit is clear. Message on LinkedIn with role title, remote setup, stack/systems, and one success condition; add first-month ownership, timeline, and compensation band when shareable.
LinkedIn support routes: Backend/API Work Samples for the profile-view work-sample route, Recruiter Preferences for Open-to-Work filters, Decision-Ready Contact for first-contact context, and Skill Evidence for the skill-to-work-sample map.
AI-native delivery loop: I use AI tooling to compress discovery, implementation, debugging, docs, and review into faster iteration, while architecture, state boundaries, privacy checks, tests, logs, deployment, runbooks, and shipped quality remain my responsibility.
Search-fit titles: Junior Backend Developer, Junior Python Developer, Python Automation Engineer, Backend Automation Engineer, QA Automation Python, API Testing / Test Automation Engineer, Support Engineer with Python, Integration Engineer, CRM/API Integration Engineer, and Internal Tools Engineer. AI workflow and RAG work stay visible as evidence-backed differentiators, not the first title I need to be screened under.
LinkedIn recruiter search alignment: remote-only full-time roles where Python, FastAPI, PostgreSQL, Docker, GitHub Actions, RAG, Vector Databases, CRM/ERP/API integration, QA Automation Python, OpenAPI, n8n, Telegram, or pgvector appear in the role.
Best immediate starts: Python/backend workflow slice, CRM/ERP/API adapter, internal operations tool, QA/API verification path, or reliability handoff. AI workflow automation is a differentiator after backend/API ownership is established.
| Send me | Best match | Fast review |
|---|---|---|
| Remote full-time role | Junior Python backend, QA/API automation, integrations, internal tools, Python/FastAPI/PostgreSQL, Docker/CI handoff. | Hiring Decision, Decision-Ready Contact, LinkedIn Recruiter Packet, First Backend Role Fit, Autoschool Intake/Admin work sample, PDF resume |
| Technical review | Code, CI, live smoke, runtime boundaries, privacy redaction, adapter contracts, runbooks, and public-safe evidence. | Verification pack, AI Ops evidence status |
| Scoped project after role fit | One messy workflow, one success condition, and a working slice with tests, logs, docs, and handoff path. | Work with me, fixed-scope offers, Start conversation |
DriveDesk AI Operator is the sharpest current work sample: documents, call audio, transcripts, or CRM leads -> RAG, analysis, scoring, tasks, Telegram approval, and CRM handoff with backend-owned state, audit, retries, idempotency, and adapter contracts.
The larger DriveDesk Flagship Backend Workflow is the broader backend workflow path: roles, records, workflows, adapters, audit/outbox, admin/operator surfaces, Docker/CI handoff, observability, backups, and recovery paths.
Since March 2024, I have supported Autoschool54 backend/application-support work remotely while turning real operational problems into public-safe backend workflow samples: admin workflows, documents, schedules, payments, accounts, access, automation, deployment, logs, backups, and recovery paths.
| Sample | What to inspect |
|---|---|
| Selected work samples | pinned repos: Autoschool Intake/Admin work sample, DriveDesk AI Operator, DriveDesk Core, AI Ops Workflow Kit, DeployMate, and MPlusForm. |
| DriveDesk Core | FastAPI/PostgreSQL operations backend foundation behind the public-safe Autoschool Intake/Admin sample: tenants, RBAC, audit/outbox, adapters, OpenAPI, Docker, pytest, CI, docs, public demo. |
| AI Ops Workflow Kit | RAG workflow backend: business scenario replay, first-slice playbook, privacy redaction, approvals, Telegram callback, dry-run CRM handoff, live PostgreSQL/pgvector persistence, CI, and smoke checks. |
| DeployMate | Self-hosted Docker deployment control panel: FastAPI/Next.js/PostgreSQL, SSH runtime tooling, CI/CD, health checks, evidence bundles, review packet, runbooks. |
| MPlusForm | Validation-boundary automation sample: Python sync pipeline, server-approved snapshots, Windows operations docs, Lua addon, and public verification run. |
| Need | My ownership surface |
|---|---|
| AI workflow / RAG automation | Ingestion, retrieval, analysis, scoring, approvals, operator docs, tests, and metrics. |
| CRM/ERP/accounting/banking integration | Explicit adapters, mappings, retries, logs, idempotency, rollout notes, and recovery path. |
| Internal ops platform | FastAPI/PostgreSQL backend, admin UI, intake/admin handoff, roles, audit trail, workflows, deployment, runbook. |
| Reliability / Docker handoff | Docker, CI/release gates, health checks, logs, backups, smoke checks, and rollback procedure. |
Fast fit checklist: message me when the work is remote-only and needs a backend-owned AI workflow, CRM/ERP/API integration, internal operations tool, QA/API verification path, Docker/CI handoff, or one first working slice with tests, logs, docs, and a handoff route. I am not positioning for onsite-only roles, pure prompt/content tasks, isolated static websites, student/course assignments, standalone game clones, generic mobile/ecommerce apps without backend/integration ownership, or vague work where success cannot be defined. LinkedIn: linkedin.com/in/alex-gerlitz-a659ab3bb · LinkedIn Services