{"slug": "what-recruiters-can-t-see-on-my-github", "title": "What Recruiters Can't See On My GitHub", "summary": "Developer Ash B. has over 100 GitHub repositories spanning React, Python, AI, automation, and more, which he says are all driven by a single obsession: eliminating repetitive work. He built tools like PostPunk, a social media scheduler, and job application helpers to automate tedious tasks. Ash hopes recruiters see a systems thinker rather than a collection of random technologies.", "body_md": "If you spend about 30 seconds looking at my GitHub profile, you might think I'm all over the place.\n\nReact.\n\nPython.\n\nHealthcare.\n\nAI.\n\nScrapers.\n\nAutomation.\n\nMarketing tools.\n\nJob bots.\n\nHonestly, that's something I've worried about.\n\nI have over 100 repositories. Recruiters can see most of them, but not all of them. Some are private because they're client work. Some are private because they're unfinished. Some are private because they contain ideas I've spent years developing and I'm not quite ready to throw the blueprints onto the internet.\n\nFrom the outside, it can look random.\n\nBut recently I realized something.\n\nAll of those projects are solving the same problem.\n\nI hate repetitive work.\n\nMy GitHub is here: [https://github.com/ashb4](https://github.com/ashb4)\n\nI've applied to thousands of jobs over the years.\n\nThousands.\n\nAnd one thing has always driven me absolutely insane.\n\nYou upload your resume.\n\nThen the company immediately asks you to type your entire resume into fifteen different boxes.\n\nYour work history.\n\nYour education.\n\nYour skills.\n\nEverything.\n\nThe computer already has the information.\n\nThe resume is right there.\n\nYet somehow I'm sitting on page seven of an application retyping information that already exists.\n\nIt feels inefficient.\n\nIt feels stupid.\n\nAnd most of all, it feels like a waste of time.\n\nEventually I got annoyed enough to start building tools to help.\n\nAt first I thought I was building unrelated projects.\n\nA job application helper.\n\nA content scheduler.\n\nA healthcare platform.\n\nAn AI framework.\n\nA browser automation system.\n\nBut when I stepped back, I noticed the same motivation behind almost all of them.\n\nEvery project started with some version of:\n\n\"There has to be a better way to do this.\"\n\nTake PostPunk.\n\nMost people see a social media scheduler.\n\nI see hours of repetitive posting that I never want to do again.\n\nI like creating content.\n\nI do not like manually posting the same content everywhere.\n\nSo I built a system where I can create when I'm feeling creative, queue everything up, and let the system handle the repetitive parts later.\n\nCreate once.\n\nReuse many times.\n\nThat's a pattern you'll see all over my GitHub.\n\nOne recruiter might see:\n\nand think:\n\n\"These don't seem related.\"\n\nI'd argue they're incredibly related.\n\nThey're all attempts to reduce repetitive human effort.\n\nDifferent domains.\n\nSame obsession.\n\nSome developers love graphics.\n\nSome love databases.\n\nSome love distributed systems.\n\nI seem to be drawn toward removing friction.\n\nIf something feels repetitive enough, eventually I start asking myself whether a computer should be doing it instead.\n\nPeople sometimes assume that because I use AI, the projects are somehow doing all the work for me.\n\nThe reality is less exciting.\n\nAI helps.\n\nBut AI is not magic.\n\nI've found that the hardest part isn't generating code.\n\nIt's understanding workflows.\n\nUnderstanding edge cases.\n\nUnderstanding what people are actually trying to accomplish.\n\nThe code is often the easy part.\n\nThe thinking is the hard part.\n\nThat's true whether you're building a healthcare platform, a job application tool, or an automation system.\n\nI don't expect recruiters to inspect all 100+ repositories.\n\nNobody has time for that.\n\nBut if they do look at my GitHub, I hope they don't see a collection of random technologies.\n\nI hope they see a systems thinker.\n\nSomeone who gets annoyed by repetitive work.\n\nSomeone who enjoys finding patterns.\n\nSomeone who likes building tools that save people time.\n\nBecause when I look at my repositories, that's what I see.\n\nNot 100 separate projects.\n\nJust one idea repeated over and over:\n\nIf a task is repetitive enough, there's probably a better way to do it.\n\nAnd sooner or later, I'm probably going to try building it.", "url": "https://wpnews.pro/news/what-recruiters-can-t-see-on-my-github", "canonical_source": "https://dev.to/ashb4/what-recruiters-cant-see-on-my-github-1f41", "published_at": "2026-06-16 18:34:02+00:00", "updated_at": "2026-06-16 18:47:13.401384+00:00", "lang": "en", "topics": ["developer-tools", "artificial-intelligence"], "entities": ["Ash B.", "GitHub", "PostPunk"], "alternates": {"html": "https://wpnews.pro/news/what-recruiters-can-t-see-on-my-github", "markdown": "https://wpnews.pro/news/what-recruiters-can-t-see-on-my-github.md", "text": "https://wpnews.pro/news/what-recruiters-can-t-see-on-my-github.txt", "jsonld": "https://wpnews.pro/news/what-recruiters-can-t-see-on-my-github.jsonld"}}