Remote Role
- Role title and remote setup.
- Stack, product domain, and team surface.
- First-month ownership or success condition.
- Hiring timeline and process.
Fast contact route
Send one role, workflow, or technical problem.
I am best evaluated through a concrete first slice: remote backend/platform work, AI/RAG workflows, CRM/ERP/API integrations, internal tools, Docker/CI, deployment, or recovery work. I use AI aggressively to compress execution time, then verify with code, tests, logs, docs, and runbooks.
Current Public Signal
The latest LinkedIn signal is the DriveDesk Core post: a technical proof route for backend/platform, operations, integration, AI workflow, Docker, CI, and review conversations.
Open the DriveDesk AI Operator case, review DriveDesk Core, open role fit, or use the role fit pack for a fast public review.
Best first message: a role, project, or messy workflow plus one success condition.
Technical Problem
- Current workflow, system, or failure mode.
- What should improve first.
- APIs, database, CRM/ERP, infrastructure, or docs involved.
- What must not break.
Fixed-Scope Project
- Manual or fragile process.
- Systems, data, and access constraints.
- Practical definition of done.
- Deadline, budget range, hosting, and handoff depth.
Remote role
Best fit: backend, platform, AI automation, DevOps, integrations, internal tools, Python/FastAPI/PostgreSQL, Docker/CI.
Fixed-scope project
Best fit: one messy workflow, one success condition, and a working slice that can become an owned system.
Proof review
Fast path into public repos, CI, docs, demo paths, runbooks, and role-to-proof mapping.
Role Context
- Role and remote setup.
- Stack and systems.
- First-month ownership.
- Hiring process and timeline.
- Relevant vacancy, product, or technical link.
Project Context
- Problem and current tools/data.
- Success condition.
- Deadline and budget range.
- Constraints and output needed.
- Useful context link or file.
What I Send Back
- Risky assumptions and missing information.
- The smallest responsible first slice.
- Likely data model, API, integration, or DevOps boundary.
- Verification plan: tests, smoke checks, logs, docs, demo path, or runbook.
- What should wait until the first working path proves the direction.