Eric Valens / Ventura

Engineer.
Builder.
AI, put to work.

I’m a Senior Software Engineer at GoodTime.io and the founder of Chimpipi. I take ambiguous problems from research to launch, and build workflows that help local businesses get things done.

HOW I WORK
01 / InputA real problemResearch before code.
02 / BuildParallel agentsOne brief. One focused fix.
03 / CheckReview & testI test every fix.
✓
Human-approvedThen it ships.
Explore the whole process

Selected work

Product engineering / Applied AI

A few things I’ve built.

AI agents · Product engineering

Cori · Interview coordination

I extended Cori for its launch: an AI agent that coordinates hiring, reports progress as it works, and waits for a recruiter’s approval before it touches a calendar.

Meet Cori

AI evaluation · Data pipelines

AI candidate evaluator

I built and scaled the AI candidate evaluator, bringing together resume parsing, ATS data, and an in-house OCR pipeline. Personal identifiers are stripped before the prompt, inside an independently bias-audited screener.

My work at GoodTime

Founder · Full-stack engineering

Chimpipi · Local business systems

I sit down with local business owners, find what is limiting them, and build the workflow. Websites, voice agents, and office automation, with training for the people who run it.

Explore Chimpipi
More about me

Nine years of shipping software. The last two have been AI features at GoodTime.io, working with the founder on the ambiguous projects: research the problem, find the right people, work out an approach, and see it through launch. That is how the product got its first generative AI, a resume evaluator inside an independently bias-audited screener, and Cori, the agent that schedules interviews and waits for a recruiter to say yes. I am careful about what AI does on someone's behalf. A person approves before anything is sent, published, or released. I am a huge fan of Grok Bot, and the film below is why. On the side I run Chimpipi: I sit down with local business owners, find what is limiting them, build the workflow, and train the people who run it.

How I run Grok Bot at work

I am a huge fan of Grok Bot. I pick the tickets, it researches each bug, and Cursor cloud agents write the fixes, one per bug, all at once. I test every one. Same hours, about ten times the work. A clean review is not a merge.

Film — 1:46

What I do

Work, year by year

How I ship a bug fix

I pick the tickets. Grok Bot researches them and Cursor cloud agents fix them in parallel, several at once. That is the point. Same hours, about ten times the work. I do the testing. A clean review is not a merge. I designed the loop, then taught it to the team.

  1. Research

    Grok Bot checks what I'm assigned, then reads the ticket, Slack, Notion, Drive, Datadog, the Loom, the screenshots, and the code. Each bug gets a brief. It does not reply in Slack.

  2. Build

    Each brief goes to its own Cursor cloud agent. Four bugs get fixed side by side, at the same time.

  3. Review

    CodeRabbit and SonarCloud review every PR. Then Claude Code and Codex review it as adversaries, trying to break the fix. The agents answer what gets flagged before I read it.

  4. Test

    The most important step: I test every fix on stage, then prod.

  5. Ship

    A clean review is not a merge. I merge what passes and send back what doesn't. Grok Bot keeps notes on what worked, and the loop runs again.

My toolkit 27 tools I reach for +

Tools I reach for

The stack under it13

Mentors I listen to

On in the car, on a run, and between builds. None of them know it.

Who I follow on AI

The timeline I read for AI news, and the people I look up to. All on X.