Inbound brief

Send enough context for a concrete engineering next step.

The fastest useful message has one decision to make, one success condition, the systems involved, and the proof route that should be checked. I work best on remote backend/platform, AI automation, RAG workflows, CRM/ERP/API integrations, internal tools, Docker/CI, DevOps recovery, and DriveDesk AI Operator-style builds.

Message on LinkedIn LinkedIn Services Start conversation Contact routes DriveDesk proof route PDF resume

Best Immediate Starts

AI workflow automation, CRM/ERP/API adapter, backend/platform slice, DevOps recovery sprint, or DriveDesk AI Operator-style proof route.

Good Fit Filter

Strongest match: backend-owned AI workflow, CRM/ERP/API integration, internal operations tool, DevOps hardening, 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.

Remote Role

Useful first context for a recruiter or hiring manager.

  • Role title, remote setup, team surface, and hiring timeline.
  • Product domain, stack, systems, and first-month ownership.
  • Current pain: speed, reliability, integrations, AI workflow, DevOps, internal tools, or support load.
  • Vacancy, product, docs, or technical description if public.

Fixed-Scope Project

Useful first context for a founder, operator, or technical owner.

  • Business process, current tools, data sources, APIs, databases, documents, or chats.
  • Practical definition of done and what must not break.
  • Required output: working slice, integration adapter, AI workflow, internal tool, DevOps fix, runbook, or recovery plan.
  • Deadline, commercial constraints, access limits, hosting, compliance, language, timezone, and handoff depth.

Technical Review

Useful first context when the decision depends on evidence.

  • Repository, demo, system link, architecture page, CI run, or public proof target.
  • Claim, risk, failure mode, or unclear boundary to validate.
  • Safe logs, screenshots, error text, recent changes, and current success check.
  • What must keep working while the review is happening.

What I Send Back

Engineering read

  • Risky assumptions and missing information.
  • The smallest responsible first slice.
  • Likely backend, data, adapter, approval, or DevOps boundary.
  • What should wait until a working path proves the direction.

Proof path

  • Relevant repo, page, demo, CI run, doc, or smoke route.
  • Evidence needed for the decision: tests, logs, screenshots, runbook, or public demo.
  • Fit against DriveDesk AI Operator, AI Ops Workflow Kit, DriveDesk Core, DeployMate, or MPlusForm.
  • Next action that avoids a generic intro call.

Review Before Contacting