Bengaluru founder bans male hires from four states
Karthik SG, founder of Bengaluru-based A1 Sports World, posted on X that his company will not hire male candidates from Uttar Pradesh, Rajasthan, Bihar and Madhya Pradesh, after an employee from one of those states was dismissed over alleged abusive behaviour toward female colleagues. He defended the move with 'my company my rules' and said the firm has 32 employees, 14 of them women. The post drew sharply divided reactions and renewed debate on regional bias in hiring. The company is tiny and the policy is almost certainly unenforceable, but the episode is a live case study in how a single founder's reaction to one incident can become a public hiring-policy statement. Key signal: A Bengaluru founder with 32 employees publicly declared his company will not hire any male candidates from Uttar Pradesh, Rajasthan, Bihar and Madhya Pradesh — a blanket ban on four states, triggered by one fired employee. For hiring leaders, this matters because for CHROs and TA leaders, the real issue is not one founder's post — it is the governance vacuum it exposes. Blanket exclusions based on state of origin sit badly against equal-opportunity norms, and in a viral era, any hiring rule can become a public position overnight. GCCs, IT services firms and product companies hiring at scale across India cannot afford founder-level improvisation on protected attributes. The practical takeaway: codify hiring criteria around role, skill and verified conduct; route misconduct through a documented process; and make sure no manager can convert one bad hire into a regional ban. Teksands view: Ignore the outrage cycle and look at the mechanics. A founder converted one misconduct case into a blanket regional exclusion, announced publicly, and defended it as a private right. That is exactly the kind of ad-hoc rule that becomes a legal and brand liability the moment a company scales. For TA leaders, the takeaway is unglamorous: define screening criteria by role and verified conduct, keep disciplinary process separate from sourcing, and make sure no hiring rule is ever born in a social post.
Key fact
A Bengaluru founder with 32 employees publicly declared his company will not hire any male candidates from Uttar Pradesh, Rajasthan, Bihar and Madhya Pradesh — a blanket ban on four states, triggered by one fired employee.
Why it matters
For CHROs and TA leaders, the real issue is not one founder's post — it is the governance vacuum it exposes. Blanket exclusions based on state of origin sit badly against equal-opportunity norms, and in a viral era, any hiring rule can become a public position overnight. GCCs, IT services firms and product companies hiring at scale across India cannot afford founder-level improvisation on protected attributes. The practical takeaway: codify hiring criteria around role, skill and verified conduct; route misconduct through a documented process; and make sure no manager can convert one bad hire into a regional ban.
The Teksands point of view
Ignore the outrage cycle and look at the mechanics. A founder converted one misconduct case into a blanket regional exclusion, announced publicly, and defended it as a private right. That is exactly the kind of ad-hoc rule that becomes a legal and brand liability the moment a company scales. For TA leaders, the takeaway is unglamorous: define screening criteria by role and verified conduct, keep disciplinary process separate from sourcing, and make sure no hiring rule is ever born in a social post.
Got a tech role that's refusing to close?
Send us the JD. We'll tell you whether the problem is talent supply, compensation, location, process - or the JD itself.
