Open source / Built in public

Too many tabs. Not enough control.

Job hunting already asks a lot of people. The software shouldn't make it harder. I started building tools to make every decision clearer, every workflow more visible, and every next step yours.

A story in two builds

00The starting point

Every job search starts with possibility. Then comes the admin.

A role saved in one tab. An older resume in another folder. A promising AI-generated answer you can't quite verify. I kept coming back to the same question: why does a job search feel harder to manage than the work we're applying to do?

01 /

Scattered context

Postings, drafts, notes, and follow-ups living in separate places.

02 /

Uncertain answers

AI-assisted writing without a clear link back to verified experience.

03 /

Invisible actions

Automation that's difficult to inspect before it changes something.

The answer wasn't a faster auto-apply button. It was a more transparent way to work.

That's where the first project began.

01The foundation / ReboundOps

First, make the process trustworthy.

A job search workspace that runs on your computer, with AI as a choice—not a requirement.

I wanted one place where I could capture a role, understand why it was a fit, prepare honest documents, and track what happened next. Without handing over the whole process to a black box.

That became ReboundOps: an open-source, local-first application designed around evidence, privacy, and human decisions.

  • Grounded documents. Resume and cover-letter drafts use user-verified facts.
  • Explainable assessments. Role fit and eligibility are considered separately.
  • Control by default. No account required; no automatic job submissions or emails.
  • Angular
  • TypeScript
  • Fastify
  • SQLite
  • Optional Ollama / cloud AI

Published as an early v0.2.0 pre-release. Installation, limitations, and tested platforms are documented in the repository.

Original concept illustration — not an application screenshot

Then another question emerged

What if the tools didn't just do the work—what if you could see the work happening?

ReboundOps focuses on the integrity of the workflow. A separate experiment asked how that workflow could feel in a visual desktop environment, with each agent action and approval in plain sight.

AI Job Search Assistant's original Scout concept illustration with a dark desktop workspace and job search workflow panels
Original project artwork — conceptual, not a screenshot
  1. Discover
  2. Rank
  3. Prepare
  4. Review
  5. Track
02The experience / AI Job Search Assistant

Then, make the automation visible.

A macOS command center where workflows, agents, documents, and approvals share one screen.

AI Job Search Assistant takes a different route. It's a visual desktop companion for the open-source ai-job-search workflow, turning its command-driven journey into a guided interface.

Instead of treating the agent as a mystery, the app emphasizes visible progress, inspectable documents, and a pause for human approval before sensitive actions.

  • Visual pipeline. Discover, rank, prepare, review, and track in one desktop experience.
  • Agent visibility. See workflow progress and tool activity rather than guessing what's running.
  • Explicit approval. Applications are not auto-submitted, and emails aren't silently sent.
  • React 19
  • TypeScript
  • Tauri 2
  • Rust
  • SQLite
  • Claude Code / Codex

Apple Silicon source build; no verified packaged installer yet. This app is a separate interface for the upstream project's workflow, not a claim of ownership of the upstream framework. Provider support and prerequisites are documented in the README.

03The thread connecting both projects

Two projects. One philosophy.

Different technologies and different interfaces. The same design instincts keep showing up.

Own your workspace

Keep your job-search records in a workspace you control. Any external provider interaction should be deliberate.

See the reasoning

A recommendation or draft is more useful when its inputs, evidence, and limitations are visible.

Keep the final say

Automation can prepare and assist. A person still decides what to save, send, and submit.

Built openly · Always evolving

The best part of open source? You can look under the hood.

Don't take a polished page as proof. Explore the repositories, inspect the implementations, check what's shipped, and see what's still being built.