Jobmark
A career journal.
The idea came from my first day at Rutgers OSS. It became something I use daily to keep track of my work, so I don't have to rely on memory.
How it started
On my first day at Rutgers OSS, my boss gave me a warning: someday a bad manager or coworker might take credit for work I had done. If I kept a daily record, I would be able to show what I had actually done when review, promotion, or interview time arrived.
I took it seriously. Starting January 7, 2026, I wrote down what I did each day in a plain text file, why it mattered, and what evidence I had. Before Jobmark existed, the habit already did.
Turning a habit into a product
Jobmark grew out of that file once I realized this wasn't a good enough solution and I could turn it into something more. I migrated the history into Jobmark and kept using it myself. Accomplishments, activities, metrics, projects, goals, contacts, and interactions, so writing a progress report was easier and I solved the problem of trying to reconstructing it from memory.
Where the assistant fits
Jobmark exposes scoped operations through Streamable HTTP MCP with OAuth 2.1 and PKCE, which lets an assistant work with the entries I already keep. Mutating calls use idempotency keys, and connection unlock is short-lived and bound to the user. Allowing an assistant to add entries, summarize them, or generate reports as a natural extension of the journaling I already do.
Where it stands
I still use Jobmark every day, and its proved useful to me. Production and preview now run in Kubernetes on separate Neon database branches after learning the hard was how important that is... Feel free to use it for yourself I believe its important to have a record of your work, and Jobmark is a tool that can help you do that.
STACK
NEXT.JS 16 · AUTH.JS · PRISMA · POSTGRESQL · MCP · KUBERNETES