Open to consulting engagements and full-time roles

AI-native senior engineering for cloud and web

Senior engineering help for AI, cloud, and web systems.

I help teams move from idea, backlog, or stuck implementation to production-ready software. The work is practical, architecture, prototypes, integrations, performance, and hands-on delivery.

Currently weighing consulting engagements and senior engineering or tech leadership roles. Reach out either way. Eastern Time, flexible availability.

engineering.manifest.ts

// What I bring to the table

export const consulting = {

openTo: ["consulting", "full-time", "tech leadership"],

approach: "AI-native, in workflow and architecture",

experience: "17+ years shipping production web platforms",

mostRecent: "Web Tech Lead, WebFirst (gov + AI)",

timezone: "America/New_York",

schedule: "flexible, weekdays + weekends",

modes: ["architecture review", "MVP", "rescue", "impl"],

stack: ["AI/RAG", "MCP", "AWS + Cloudflare", "Next.js", "Drupal"],

startsIn: "1 to 2 weeks",

};

$ contact --email davo20019@gmail.com

✓ ready to talk

AI-native engineer. 17+ years of production judgment, multiplied by agents I drive through every step of delivery.

Most recently Web Tech Lead at WebFirst, where I built security-focused government and AI platforms. Previously Director of Web Development and Solutions Architect at New Target, leading global teams of 10+ engineers across enterprise Drupal, WordPress, and Next.js delivery.

17+

Years building production web platforms

10+

Engineers led across three continents

AI-native

Workflow and architecture, not bolted on

Gov

Security-focused public-sector delivery

AI-native by default

How I work

AI-native means I keep agents in my engineering workflow across scoping, design, code, review, and ship. 17+ years of production work decides what to build, what to skip, and what to ship. Speed is a side effect, not the product.

01Judgment

Senior engineering, not vibe coding

Every architectural call, every PR, every deploy is mine. AI is a tool I use, not a stand-in for the work or the experience behind it.

02Workflow

I keep agents in the loop

I use AI throughout scoping, design, code, and review. Where it adds value I lean in. Where it does not, I do the work myself.

03Quality

Faster cycles, not lower bars

Same standards as hand-written code. Tests, observability, accessibility, and rollback paths included by default.

Recently Shipped

A sampling of side-project work that mirrors the kind of help I can offer.

View all projects

What I Can Help With

These are the areas where I contribute quickly without a long ramp-up. Each card lists the concrete outcomes you can expect.

AI & Agents

AI integration and LLM implementation

Add LLM features to existing products with tool use, structured outputs, prompt workflows, and cost-aware model routing.

  • Working AI features inside real apps
  • Cleaner prompts and safer outputs
  • Latency and token-cost tuning
AI & Agents

RAG and vector search

Design retrieval pipelines that connect documents, databases, embeddings, vector stores, and application UX.

  • RAG architecture and implementation
  • Milvus, pgvector, or Vectorize setup
  • Search quality debugging
AI & Agents

Agent systems and MCP

Build agent workflows that call tools, inspect data, coordinate steps, and expose useful capabilities through MCP.

  • MCP servers and tool interfaces
  • Agent workflow design
  • Guardrails for production use
Cloud & Web

Cloud and edge architecture

Plan and ship production applications across AWS, Cloudflare, Vercel, and edge platforms. Workers and Durable Objects when edge fits. Lambda, S3, and managed services when it does not. Match the platform to the workload, not the other way around.

  • Multi-cloud architecture for AI and web
  • Edge, serverless, and managed-services trade-offs
  • Deployment, performance, and cost fixes
Cloud & Web

Next.js full-stack builds

Build or improve App Router projects with TypeScript, i18n, API routes, static generation, and Cloudflare deployment.

  • Feature implementation
  • Routing and metadata cleanup
  • OpenNext and deployment support
CMS Modernization

Drupal and WordPress modernization

Modernize legacy CMS work with custom modules, integrations, search, migration planning, and performance improvements.

  • Drupal and WordPress technical fixes
  • Search and integration work
  • Upgrade and migration planning

Ways to Work Together

Pick the engagement that matches where you are. With agents in my workflow, most engagements land in a fraction of the traditional timeline. Scope is written down before any work starts.

Architecture review

2 to 5 days

A focused review of an app, AI workflow, deployment, or technical plan. With agents in the loop, I turn multi-week reviews into a same-week deliverable without losing depth.

Best for
Teams about to commit to a stack, AI workflow, or rebuild
Deliverable
Written report, risk register, prioritized next steps, plus a Loom walkthrough

Prototype or MVP

1 to 2 weeks

A working build that proves the integration, workflow, or user experience. I use agents to compress scaffolding and boilerplate into days, then drive the parts that need senior judgment.

Best for
Validating an integration, workflow, or product hypothesis
Deliverable
A small working build, deployed, with a clean repo you can keep

Implementation support

Hours to days per task

Hands-on development for a defined feature, integration, migration, or performance improvement. Most defined work lands in a fraction of the traditional timeline. Tests, reviews, and rollback paths included.

Best for
Teams shipping a defined feature, integration, or migration
Deliverable
Code, PR reviews, and short written updates with Loom walkthroughs

Rescue and debugging

Hours to days

Help with broken deployments, slow apps, brittle AI features, or unclear technical direction. I use agents to surface root causes fast, then drive the fix and the guardrails.

Best for
Broken deploys, slow apps, brittle AI features, unclear direction
Deliverable
A working system, written root-cause notes, and guardrails so it does not happen again

Simple Process

Async-first, written down, and visible from day one. I keep agents in the loop, but every step that needs senior judgment stays mine.

  1. 01Day 1

    Scope

    We clarify the problem, constraints, timeline, and what success should look like. I use agents in discovery to cover ground that used to take a week of meetings.

  2. 02Day 1 to 2

    Plan

    Soon after scoping, you have a written plan with risks, assumptions, and a clean first milestone.

  3. 03Day 2 onward

    Build

    I execute in small increments. Daily written updates and Loom walkthroughs so progress stays visible without sync meetings.

  4. 04Wrap-up

    Wrap

    Code, documentation, and a written handoff so your team can keep going without me.

Good Fit

  • You need senior technical help without hiring a full-time engineer.
  • You have an AI, web, or cloud project that needs production judgment.
  • You want a builder who can advise and also ship code.
  • You prefer direct communication, clear scope, and practical tradeoffs.
×

Probably Not a Fit

  • ×You are optimizing for the cheapest possible rate over senior judgment.
  • ×You want someone to skip code review, tests, or accessibility to ship faster.
  • ×The work is deep specialty far outside web, cloud, AI, or content systems.
  • ×There is no clear scope and no path to clarifying one together.

Common Questions

If your question is not here, the fastest answer is a 30-minute call.

Book a 30-minute Strategy Call
Are you open to full-time roles too?
Yes. I am weighing senior engineering and tech leadership roles alongside consulting engagements. Reach out either way and we can figure out the right shape.
How quickly can you start?
Usually one to two weeks from a signed scope. Sometimes sooner for short reviews.
Do you sign NDAs?
Yes. Mutual NDAs are fine before any technical conversation. I can send a template or sign yours.
How does pricing work?
Most engagements are fixed-fee against a written scope. Open-ended work runs hourly with a weekly cap so there are no surprises.
How do we communicate during the work?
Async first. Loom walkthroughs and a weekly written update. Synchronous calls when they actually unblock something.
What is your time zone and availability?
Eastern Time. Flexible during the week and on weekends, with quick response times.
Will I own the code?
Yes. All deliverables transfer to you on payment, with documentation included.
Can you work with my existing team?
Yes. I am comfortable in code review, pairing, and technical-lead support, and I keep written notes so async teams stay informed.

Have a project, a team, or a role I should know about?

Send a note or book a short call. A focused conversation is usually enough to see whether there is a fit on consulting or a full-time role.