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 Reviewer Replay 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. DriveDesk Business Intake API Handoff shows the real-work API/admin/outbox route with synthetic evidence only.

Message on LinkedIn Backend/API work samples OpsDesk Reviewer Replay 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 Reviewer Replay, where synthetic webhook intake becomes validated FastAPI state, duplicate idempotency, operator queue, status handoff, outbox dispatch, metrics, support diagnostics, and OpenAPI checks without local Docker.

Real-work context: since March 2024 I have supported Autoschool54 / DriveDesk backend and application-support work remotely. The safest public proof is DriveDesk Business Intake API Handoff: bot-style intake -> backend validation/FastAPI preview -> validated business record -> admin queue -> status transition -> outbox/integration handoff, shown with synthetic evidence only.

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

Python
FastAPI
PostgreSQL
SQL
REST APIs
OpenAPI
pytest
SQLAlchemy
GitHub
GitHub Actions
Docker Compose
Systems Integration
API Integration
CRM Integration
Webhooks
Telegram API
QA Automation
API Testing
Runbooks
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	OpsDesk Reviewer Replay first, then Backend/API Work Samples, then DriveDesk Business Intake API Handoff, then the PDF resume after role fit is clear.

Featured Order

OpsDesk Reviewer Replay - first visible code proof.
Backend/API Work Samples - public route for LinkedIn profile views.
DriveDesk Business Intake API Handoff - real-work API/admin/outbox handoff proof.
LinkedIn Recruiter Packet - 30-second role lane and review order.
First Backend Role Fit - what a team can safely give me first.
PDF Resume - compact handoff after role fit is clear.

Featured Card Copy

GitHub Recruiter Handoff -> OpsDesk Reviewer Replay -> DriveDesk Business Intake API Handoff -> LinkedIn Recruiter Packet -> First Backend Role Fit -> PDF resume.

Backend/API work samples for remote Python roles. OpsDesk Reviewer Replay is the first public code proof; DriveDesk Business Intake API Handoff is the real-work API/admin/outbox handoff proof with synthetic public evidence. Deeper 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 Reviewer Replay -> DriveDesk Business Intake API Handoff -> First Backend Role Fit -> PDF resume.

OpsDesk Reviewer Replay 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.

DriveDesk Business Intake API Handoff shows the real-work shape: bot-style intake -> backend validation/FastAPI preview -> admin queue -> status transition -> outbox/integration handoff, with synthetic public evidence only.

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.