Hiring for Attitude: Why I Ignore Perfect Resumes
In this tactical leadership post, the author pulls back the curtain on the hiring process at Bitbase India. It challenges the traditional tech hiring model that over-indexes on whiteboard tests and keyword matching. By prioritizing "Attitude" over "Skill," the author argues that a company's culture is defined by who you don't hire. The post details specific mechanisms, like ignoring resume gaps and utilizing video introductions, to find candidates who possess the empathy and communication skills necessary for a scalable, healthy engineering department.
I review hundreds of resumes. Many look flawless on paper, packed with the latest frameworks and perfectly formatted experience. But over the years, I've learned a hard truth: tech stacks change, but character doesn't. That is why my core philosophy is hiring for attitude and training for skill. A "perfect" resume tells me what you did yesterday, but your attitude tells me what we can build together tomorrow.
As we scale operations here at Bitbase India building out our new Mobile and .NET departments, I find myself staring at hundreds of resumes. Many of them are perfect on paper. They list every framework, every certification, and have the right keywords to beat the Applicant Tracking System (ATS).
But paper doesn't write code. People do.
In my transition from Front-End Developer to Country Manager, my hiring philosophy has shifted drastically. I no longer look for the "Smartest Developer in the Room." In fact, that person is often a liability. I am looking for the Best Teammate in the Room.
The "Soft" Skills are the Hard Requirements
We often label communication, empathy, and patience as "soft skills." This is a mistake. In a distributed, remote-friendly environment, communication is a technical requirement. If you write the most efficient algorithm in the world but cannot explain why it works to a junior developer, or you get defensive when QA finds a bug, your code’s value drops to zero. You become a bottleneck, not an asset.
Why We Do Asynchronous Video Intros This is why I introduced a seemingly controversial step in our hiring process: the Asynchronous Video Introduction. I don’t ask for this to see how polished you look. I ask for it to hear how you think.
- Can you articulate your story clearly?
- Do you sound excited about building things?
- Are you human?
A resume tells me what you did. A 2-minute video tells me who you are. I have hired candidates who stumbled over technical questions but showed immense curiosity in their video. I have rejected candidates with perfect technical scores who showed zero interest in the "team" aspect of the work.
Red Flags I Happily Ignore
- Resume Gaps: Life happens. Maybe you traveled, maybe you took care of family, maybe you burned out. I don’t care about the gap; I care about who returned from it.
- Missing "Framework X": If you know JavaScript deeply, you can learn React or Vue in a week. If you know C# fundamentals, the specific .NET library doesn't matter. Syntax is cheap; logic is expensive. We can train for skill. We cannot train for attitude.
The Real Red Flag The only true red flag for me is Arrogance. The belief that you have nothing left to learn. We are building a culture at Bitbase where we lift each other up. I would rather hire a "Good" developer who elevates the whole team than a "Great" developer who brings everyone else down.
- Communication is Code: In modern teams, the ability to explain your work is just as critical as the work itself. "Soft skills" are actually "Core Skills" for collaboration.
- The Video Filter: Explaining the rationale behind Asynchronous Video Intros. It’s not a beauty contest; it’s a communication test. It allows the hiring manager to sense passion and clarity that text on a PDF can never convey.
- Skill is Transient, Attitude is Permanent: Frameworks change every six months. A developer’s willingness to learn and adapt is far more valuable than their current knowledge of a specific tool. You can teach syntax; you can't teach curiosity.
- The "Genius" Liability: A warning against hiring the "Rockstar" developer who destroys team morale. One arrogant high-performer can cause three other good employees to quit.
