Stop saying "I know Python." Start showing it. Trekme turns your weekly developer work into dashboards and reports that act like an interactive resume and update themselves every week. Think New Relic or Datadog for your career: a living, portable record of what you built with, how deeply you used it, and how your skills evolve over time, giving you documented evidence beyond one-shot, AI-written resumes.
It's helpful for such a head in the clouds as me. It's nice that I don't have to track or recall skills used in various projects. Helps with sharing skills and even self reflection about my own knowledge. Worth giving a shot.
Ratings
Ease of use
Reliability
Value for money
Customization
Report
8 views
Maker
📌
Hey Product Hunt, I’m Andrzej, maker of Trekme.
I built this because hiring still works backwards. A role opens, then the candidate rewrites a CV to fit the posting. On top of that, a resume has to compress years of work into a small space, so relevant but less obvious experience often gets dropped entirely.
That makes it hard to answer simple questions with confidence: When did this person actually start using this technology? How consistently have they used it? Was it shallow exposure or real working depth?
My goal with Trekme is to help developers build that record before they need it, not reconstruct it after the fact. So when a job asks for Python, Django, AWS, or anything else, you can show that you were already working with it before the posting even existed.
I’d love feedback from both job seekers and hiring managers: would a time-based record of real experience be more useful than a polished one-page CV? What would make you trust it?
Report
That's a great idea, but my problem is keeping up with regular data entry.
The Treckme.pro has reminders, but some extra motivation would be helpful (like in mobile games). Every time you enter data regularly, a plant grows, you level up a pet, or something like that. Gamification would definitely help motivate people to keep entering data.
Report
Maker
@artur_ross We have some basic gamification elements implemented, like: showing your current and potential streak in filled up consecutive weeks, and your place in global high-score table. each weekly reminder email also shows you insights from recent weeks... but i I wrote, those are rather basic as we focus on usability for our users first... currently we focus on making reports and dashboards better
Report
I’d trust a skill timeline more than a polished CV, but only if it stays close to real work.
A resume line like “experienced with AWS” is too easy to stretch. Showing when someone used it, how often, and in what kind of project gives a much better signal.
The privacy controls would matter a lot though. Developers should be able to prove depth without exposing company details, private repos, or client work.
Is this tracking gotten locally from my git history, or do I have to connect accounts and upload data?
Report
@thamibenjelloun tracking is done locally (your own LLM is reviewing codebase changes ) and only technology names are uploaded via MCP, or if you like: by old-school web based form that you can update every week. so there is no way to leak the codebase
Report
better than recruitment tasks created by LLM and solved by another LLM, or questions prepared and answered the same way
That's a great idea, but my problem is keeping up with regular data entry.
The Treckme.pro has reminders, but some extra motivation would be helpful (like in mobile games). Every time you enter data regularly, a plant grows, you level up a pet, or something like that. Gamification would definitely help motivate people to keep entering data.
@artur_ross We have some basic gamification elements implemented, like: showing your current and potential streak in filled up consecutive weeks, and your place in global high-score table. each weekly reminder email also shows you insights from recent weeks... but i I wrote, those are rather basic as we focus on usability for our users first... currently we focus on making reports and dashboards better
I’d trust a skill timeline more than a polished CV, but only if it stays close to real work.
A resume line like “experienced with AWS” is too easy to stretch. Showing when someone used it, how often, and in what kind of project gives a much better signal.
The privacy controls would matter a lot though. Developers should be able to prove depth without exposing company details, private repos, or client work.
Mailwarm
Is this tracking gotten locally from my git history, or do I have to connect accounts and upload data?
@thamibenjelloun tracking is done locally (your own LLM is reviewing codebase changes ) and only technology names are uploaded via MCP, or if you like: by old-school web based form that you can update every week. so there is no way to leak the codebase
better than recruitment tasks created by LLM and solved by another LLM, or questions prepared and answered the same way