Khent DahayDownload CV

Services / Contract engineering

Build the wedge. Keep the evidence visible.

I work with founders and small teams that need a builder who can read the context, ask direct questions, and own a slice from product ambiguity to shipped software, including agentic AI workflows.

Start a project note
01

Full-stack feature slice

Problem
You have a product gap, but the work crosses UI, API, data, and deployment.
What I deliver
I define the smallest useful slice, build the screens and backend path, document the decisions, and leave handoff notes for the next iteration.
ReactNext.jsDjangoNest.jsPostgreSQL
02

Agentic development

Problem
You need AI agents inside a real workflow, not a demo that breaks when the prompt changes.
What I deliver
I design tool-using agents with clear scope, retrieval boundaries, approval points, fallback behavior, logs, and human handoff states.
Agentic AILangChainGeminiAWS BedrockFastAPIPython
03

Automation and internal tools

Problem
Your team is repeating the same browser, spreadsheet, admin, or release work by hand.
What I deliver
I build scripts, CLIs, Selenium jobs, or desktop utilities that are scoped tightly enough to maintain.
PythonSeleniumPyQt5CLIBeautifulSoup
04

Cloud release cleanup

Problem
Deployments work, but only because one person remembers the order of operations.
What I deliver
I clean up Docker, AWS/Azure, CI/CD, env handling, and release notes so the process can be repeated by the team.
AWSAzureDockerCI/CDGitHub Actions
05

GoHighLevel CRM workflow implementation

Problem
Leads are entering the CRM, but the team cannot reliably see ownership, follow-up status, or the next action.
What I deliver
I map the pipeline, fields, triggers, routing rules, and exceptions; then build, test, and document GoHighLevel workflows that are easier for the team to operate.
GoHighLevelCRMLead routingFollow-upsAutomation

05 / How I keep it practical

Small release first. Cleaner system after.

  1. Audit the existing product, repo, and notes.
  2. Choose one vertical slice with a visible release outcome.
  3. Build with regular checkpoints and plain-language tradeoffs.
  4. Hand off with QA notes, risks, and next steps.

Available remote-first

Bring the rough brief.

Send the current state, the blocker, and what a useful first release should change. I will help turn it into a buildable slice.

khentmark27dahay@gmail.comGitHubLinkedIn