Solynth Labs · product
Trekky
Keep the whole job search together.
About the project
I build and operate Trekky to keep job discovery, application preparation, tracking, and follow-ups together around each role.
Keep the work around the role
A job search spreads across saved links, spreadsheets, inbox threads, calendar reminders, and versions of a résumé. I built Trekky around the role being pursued. Its stage, documents, contacts, interviews, and next action belong to the same workflow, from finding the opening through preparation and follow-up.
Keep tracking responsive and records durable
Protected Next.js pages load their starting data on the server, with MongoDB holding the records and SWR optimistic updates keeping day-to-day tracking responsive. I record a saved role and a submitted application as separate lifecycle events. That distinction matters: saving an interesting job should not count as applying for it in the outcome analytics.
Search the dataset before the live sources
I read from a cached job dataset before falling back to live sources. This reduces repeated upstream work, but a cached listing can lag behind its source. Discovery covers sources across New Zealand, Australia, the United States, and Singapore. Duplicate handling and source history keep imported listings reviewable.
Preparation still needs a person's decision
AI apply kits help prepare material for a specific role, but the person applying reviews the output and chooses the final submission. I keep that decision explicit. The web app is the core, with PWA, browser extension, Google calendar sync, and authenticated MCP integration paths. Their setup and availability vary; an integration in the codebase is not a promise that every account has it enabled.
Next project
