Public role fit

Remote Python/backend automation and AI workflow work around real workflows.

I am strongest where a messy business process needs to become a working system: FastAPI/PostgreSQL backend, RAG/transcript workflow, integration adapter, admin/operator surface, Docker/CI path, logs, docs, and runbook.

Message on LinkedIn LinkedIn Recruiter Packet First backend fit Autoschool intake/admin Decision-ready contact

Fastest role-fit route: LinkedIn Recruiter Packet -> DriveDesk Business Intake API Handoff -> First Backend Role Fit -> Decision-Ready Contact; use the PDF resume after the evidence route is clear.

Search-match stack: Python, FastAPI, PostgreSQL, pytest, REST APIs, OpenAPI, Docker, Docker Compose, GitHub Actions, RAG, n8n, Telegram, CRM/ERP/API integrations, workflow integration, Backend Development, QA Automation Python, Workflow Automation, and PostgreSQL/pgvector-backed workflows.

Remote-capable Python/FastAPI PostgreSQL Docker n8n Telegram AI/RAG RAG workflow evidence CRM integrations Docker/CI Runbooks

AI Workflow Evidence

DriveDesk AI Operator-style systems: document/transcript/lead ingestion, RAG retrieval with quality eval, analysis JSON, scoring, routing, Telegram approvals, outbox worker handoff, CRM handoff, auditability, and operator control.

AI Ops public evidence status

Backend / Internal Tools

FastAPI/PostgreSQL systems, records, roles, workflow state, OpenAPI, tests, Docker, CI, docs, audit/outbox, and adapters.

DriveDesk Core review

Integration / QA / Reliability

CRM/ERP/1C/bank/API boundaries, mapping, validation, retries, logs, deployment, health checks, recovery, and runbooks.

Verification pack

Search-fit role targets

Best matches: Junior Backend Developer, Junior Python Developer, Python Backend Engineer, Integration Engineer, CRM/API Integration Engineer, Internal Tools Engineer, QA Automation Python, and Docker/CI handoff roles. AI workflow and RAG stay visible as evidence-backed differentiators, not the first title I need to be screened under.

These titles map to the same review path: DriveDesk AI Operator, AI Ops Workflow Kit, DriveDesk Core, DeployMate, fixed-scope offers, and the first month delivery plan.

Open AI workflow role fit, open full role targets, or open skill evidence.

Fast Review Path

  1. Open the DriveDesk AI Operator route for the short profile, current offer, and evidence links.
  2. Open DriveDesk AI Operator for the main AI workflow review path.
  3. Open AI Ops evidence status and reviewer acceptance for CI, runtime-boundary, smoke, and evidence coverage.
  4. Open DriveDesk Core for backend/internal-tools foundation evidence.
  5. Open the verification pack for demos, CI, docs, and runbook evidence.

Deeper AI Ops evidence, including public-safe approval evidence, is linked from the public evidence status when a technical reviewer wants full drill-down.

Useful First Context

  • Role or project surface.
  • Systems, APIs, documents, transcripts, or CRM objects involved.
  • What should improve first.
  • What should remain under human approval.
  • What must be logged, tested, audited, or recoverable.