Remote Role
Backend, Python, AI automation, API integration, internal tools, or Docker/CI handoff support.
- Best evidence: Hiring decision route.
- First-month plan: delivery plan.
- Skill map: skill evidence.
I build backend-owned AI workflow and operations systems for real businesses: RAG, transcript and call analysis, approval flows, CRM/ERP/API adapters, FastAPI/PostgreSQL backends, Docker/CI, runbooks, and recovery paths. The fastest start is one success condition and enough context to prove the first responsible slice.
AI workflow automation, CRM/ERP/API adapter, backend automation and integration slice, Docker/CI recovery sprint, or DriveDesk AI Operator-style work sample.
Best fit: remote-capable work with a concrete success condition, real systems/data, and a need for tests, logs, docs, deployment, and handoff.
Send one remote role or one workflow plus one success condition. I will return a fit read, risky assumptions, the smallest responsible first slice, review path, and the right next route: remote role conversation, fixed-scope project, technical review, or no-fit.
Backend, Python, AI automation, API integration, internal tools, or Docker/CI handoff support.
One workflow, one technical outcome, one review path, and a handoff route.
Code, CI, live smoke, docs, runbook, screenshots, and public evidence before claims.
For routing from employer pain to repo evidence, use AI Ops Employer Trigger Evidence. It maps AI workflow/RAG, CRM/ERP/API integration, Python/backend ownership, QA/API verification, and reliability handoff triggers to inspectable repo evidence.
Strong match: remote-capable role or fixed-scope work that needs backend automation, integration ownership, AI workflow automation, internal operations tooling, backend delivery handoff support, or one working slice with tests, logs, docs, and handoff.
Not my target right now: onsite-only roles, pure prompt/content tasks, isolated static websites, student/course assignments, standalone game clones, generic mobile/ecommerce apps without backend/integration ownership, or undefined outcomes with no way to verify success.
Send the role or workflow, the systems involved, the first useful outcome, timeline, access constraints, and commercial constraints. I will respond with fit, risky assumptions, the smallest responsible first slice, and the review path.