Public role fit

Remote backend/platform and AI automation 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.

DriveDesk proof route Open AI Operator case AI Ops proof status Live owner proof AI Ops acceptance AI Ops CI workflow PDF resume GitHub-readable version
Remote-only Python/FastAPI PostgreSQL AI/RAG CRM integrations Docker/CI Runbooks

AI Automation

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

AI Ops public proof status

Backend / Platform

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

DriveDesk Core review

Integration / DevOps

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

Verification pack

Fast Review Path

  1. Open the DriveDesk proof route for the short profile, current offer, and proof links.
  2. Open DriveDesk AI Operator for the main AI workflow case direction.
  3. Open AI Ops proof status and reviewer acceptance for live demo, CI, smoke, and evidence coverage.
  4. Open DriveDesk Core for backend/platform foundation proof.
  5. Open the verification pack for demos, CI, docs, and runbook evidence.

Deeper AI Ops proof, including the live owner proof, is linked from the public proof 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.