Clean public review path

DriveDesk AI Operator: backend-owned AI workflow evidence.

I build systems where documents, call audio, transcripts, CRM leads, and knowledge-base records become RAG-backed analysis, lead scoring, follow-up drafts, Telegram approvals, CRM actions, audit logs, retries, and runbooks.

Message on LinkedIn AI backend review pack Hiring signal brief First slice playbook Start conversation PDF resume Role fit Operational readiness AI Operator case Verification pack

FastAPI + PostgreSQL RAG + transcripts n8n + Telegram CRM adapters Docker + CI

Remote role signal

Strongest first context: role title, remote setup, stack, team surface, first-month ownership, and hiring timeline.

DriveDesk AI Operator route: drivedesk-proof-route.html

Workflow project signal

Strongest first context: business process, current tools/data, success condition, constraints, and systems that must stay stable.

Useful first outcome: working slice with tests, docs, and handoff.

Remote role decision

Use this route to evaluate fit for AI automation, backend automation, integration, Docker/CI handoff, internal tools, and first-month ownership.

60-second evidence map

  • Hiring Signal Brief: shortlist-focused evidence for backend-owned state, RAG quality, approval, CRM-safe handoff, retry/dead-letter, idempotency, and dry-run boundaries.
  • Live Postgres evidence: public runtime runs with `storage=postgres`, `rag_eval=2/2`, and restart persistence.
  • Business Scenario Replay: business input -> backend route -> RAG quality -> approval -> CRM handoff evidence.
  • First Slice Playbook: concrete first slices for RAG/transcript, CRM handoff, human approval, and reliability routes.
  • Demo walkthrough: transcript -> RAG -> approval -> CRM-safe handoff in a committed GIF generated from the public-safe offer demo.
  • AI Backend Review Pack: compact route through AI workflow, backend automation, integration, Docker/CI handoff, live evidence, and resume evidence.
  • Public-safe approval evidence: redacted Telegram approval and CRM-safe handoff boundary.
  • Privacy boundary: redaction before RAG retrieval, approval context, and CRM handoff.
  • Acceptance report: live API, RAG quality eval, smoke checks, CI, Pages, and PDF evidence.
  • Profile funnel health: portfolio, pinned evidence repos, GitHub metadata, PDF, demo, and AI Ops docs are checked by live smoke.
  • DriveDesk Core review: FastAPI/PostgreSQL backend depth, OpenAPI, CI, and public demo.
  • Skill evidence: AI automation, Python/FastAPI, PostgreSQL, RAG, CRM/ERP, Docker/CI, and Docker/CI handoff mapped to public evidence.
  • Role fit: remote-capable backend automation and integration, AI automation, Docker/CI handoff, and integration match.
  • First month plan: first 48 hours, week 1, working slice, hardening, demo, and handoff path.
  • Operational readiness: distributed remote-team review of architecture, state ownership, reliability, privacy, integration contracts, CI, runbooks, and handoff quality.

Main review path

  • DriveDesk AI Operator: flagship AI sales/support workflow case.
  • Selected work-sample projects: project-level evidence map for LinkedIn and GitHub review.
  • DriveDesk Core: operations and integration backend foundation.
  • AI Ops Workflow Kit: reviewable FastAPI AI/RAG workflow backend evidence with business scenario replay, first-slice playbook, committed demo walkthrough, deterministic retrieval-quality checks, and PostgreSQL/pgvector state.

What this shows

  • AI tooling accelerates execution while architecture, verification, deployment, and quality stay my responsibility.
  • n8n stays an orchestration layer while backend code owns state, PostgreSQL/pgvector persistence, RAG quality eval, privacy redaction, contracts, retries, audit, and idempotency.
  • External writes are guarded by approvals, dry-run adapters, observable handoff events, and recovery paths.

Best-fit work

  • Remote backend automation and integration and AI automation roles.
  • RAG, transcript/call analysis, approval workflows, CRM/ERP/API integrations, and internal tools.
  • Fixed-scope projects where the output is a working business system with tests, docs, and handoff.