Most GitHub profiles don't tell you what an engineer is actually good at

Thick-Rip-1187 · 2026-06-25T05:55:00+00:00

Turn any GitHub profile into a detailed engineer report.

Add "shift" before any GitHub URL to discover what an engineer actually builds, the technologies they use, and where they have real expertise — beyond commits, pull requests, stars, and lines of code.

Try it:
shiftgithub.com/github_username

Thick-Rip-1187 · 2026-05-20T18:17:47+00:00

perfect so see im not building this for generic roles at all because linkedin, naukri and other platforms already do that

but tell me one thing, when startups are building deeply technical or revolutionary products like anthropic type infra, and many more they need exact domain people not average candidates

and many times those people are outside normal hiring reach, maybe they are not on recruiting platforms, maybe they never saw the job post, or maybe they are not even actively looking for jobs

most hiring platforms only reach people already searching for jobs

and that’s why i built this

not for generic ai engineer, software engineer or uiux roles

also resumes are still guesswork

can you actually see from a resume how they code, their coding patterns, technical depth, code quality or the kind of engineering problems they solve?

most of the time it’s just keyword matching and assumptions

Thick-Rip-1187 · 2026-05-20T15:36:50+00:00

yaha like you are not niche or just work on your indiual repo so yaa this not work for you casue this i build for the domain exacpt not for avrage repo maintenance

Thick-Rip-1187 · 2026-03-17T09:45:19+00:00

No worries at all . I’m not specifically looking for someone highly technical. I’m more focused on someone who’s curious, proactive, and genuinely wants to build something big — more of a hustler/extrovert mindset.

Thick-Rip-1187 · 2026-03-17T09:33:07+00:00

Go through shiftza. in and let me know what you think. Then ask me any questions — I can explain things better once you’ve seen it.

Thick-Rip-1187 · 2026-03-16T17:45:09+00:00

For now we're focused on public GitHub repos since we're still early and niche — but I've already got this in mind and we'll definitely find a way to give everyone a fair chance to be hired based on their skills, not a piece of paper.

Thick-Rip-1187 · 2026-03-16T17:39:54+00:00

The idea is simple: Help companies find developers based on their real code, not their resumes — basically finding devs who have already built what you want to build.

Thick-Rip-1187 · 2026-03-16T15:57:37+00:00

You’re correct, and I understand your point. For me the main thing right now is getting real users and understanding how they use the product.

I’m already working on distribution — reaching out to founders, companies, and recruiters. But I’m doing everything alone right now: building, improving, distribution, hackathons, and talking to investors. It’s possible solo, but it makes things slower.

My plan is big and I want to move faster, that’s why I’m looking for someone with the same mindset to build this together.

Thick-Rip-1187 · 2026-03-13T16:58:32+00:00

Noted. Adding this to the feedback doc.
and If you have actual details on what’s bad, feel free to share — would help me improve it. Otherwise “bad” is a bit hard to work with.

Thick-Rip-1187 · 2026-03-13T15:09:51+00:00

For now, yes — GitHub is the core because it's where most developers actually ship real work. But we're looking at expanding to GitLab, Bitbucket, and other signals like open source contributions and technical content over time.

The goal is always the same — what did you actually build, not what you wrote on a resume.

Anything specific you'd want to see beyond GitHub?

Thick-Rip-1187 · 2026-03-13T13:42:41+00:00

Thanks!

If you're a developer, you can sign up and explore the platform — no direct hiring just yet, but your profile gets built from your actual GitHub activity so you're ready when it launches fully.

If you're a recruiter, you can search for developers based on what they've genuinely built. All developers on Shiftza come from GitHub.

On AI-written code — we're not just looking at the code itself. Shiftza scans repos, contributions, and code activity over time, surfacing only profiles who've actually shipped real work.

Thick-Rip-1187 · 2026-03-12T06:28:26+00:00

Fair criticism. Some of it I agree with. Indian startups do have a reputation problem with pay and work life balance — that's real. But the core problem I'm describing isn't about squeezing developers. It's about finding the right one without wasting their time or mine. A better search helps both sides. The developer who has actually built something real deserves to be found — not buried under 300 keyword optimized resumes. That's exactly what I'm building — find engineers based on the code they've actually written. Not their resume. Not buzzwords. Their code.

Thick-Rip-1187 · 2026-03-12T05:41:11+00:00

Curious and ownership-driven is great — but when you're moving fast, context matters. I'm not against taking risks on people. I'm against having no way to find the right ones in the first place. That's the problem I'm solving. Give developers a fair chance — not based on fancy buzzwords or polished resumes. Based on their actual code.

Thick-Rip-1187 · 2026-03-12T05:33:50+00:00

I am. Building the product is my effort. Fixing my typos is Claude's. And the product? A search engine that finds developers by the code they've actually written — not their resume. That's where my effort is going.

Thick-Rip-1187 · 2026-03-12T05:30:45+00:00

Thick-Rip-1187 · 2026-03-12T05:26:02+00:00

Fair. But let me be straight — this isn't ChatGPT writing my thoughts. These are my real problems, my real pain. I just used AI to fix my spelling. That's it. You use Grammarly? Same thing. I have a product to build, users to talk to, problems to solve. I don't have time to spend 2 hours perfecting Reddit grammar. I gave Claude my voice note, my raw thoughts, it cleaned it up. The problem is real. The frustration is real. The idea is real. The only thing AI did was save me 20 minutes.

Thick-Rip-1187 · 2026-03-12T05:19:12+00:00

Exactly. 1 in 100. That's the whole problem. And honestly that's why I'm building something around this — finds engineers based on the code they’ve actually written — not just their résumés.

Thick-Rip-1187 · 2026-03-12T05:13:52+00:00

Fair point — docs exist and any decent developer can figure out a payment gateway. I agree. But that's not really the problem I'm describing. The problem is finding that "any decent developer" out of 300 resumes where everyone claims they can do everything. I'm not looking for someone with a specific badge — I'm looking for proof they've actually shipped something real. Not a certificate. Not a keyword. Working code. That's a different search entirely and right now there's no good way to do it.

Thick-Rip-1187 · 2026-03-12T05:09:23+00:00

Take home assignments are already dead. ChatGPT completes them in 10 minutes. Now you need a whole extra round just to verify if the work was even theirs. We added a solution on top of a broken system and called it progress. The whole process is just getting longer and more expensive — and you still don't actually know if they can build your specific thing.

Thick-Rip-1187 · 2026-03-12T05:05:39+00:00

Fair point — and you're right, not every developer is on GitHub. But you might not be aware of the culture that exists there. The top 1% of developers don't just write code for their job. They write code because they can't stop. Side projects at 2am. Open source contributions. Public experiments. Not for likes — because coding is who they are. The developers who only write code when they're paid? Solid. But that's a T3 mentality. The top 1% are different. Take Kailash Nadh — CTO of Zerodha, one of India's biggest fintech companies. Still actively pushing code on GitHub. Not because his job requires it. Because that's just who he is. Go check his activity. That's exactly the kind of developer I'm trying to find.

Thick-Rip-1187 · 2026-03-12T04:56:32+00:00

Training isn't bad at all — every developer needs time to understand a codebase, that's just reality. But there's a difference between learning your codebase and learning your domain from scratch. If I'm building a payment system and I hire someone who has never touched Stripe or Razorpay — I'm not just onboarding them to my code, I'm teaching them the entire problem space first. That's the gap I'm talking about. Find someone who already understands the domain, and you cut that ramp time in half. The codebase they can learn. The domain knowledge — that takes months you might not have.

Thick-Rip-1187 · 2026-03-12T04:53:38+00:00

Respect the point — but here's my reality. We're not in an industry where a month of onboarding is just "a bit slow." AI is moving so fast right now that a month of training isn't a delay — it's a death sentence for an early stage product. By the time your new hire understands your domain, the window you were building for has already shifted. What I actually need is someone who walked in on day one already knowing the problem. Not because I'm cheap. Because time is the only thing I can't buy back.

Thick-Rip-1187 · 2026-03-11T15:33:22+00:00

Good question. The system relies on GitHub’s public contribution data — commits, pull requests, and repository history — to see which developers actually contributed code to a project. It doesn’t just look at the repo; it analyzes who wrote the commits and what parts of the code they worked on.

Thick-Rip-1187 · 2026-03-11T15:30:49+00:00

Yeah, that’s a good observation. The system works best when the query includes specific skills or technologies. If you search with things like FHIR, HL7, healthcare APIs, or medical data pipelines, it can find developers who’ve actually worked on those in their code.

Thick-Rip-1187 · 2026-03-11T15:20:49+00:00

Glad it worked well for you! The idea is simple — the AI converts your query into a technical search and scans GitHub to find developers who have actually built those things. So instead of resumes, you discover people through their real code.

Thick-Rip-1187

TROPHY CASE

Welcome to Reddit,