Rahul Reddy

We're rethinking technical hiring at Talenser and would love your perspective.

If you could see only one thing before deciding whether to interview a candidate, what would it be?

• Resume

• Portfolio

• GitHub profile

• Practical skill assessment

• AI interview summary

• Work samples

• Something else?

We'd love to hear how you hire today and what you'd change.

Something I keep thinking about:

We still hire mostly off r sum s a one-page document someone wrote about themselves. But a resume can't really show if a person can do the actual work, solve real problems, or handle pressure. Yet it's usually the first and biggest filter.

Hey everyone,

I'm Rahul, founder of @Talenser (talenser.com), based in India.

Before this, I kept running into the same problem: hiring developers is painful. Companies drown in r sum s, spend hours filtering keywords and running interview rounds, and still make wrong hires while genuinely skilled developers get overlooked because a r sum doesn't show what they can actually do.