Open-to-Work alignment

Recruiter preferences for remote Python/backend and QA/API roles.

I use this page to match a role quickly: target titles, remote setup, evidence route, and first-contact fit.

Fastest recruiter route: GitHub Recruiter Handoff -> OpsDesk Reviewer Replay -> DriveDesk Business Intake API Handoff -> LinkedIn Recruiter Packet -> First Backend Role Fit -> PDF resume. Use Recruiter Review Pack and Decision-Ready Contact after a concrete role or workflow is on the table.

Message on LinkedIn GitHub handoff LinkedIn profile signal Decision-ready contact LinkedIn recruiter packet Delivery capability Application fit pack Autoschool intake/admin

Remote Full-time Contract Python FastAPI PostgreSQL RAG CRM / ERP Docker / CI

Open-To-Work Preference Set

Preferred search titles	Back End Developer, Python Developer, Quality Assurance Automation Engineer, Integration Engineer, Application Support Engineer.
First-role title support	Junior Backend Developer and Junior Python Developer stay visible in review paths, posts, and outreach copy so the search surface remains honest about first-role intent.
Search expansion 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 stay visible as evidence-backed differentiators, not the first Open-to-Work title filter.
Location type	Remote.
Remote locations	Russian-speaking product/backend teams, distributed backend teams, async-first product teams, and distributed product/operations teams.
Employment types	Full-time and contract.
Availability	Open to remote-capable full-time roles and concrete fixed-scope projects.
Compensation screen	Remote full-time, fixed-scope, and distributed roles should include a compensation band before a call; exact fit is discussed privately.
Strongest match	My strongest match is a bounded first Python/backend task, internal operations tool, API/CRM integration, QA automation Python bridge, or backend-owned AI workflow with tests, logs, docs, deployment path, and handoff.
Distributed async signal	Written review paths, English-first docs, async technical review, privacy/integration boundaries, CI, runbooks, and timezone-friendly handoff.

Source-Backed Search Rationale

Checked on 2026-07-04.

LinkedIn Open-to-Work explicitly uses job titles, location type, locations, employment types, and visibility, so the profile should not spread the first-job surface across unrelated titles.
LinkedIn Recruiter exposes skill matching and skill filters, so the top visible skills should stay tied to public evidence and role keywords.
LinkedIn Featured is an evidence surface, so first visible work samples should be short review paths: GitHub Recruiter Handoff, OpsDesk Reviewer Replay, Backend/API Work Samples, LinkedIn Recruiter Packet, First Backend Role Fit, Autoschool Intake/Admin work sample, and PDF Resume before deeper routes.
GitHub profile README and pinned repositories remain the fastest public technical review path, so the README, GitHub Recruiter Handoff, pins, CI, and PDF resume must stay aligned even when a browser route is not needed.
Current market scan supports band-aware private screening for serious remote full-time outreach. The strongest first-job path is not a generic junior Python label; it is Python backend/internal tools, QA/API Python, support-with-Python, integration/API/CRM, or AI workflow with backend/API proof with one public work sample and a first useful slice. Broader distributed-team scan supports keeping English-first async/team evidence visible while keeping the first screen role/workflow focused.

Profile Surface

Headline	Python Backend Developer \| FastAPI, PostgreSQL, API/CRM Integrations \| QA Automation Python support
About lead	I build backend-owned workflow slices for real business processes: FastAPI endpoints, PostgreSQL state, REST/OpenAPI contracts, admin queues, API/CRM mappings, pytest/API smoke checks, docs, and handoff notes.
Profile signal route	LinkedIn Profile Signal keeps the headline, About, Featured order, Open-To-Work fields, skill order, and no-overclaim boundaries aligned.
Open-To-Work titles	Back End Developer, Python Developer, Quality Assurance Automation Engineer, Integration Engineer, Application Support Engineer.
Featured first order	Backend/API Work Samples, OpsDesk Reviewer Replay, LinkedIn Recruiter Packet, PDF Resume, Autoschool Intake/Admin work sample.
Top skill order	Python, FastAPI, PostgreSQL, REST APIs, OpenAPI, GitHub, pytest, Docker Compose, Systems Integration, CRM/API Integration.

Recruiter Search Keywords

Python, FastAPI, PostgreSQL, Docker, GitHub Actions, RAG, Vector Databases, CRM, ERP, API Integration, workflow integration, n8n, Telegram, QA Automation Python, OpenAPI, pgvector, CI, runbooks, audit logs, idempotency, retries, backend-owned state, operational handoff.

First Contact Fit

Send one remote role or one business workflow, one success condition, the systems involved, the ownership boundary, and the timeline.

Best First Outcome

Role/project fit read, risky assumptions, smallest responsible working slice, and verification route.

Recruiter Filter Map

I use this as the public filter map for LinkedIn Recruiter-style searches and fast manual screening.

Title	Junior Backend Developer, Junior Python Developer, Python Automation Engineer, QA Automation Python, Support Engineer with Python, Back End Developer, Python Developer, Integration Engineer, CRM/API Integration Engineer, and Internal Tools Engineer.	Application Fit Pack
Skills	Python, FastAPI, PostgreSQL, Docker, GitHub Actions, RAG, pgvector, CRM/ERP/API integration, API Integration, OpenAPI, QA Automation Python, n8n, Telegram.	Skill Evidence
Remote / location	Remote-capable, Russian-speaking product/backend teams, distributed teams, distributed async review, and written handoff.	Verification Pack
Language / review	Russian-speaking product review or English-first public docs, async review paths, CI, smoke checks, runbooks, diagrams, and handoff notes.	Verification Pack
Featured evidence	GitHub Recruiter Handoff, OpsDesk Reviewer Replay, Backend/API Work Samples, LinkedIn Recruiter Packet, First Backend Role Fit, Autoschool Intake/Admin work sample, and PDF Resume first; Recruiter Review Pack, Delivery Capability, Application Fit Pack, DriveDesk AI Operator route, DriveDesk Core, AI Backend Review Pack, Verification Pack, and Decision-Ready Contact after first context.	GitHub Recruiter Handoff
Application / ATS shortlist	Parser-readable lanes for Python backend/internal tools, Integration/API/CRM, QA Automation Python, and AI workflow automation.	Application Fit Pack
Seniority / specialist signal	Backend-owned state, AI-output review, CRM/ERP/API adapter contracts, privacy boundary, audit, retries, idempotency, smoke checks, and runbooks.	AI Backend Review Pack

Recruiter Boolean Search Strings

I use short keyword strings when a recruiter needs to find my profile by technical intent.

(RAG OR "AI workflow" OR "workflow automation") AND (Python OR FastAPI) AND (CRM OR ERP OR integration)
(Python OR FastAPI OR SQL) AND ("internal tools" OR admin OR automation) AND (remote OR junior)
(Python OR FastAPI) AND (PostgreSQL OR pgvector) AND (Docker OR "GitHub Actions") AND (remote OR async)
("QA Automation" OR "Test Automation" OR "API Testing") AND Python AND (REST OR OpenAPI OR pytest)
("Backend Automation Engineer" OR "Internal Tools Engineer") AND (OpenAPI OR audit OR outbox OR "workflow state")
("Integration Engineer" OR "API Integration" OR "workflow integration") AND (CRM OR ERP OR 1C OR banking OR webhooks) AND (idempotency OR retries OR audit)
(Docker OR "Docker Compose" OR CI OR "health checks" OR runbooks) AND FastAPI AND Python

Docker/CI query boundary: use it for backend delivery handoff, reliability, health checks, logs, and runbook evidence. Cloud/platform terms stay secondary unless a role gives a reviewed support boundary around them.

LinkedIn Skills Search Surface

My profile is easiest to evaluate when every major skill filter has the same public pattern: it appears in the visible LinkedIn surface, it is attached to real experience, and it points to inspectable evidence instead of staying as a loose keyword.

Python / backend / internal tools	Headline, About, Skills, Autoschool54 experience, OpsDesk Reviewer Replay, Delivery Capability, Application Fit Pack, First Backend Role Fit, Autoschool Intake/Admin work sample, and DriveDesk Core route.	OpsDesk Reviewer Replay, Delivery Capability, Application Fit Pack, First Backend Role Fit, Backend Role Fit, Autoschool Intake/Admin work sample, DriveDesk Core, AI Backend Review Pack, Verification Pack
AI workflow / RAG	Headline, About, Skills, Featured DriveDesk AI Operator route, and AI Ops evidence links.	DriveDesk AI Operator route, AI Ops Employer Trigger Evidence, AI Automation Role Fit
CRM / ERP / API integration	About, Experience, Skills, Services, and review paths for adapter contracts and handoff.	Operational Readiness, Case Studies, DriveDesk AI Operator
Reliability / Docker handoff	Experience, Skills, Featured verification routes, and work-sample projects with CI/smoke/runbook evidence.	DeployMate, Verification Pack, First 30 Days Delivery Plan

Best high-signal skills to keep aligned across LinkedIn and review paths: Python, FastAPI, PostgreSQL, Docker, GitHub Actions, RAG, Vector Databases, pgvector, OpenAPI, CRM, ERP, API Integration, workflow integration, QA Automation Python, n8n, Telegram, runbooks, audit logs, idempotency, retries, and operational handoff.

LinkedIn skill-filter target: keep Python, FastAPI, PostgreSQL, REST/OpenAPI, GitHub, Docker, pytest, Systems Integration, CRM/API integration, QA/API terms, and AI/RAG workflow terms tied to public evidence. Broad DevOps/platform terms should support reliability and handoff proof only, not become the first role claim.

Current Search-Surface Audit

This is the tight search surface I want recruiters, hiring managers, and project clients to use before sending a message.

Preferred search titles	Back End Developer, Python Developer, Quality Assurance Automation Engineer, Integration Engineer, Application Support Engineer.	Use this set for backend/Python/QA/API/integration/support screens, not standalone AI.
First-role title support	Junior Backend Developer, Junior Python Developer, Support Engineer with Python, QA Automation Python, and API Testing / Test Automation Engineer.	Use these in review paths, posts, and outreach copy when the first task is a bounded backend/API slice.
Search expansion 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.	Use these in posts, review paths, and recruiter search strings; keep AI/RAG as review evidence, not a first-title filter.
Top skills order target	Python, FastAPI, PostgreSQL, Docker, GitHub Actions, RAG, Vector Databases, pgvector, OpenAPI, CRM, ERP, API Integration, workflow integration, QA Automation Python, n8n, Telegram, audit logs, idempotency, retries, runbooks.	Keep the first visible skills tied to evidence, not generic AI claims.
LinkedIn skill filter target	Python, FastAPI, PostgreSQL, REST/OpenAPI, GitHub, Docker, pytest, Systems Integration, CRM/API integration, QA/API terms, AI/RAG workflow evidence, and reliability handoff terms.	Keep visible skills tied to evidence; keep broad DevOps/platform terms as support evidence, not the first role claim.
Services search surface	Cloud Application Development, Web Development, Application Development, Custom Software Development, Information Management, and IT Consulting are broad marketplace labels; the profile overview and media should route them to Python/backend automation, AI workflow, integration, internal tools, QA/API verification, and Docker/CI handoff evidence.	Route each request through LinkedIn Services Fit, Python Backend & AI Workflow Services, and DriveDesk AI Operator route when deeper AI workflow review is needed.
Services response loop	Target first response: fit/no-fit, risky assumptions, smallest responsible first slice, review path, and handoff path.	Strongest for requests that name the current workflow, systems involved, one observable success condition, and what must not break.

LinkedIn Profile Alignment

This page defines the LinkedIn setup and target alignment I want recruiters to see before sending a message.

Headline	Python Backend Developer \| FastAPI, PostgreSQL, API/CRM Integrations \| QA Automation Python support
About / Experience	First-person ownership language around Python backend/application-support work, backend-owned AI workflow and operations systems, AI-assisted engineering workflow, evidence-slice contact language, real Autoschool54 operations since March 2024, and privacy-safe public evidence.
Profile signal route	LinkedIn Profile Signal is the aligned headline, About, Featured, Open-To-Work, skill-order, and boundary page for the visible LinkedIn profile.
Featured route target	GitHub Recruiter Handoff at `https://github.com/AlexGerlitz/AlexGerlitz/blob/main/GITHUB_RECRUITER_HANDOFF.md`, OpsDesk Reviewer Replay, Backend/API Work Samples, LinkedIn Recruiter Packet, First Backend Role Fit, Autoschool Intake/Admin work sample, and PDF Resume first. Recruiter Review Pack and Decision-Ready Contact are for forwarding or next-step context after a concrete role or workflow appears; Delivery Capability, Application Fit Pack, DriveDesk AI Operator route, DriveDesk Core, AI Backend Review Pack, and Verification Pack are deeper routes after first context.
Open-to-Work	Remote job titles and skill filters aligned with Python/backend automation, internal tools, API/CRM integration, QA Automation Python, AI workflow automation, and reliability handoff.
Resume / handoff	Decision-Ready Contact and Start Conversation routes before PDF Resume for internal sharing.
Services	LinkedIn Services overview and media should route requests toward Python/backend automation, AI workflow, integration, internal tools, QA/API verification, Docker/CI handoff, or data-workflow evidence instead of generic web/app work.

LinkedIn Featured Alignment

The first LinkedIn Featured card should make the review path obvious without asking a recruiter to infer it from the page title.

Surface	Public signal	LinkedIn copy
Featured card: Backend/API Work Samples - Alex Gerlitz	First visible work-sample route for profile viewers and recruiter shares.	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, with DriveDesk Business Intake API Handoff in the first proof route.
Featured first card order	Keep the backend/API route first so the profile opens with the safest first-role evidence.	Backend/API Work Samples first; DriveDesk, AI backend, and recruiter proof pack remain deeper routes after fit.
About fast review path	Keep the compact public route in About, and make the linked route start with GitHub Recruiter Handoff.	Fast review path points to the backend/API work-sample route; that route starts with GitHub Handoff, OpsDesk Reviewer Replay, role fit, Autoschool evidence, and PDF resume.

Recruiter Decision Fit

Use this section to decide which role lane, review path, and first assignment are worth discussing.

Best-fit role lane	Python Backend / API Automation with FastAPI, PostgreSQL, API/CRM Integrations, and QA/API Python support
First useful assignment	One FastAPI endpoint, data model, admin queue step, API/CRM mapping, API smoke check, SQL/data check, or runbook gap that can be reviewed as a bounded shipped slice.
Fastest evidence	GitHub Recruiter Handoff -> OpsDesk Reviewer Replay -> DriveDesk Business Intake API Handoff -> LinkedIn Recruiter Packet -> First Backend Role Fit -> PDF resume. Use Recruiter Review Pack after the backend/API fit is clear.
Why the sample matters	Autoschool Intake/Admin shows request intake, backend validation, stored state, admin review, operator status, tests or smoke checks, and handoff notes using synthetic public evidence.
Public evidence boundary	Public work samples use synthetic or redacted evidence only: no real names, phone numbers, chat IDs, admin URLs, logs, dumps, tokens, credentials, or live admin screenshots.

Public Profile Focus

The public profile is intentionally narrow: remote backend/API-heavy roles where one useful workflow slice can prove value quickly.

Primary focus	Remote-capable Junior Python Backend / API Automation.
Adjacent lanes	QA/API Python, CRM/API Integration, Internal Tools, and Support Engineer with Python when the role is backend/API-heavy.
Strongest first code proof	OpsDesk Reviewer Replay: support request -> FastAPI validation -> SQLAlchemy state -> operator queue -> status transition -> idempotent outbox -> SLA worker -> SQL metrics, tests, Docker handoff, and CI. DriveDesk Business Intake API Handoff is the real-work API/admin/outbox handoff proof with synthetic public evidence only.
Preferred search titles	Back End Developer, Python Developer, Quality Assurance Automation Engineer, Integration Engineer, Application Support Engineer.
AI positioning	AI tooling accelerates research, implementation, debugging, docs, tests, and review; architecture, privacy, state boundaries, verification, and shipped quality remain engineering-owned.
Scope boundary	Docker/CI is backend delivery handoff evidence: Compose, CI, health checks, logs, runbooks, and recovery notes.

Search Intent To Evidence Stack

Application system, ATS, or quick shortlist	Application Fit Pack -> Role Fit Message Examples -> Delivery Capability -> Skill Evidence
Python Backend, Internal Tools, Support Engineer with Python, or Integration Engineer	OpsDesk Reviewer Replay -> Application Fit Pack -> First Backend Role Fit -> Autoschool Intake/Admin work sample -> DriveDesk Core Review -> Verification Pack
QA Automation Python, API Testing, or Test Automation Engineer	Application Fit Pack -> Skill Evidence -> Verification Pack
AI workflow, RAG, or automation review	DriveDesk AI Operator route -> AI Backend Review Pack -> AI Automation Role Fit
CRM, ERP, API Integration, or Internal Tools	Autoschool Intake/Admin work sample -> Case Studies -> Verification Pack -> Start Conversation
Reliability, Docker/CI, or operational handoff	Verification Pack -> DeployMate evidence -> Operational Readiness

Evidence Map

GitHub Recruiter Handoff: GitHub-native wrapper for role lane, first proof, PDF, markdown work samples, recruiter prompt, and privacy boundary.
Decision-Ready Contact: minimum context, fit read, risk check, smallest responsible first slice, review path, and next route.
LinkedIn Profile Signal: aligned headline, About, Featured, Open-To-Work, skill-order, and no-overclaim boundaries.
LinkedIn Recruiter Packet: search fit, review order, and first result.
Delivery Capability: current role-market fit, first useful workflow slice, AI-assisted delivery boundary, and Docker/CI handoff boundary.
Application Fit Pack: parser-readable application lanes, exact keywords, first useful result, review path, and not-my-first-lane boundary.
First Backend Role Fit: first-role backend evidence for bounded tickets, reviewable diffs, tests or smoke checks, docs, and handoff.
Backend Role Fit: fast backend/internal-tools review path before deeper portfolio review.
Autoschool Intake/Admin work sample: first-job backend evidence for Telegram intake, validation, database state, admin queue, status workflow, and privacy boundary.
AI Automation Role Fit: precise role-fit route for AI automation, RAG, structured outputs, approvals, CRM/API handoff, tests, logs, and runbooks.
DriveDesk AI Operator route: flagship backend-owned AI workflow review path.
AI Backend Review Pack: compact route through Python/backend automation, AI workflow, integration, Docker/CI boundary, verification, and resume evidence.
Operational Readiness: distributed remote-team review of architecture, reliability, privacy, CI, runbooks, and handoff quality.
PDF Resume: compact resume route after the decision-ready contact context is clear.

Not My Target

Onsite-only roles, pure prompt/content tasks, isolated static websites, student/course assignments, standalone game clones, generic mobile/ecommerce apps without backend/integration ownership, and undefined work where success cannot be tested or handed off.