BENGALURU — According to a 2025 survey by JobsForHer, 34% of urban Indian professionals say they met their significant other at work. In the IT industry, where the hours are long, the attrition is high, and the social circle outside the office consists primarily of other people from the same office, this number is probably conservative. The Indian IT office is not just a place of work. It is, for approximately one-third of its population at any given time, the most active theatre of romantic activity in their lives. This is because the office has air conditioning, free coffee, and people who understand what you mean when you say "the build is broken" — and nothing is more intimate than shared suffering.

The typical Indian IT romance follows a predictable arc. Phase 1: repeated proximity. They are on the same project. Or the same floor. Or they sit near each other and one of them always arrives exactly when the other's coffee is ready and this happens enough times that it stops being coincidence and starts being scheduling. Phase 2: the "team lunch" escalation. Everyone goes to lunch together but they always end up talking to each other. Their colleagues notice. Their colleagues say nothing. Their colleagues notice more loudly in the team WhatsApp group where they have a separate thread for exactly this observation.

The Indian IT office affair — meaning specifically the case where one or both parties are married to someone else — is a separate and more complex category that HR policies address in seventeen different clauses and that actual humans navigate with the creativity of people who have read the policy and concluded that the canteen at 2 PM is technically not covered by clause 14(b). Companies with "fraternisation policies" find them difficult to enforce. Companies without them find the situations they produce difficult to manage. The Coorg offsite, which occurs annually in most large IT teams, has a documented role in both categories of relationship. The Coorg offsite is officially for team-building. It builds many things.

The breakup — and in an industry with this much proximity and attrition, there are many breakups — creates a specific workplace dynamic that no management textbook covers. The sprint retrospective where both parties are present. The standup where one person announces a blocker and the other person is the blocker. The team lunch which now requires a seating chart that nobody draws but everyone understands. HR's "conflict of interest" policy does not have a section on "was in a relationship with the person who is now reviewing my code." This gap in policy documentation is felt deeply and silently by approximately one floor of every large Indian IT office at any given time.