A Bengaluru entrepreneur\u2019s decision to stop hiring male candidates from Uttar Pradesh, Bihar, Rajasthan and Madhya Pradesh has triggered a wider debate about workplace safety, regional bias and how companies should respond when an employee allegedly crosses the line.<\/p>\n\n\n\n
Now, Neftic founder Shivam Namdeo<\/strong> has entered the conversation, arguing that protecting employees is essential \u2014 but that an individual incident should not automatically become a reason to exclude thousands of unrelated candidates based on their place of origin.<\/p>\n\n\n\n Karthik SG, founder of Bengaluru-based A1 Sports World, announced on September 22 that his company would no longer hire male candidates from four states: Uttar Pradesh, Rajasthan, Bihar and Madhya Pradesh. He said the decision followed an internal discussion after an incident involving a former employee.<\/p>\n\n\n\n The entrepreneur later said the employee had allegedly behaved abusively towards female colleagues despite receiving two warnings and had allegedly attempted to force himself on a female employee.<\/p>\n\n\n\n Karthik said the employee was an MBA graduate whose r\u00e9sum\u00e9 and background had appeared clean during recruitment. According to his account, the alleged behaviour emerged around two months after the employee joined the company.<\/p>\n\n\n\n Those allegations have not been independently established in the reports reviewed for this article.<\/p>\n\n\n\n Karthik also said A1 Sports World has 32 employees, including 14 women, and that 20 employees are from outside Karnataka, including 12 from outside South India. He said workplace and child safety were central to his decision.<\/p>\n\n\n\n When criticised online, he defended his position with the statement: \u201cMy company, my rules.\u201d<\/p>\n\n\n\n Responding to the controversy, Neftic founder Shivam Namdeo has challenged the idea that an individual employee\u2019s alleged misconduct should translate into a geographical hiring restriction.<\/p>\n\n\n\n His argument is straightforward: if the problem was one employee, the appropriate management question should be what happened during the recruitment and probation process \u2014 and what systems can prevent a similar incident in the future.<\/p>\n\n\n\n \u201cYour personal experience cannot automatically become company policy,\u201d Namdeo argues.<\/p>\n\n\n\n He points instead to mechanisms such as:<\/p>\n\n\n\n The central distinction, according to Namdeo, is between managing an incident and generalising from it<\/strong>.<\/p>\n\n\n\n \u201cIf one person creates a serious problem, my first question as a founder would be: \u2018What did we miss, and how do we build a better system so this doesn’t happen again?\u2019\u201d<\/p>\n\n\n\n Namdeo\u2019s criticism focuses on the gap between evaluating an individual and evaluating an entire category of people.<\/p>\n\n\n\n A candidate from Indore, Patna, Lucknow or Jaipur does not necessarily share the behaviour, values or workplace conduct of another person who happens to come from the same state.<\/p>\n\n\n\n That makes state of origin a weak substitute for evaluating the qualities employers actually need to assess: professional conduct, qualifications, references, communication, experience and behaviour during the hiring process.<\/p>\n\n\n\n The controversy therefore raises a broader question for Indian startups: Can a company legitimately prioritise workplace safety while still ensuring that hiring decisions are based on individual candidates rather than broad demographic assumptions?<\/strong><\/p>\n\n\n\n The two objectives are not necessarily incompatible.<\/p>\n\n\n\n The Bengaluru dimension adds another layer to the debate.<\/p>\n\n\n\n Official Census of India datasets track migration into Karnataka and Bengaluru by place of previous residence, duration and reason for migration.<\/p>\n\n\n\n Research based on Census 2011 data has estimated that migrants accounted for around 50.6% of Bengaluru\u2019s population, placing the city among India\u2019s major destinations for internal migration. Employment has been identified as one of the principal reasons for migration to the city.<\/p>\n\n\n\n That does not mean Bengaluru\u2019s growth can be attributed to migrants alone. Karnataka\u2019s own population, institutions, entrepreneurs and workforce have been fundamental to the city\u2019s development.<\/p>\n\n\n\n But it does underline an important reality: Bengaluru has developed as a labour and talent magnet for people from across India.<\/p>\n\n\n\n For companies operating in that ecosystem, birthplace can therefore be a particularly blunt hiring filter.<\/p>\n\n\n\n Namdeo has also made clear that his response is not an argument against workplace safety or zero tolerance for harassment.<\/p>\n\n\n\n His position is that companies should act decisively against individuals accused or found responsible for misconduct while simultaneously improving the systems that allowed the problem to emerge.<\/p>\n\n\n\n That distinction matters.<\/p>\n\n\n\n A company has the right to establish workplace standards and take action when those standards are breached. But whether a broad geographical restriction is an effective way to achieve that objective remains a separate question.<\/p>\n\n\n\n The controversy has consequently moved beyond one founder\u2019s hiring policy. It has become a discussion about how Indian startups handle risk, recruitment, workplace safety and regional diversity.<\/p>\n\n\n\n The debate ultimately presents two competing instincts after a serious workplace incident.<\/p>\n\n\n\n One is to reduce risk by excluding a broader category of candidates.<\/p>\n\n\n\n The other is to improve the process so that individuals are evaluated more effectively.<\/p>\n\n\n\n Namdeo\u2019s response argues for the second approach.<\/p>\n\n\n\n His message to founders is blunt: protecting employees is part of leadership, but so is ensuring that one person\u2019s alleged actions do not become the basis for judging thousands of people who have never been given an opportunity.<\/p>\n\n\n\n As he puts it: \u201cMy state isn’t your hiring problem. Your hiring process is.\u201d<\/strong><\/p>\n\n\n\n For Indian startups hiring in increasingly diverse cities such as Bengaluru, the question may not be whether founders should have rules. It is whether those rules actually address the problem they were created to solve.<\/p>\n\n\n\nBengaluru CEO\u2019s hiring decision sparks controversy<\/h2>\n\n\n\n
Shivam Namdeo questions the logic of collective exclusion<\/h2>\n\n\n\n
\n
The problem with using geography as a hiring filter<\/h2>\n\n\n\n
Bengaluru\u2019s identity is deeply connected to migration<\/h2>\n\n\n\n
A founder-to-founder disagreement<\/h2>\n\n\n\n
The larger lesson for founders<\/h2>\n\n\n\n