LinkedIn profile signal

Python Backend / API Automation first, proof one click away.

The first LinkedIn screen should point to one clear lane: remote-capable Junior Python Backend / API Automation, with adjacent QA/API Python, CRM/API integration, internal tools, and support-with-Python roles when the work is backend/API-heavy.

Strongest proof: OpsDesk Lite shows support request intake, FastAPI validation, SQLAlchemy state, operator queue, status transition, idempotent outbox, SLA worker, SQL metrics, tests, Docker Compose handoff, CI, and privacy audit.

Message on LinkedIn Backend/API work samples OpsDesk Lite Recruiter packet PDF resume
Python FastAPI PostgreSQL REST / OpenAPI pytest CRM/API integration Docker Compose handoff

Headline

Python Backend Developer | FastAPI, PostgreSQL, API/CRM Integrations | QA/API Python

Short Role Signal

Remote-capable Junior Python Backend / API Automation. Adjacent fits only when the first month can ship one backend/API-heavy slice.

Boundary

Docker/CI is backend delivery handoff evidence. AI tooling speeds work; architecture, privacy, state, tests, and shipped quality stay mine.

About Text

I build Python backend/API automation for business workflows: FastAPI endpoints, PostgreSQL state, REST/OpenAPI contracts, admin queues, API/CRM mappings, pytest/API smoke checks, logs, docs, and handoff notes.

Strongest first code proof: OpsDesk Lite, where a support request becomes FastAPI validation, SQLAlchemy state, an operator queue, status transition, idempotent outbox event, SLA worker event, SQL metrics summary, tests, Docker Compose handoff, and CI.

Real-work context: since March 2024 I have supported Autoschool54 / DriveDesk backend and application-support work remotely, then turned the safe parts into public work samples with synthetic evidence.

Best first role fit: junior Python backend/API automation, internal tools, QA/API Python, CRM/API integration, or support engineer with Python when the first month can ship one useful backend/API-heavy slice.

AI tooling speeds up research, implementation, debugging, docs, tests, and review. Architecture, privacy, state boundaries, verification, and shipped quality remain my responsibility.

Open-To-Work

Job titles Back End Developer, Python Developer, Quality Assurance Automation Engineer, Integration Engineer, Application Support Engineer.
Support titles Junior Backend Developer, Junior Python Developer, QA Automation Python, API Testing / Test Automation Engineer, Support Engineer with Python, CRM/API Integration Engineer, Internal Tools Engineer.
Location type Remote.
Employment types Full-time and contract.
Locations Remote-first Russia/CIS search first, plus distributed Europe/EMEA teams when the role is English-first and remote. Keep the public signal about remote async delivery and English-first review proof.

Skill Order

  1. Python
  2. FastAPI
  3. PostgreSQL
  4. SQL
  5. REST APIs
  6. OpenAPI
  7. pytest
  8. SQLAlchemy
  9. GitHub
  10. GitHub Actions
  11. Docker Compose
  12. Systems Integration
  13. API Integration
  14. CRM Integration
  15. Webhooks
  16. Telegram API
  17. QA Automation
  18. API Testing
  19. Runbooks
  20. Technical Documentation

Recruiter Discovery Settings

Top 3 visible skills Python, FastAPI, PostgreSQL.
Next skill cluster SQL, REST APIs, OpenAPI, pytest, SQLAlchemy, Docker Compose, GitHub Actions, API Integration, CRM Integration, QA Automation, API Testing, Technical Documentation.
Open-To-Work title order Back End Developer, Python Developer, Junior Backend Developer, Junior Python Developer, Quality Assurance Automation Engineer, Integration Engineer, Application Support Engineer.
Remote filter Remote only for the first public search pass; hybrid/on-site should be handled only when the role is unusually strong.
Resume sharing Use only the current two-page Python Backend / API Automation resume and keep it aligned with the headline, About, skills, and Featured order.
First recruiter click Backend/API Work Samples first, then OpsDesk Lite, then the PDF resume after role fit is clear.

Featured Card Copy

GitHub Recruiter Handoff -> OpsDesk Lite -> LinkedIn Recruiter Packet -> First Backend Role Fit -> Autoschool Intake/Admin work sample -> PDF resume.

Backend/API work samples for remote Python roles. OpsDesk Lite is the first public code proof; Autoschool is the real-work workflow context with synthetic public evidence. Deeper DriveDesk/AI workflow evidence comes after fit.

Backend/API Activity Post

I am narrowing my public proof path around remote-capable Junior Python Backend / API Automation.

Fastest technical review:
GitHub Recruiter Handoff -> OpsDesk Lite -> First Backend Role Fit -> Autoschool Intake/Admin work sample -> PDF resume.

OpsDesk Lite is the first code proof: support request -> FastAPI validation -> SQLAlchemy state -> operator queue -> status transition -> idempotent outbox -> SLA worker -> SQL metrics, with tests, Docker, CI, and privacy audit.

Autoschool remains the real-work context, shown only with synthetic public evidence.

AI tools help me move faster through research, debugging, docs, tests, and review. Architecture, privacy, state boundaries, verification, and shipped quality stay my responsibility.

Review path: https://alexgerlitz.github.io/AlexGerlitz/backend-api-work-samples.html

Best-Fit Boundaries

Primary signal stays Python backend/API automation: FastAPI, PostgreSQL/SQL, REST/OpenAPI, integrations, admin workflows, QA/API checks, Docker/CI handoff, and clear documentation. AI/RAG and cloud/platform evidence are supporting proof after the backend/API fit is clear.

Privacy Boundary

Public work samples use synthetic or redacted evidence only: no real names, phone numbers, chat IDs, admin URLs, logs, dumps, UUIDs, tokens, credentials, or live admin screenshots.

Source-Backed LinkedIn Surface

Checked on 2026-07-04. LinkedIn Featured supports work samples and external links; Open-To-Work uses job titles, locations, employment types, and visibility; recruiter discovery depends on consistent skills, profile fields, job preferences, and resume data.