Retaliation by Git Commit: How Tech Employees Are Punished After Reporting Harassment

Workplace retaliation generally occurs when an employer takes adverse action against an employee because the employee engaged in legally protected activity, such as reporting or opposing conduct the employee reasonably believes constitutes unlawful harassment or discrimination. Identifying potential retaliation can be particularly difficult in technology workplaces because projects, teams, responsibilities, and company priorities may change frequently. An employer may explain a project reassignment, poor review, or change in responsibilities as an ordinary business decision. For this reason, one of the most important considerations may be how the employee was treated before the complaint compared with how they were treated afterward. Timing can also be significant. A single critical code review months after a complaint may have an innocent explanation, while a series of negative actions beginning shortly after the employee reports harassment may raise different concerns. Code reviews are one example of how an ordinary workplace practice can potentially become a tool for retaliation. Reviewing code, requesting revisions, and providing technical feedback are normal parts of many technology jobs. However, concerns may arise when an employee who previously received positive feedback suddenly begins receiving unusually harsh criticism or repeated write-ups after making a harassment complaint. An employee might be required to make excessive revisions that are not demanded of coworkers in similar positions, have work repeatedly rejected despite a history of satisfactory performance, or be held to standards that do not appear to apply to other employees. Excessive supervision or suddenly taking away an employee‘s ability to work independently may also affect productivity. If those obstacles then become the basis for criticizing the employee‘s performance, the overall sequence of events may be relevant to a retaliation claim. Changes to an employee‘s projects and responsibilities may be significant as well. Tech employees often build their careers through high-visibility projects that provide opportunities to develop new skills, work with leadership, and demonstrate their value to the company. Removing an employee from an important project after a complaint can therefore have consequences even if the employee keeps the same title and salary. Other changes may include assigning less meaningful work, giving assignments typically handled by lower-level employees, excluding the employee from meetings or planning discussions, transferring responsibilities to coworkers without a clear explanation, or, conversely, giving the employee an unreasonable amount of work. While legitimate business reasons may explain these decisions, a sudden pattern of exclusion or altered responsibilities after a protected complaint may warrant closer examination.

Performance evaluations and promotion decisions are another area where potential retaliation may be less obvious. An employee who was previously receiving positive feedback or being considered for advancement may suddenly be told that they lack “leadership,” “communication,” “teamwork,” or “culture fit.” These criteria may sometimes be legitimate considerations, but their subjective nature can make it important to examine whether the employer applied them consistently. A sudden negative evaluation following a harassment complaint may be particularly notable when it conflicts with the employee‘s documented performance history. Negative performance ratings can have consequences far beyond the review itself. They may affect promotions, bonuses, raises, equity or stock opportunities, and future assignments. They may also be considered when a company makes termination or layoff decisions. Employees who believe they are experiencing retaliation should therefore consider preserving performance evaluations, written praise, awards, promotion discussions, and other records they are legally permitted to retain. Evidence showing consistently positive performance before a complaint followed by unexplained negative reviews afterward may help provide context for the change. For technology employees, access itself can also be essential to job performance. Engineers and other employees may rely on repositories, databases, internal systems, Slack or Teams channels, and other technical resources to complete their work.

If access is unexpectedly restricted or revoked after an employee reports harassment, the employee may become unable to perform assignments that were previously routine. Exclusion from meetings, communications, or collaborative tools can similarly isolate an employee from coworkers and important information. In some circumstances, an employee may then be criticized for missed deadlines or poor performance caused in part by the very restrictions placed on them. Again, not every access change is retaliatory. Security requirements, project changes, and legitimate business needs may require companies to modify employee permissions. The surrounding circumstances—including timing, the employer’s explanation, and whether similarly situated employees were treated differently—can help distinguish ordinary operational decisions from potential retaliation.

Not every negative workplace experience after a harassment complaint constitutes unlawful retaliation. Employers generally remain entitled to manage employees, provide legitimate performance criticism, restructure teams, and make business decisions. The question is whether a negative action was taken because the employee engaged in legally protected activity. Because motive is not always directly stated, the overall pattern of events can be important. Employees may want to consider how soon negative treatment began after their complaint, whether their treatment changed significantly, and whether coworkers in similar positions were treated differently. An employer’s explanation may also be relevant. For example, a performance concern that appears suddenly after years of positive feedback may raise different questions than an issue that was consistently documented before the employee complained. Several actions that might appear minor individually—such as exclusion from meetings, harsher reviews, lost responsibilities, and delayed advancement—may take on greater significance when considered together and in chronological context. Documentation can be particularly important in these situations. Employees may consider maintaining a timeline identifying when they reported harassment and when subsequent workplace changes occurred. They should preserve records they are legally permitted to keep, such as performance evaluations, written feedback, relevant emails, and communications regarding projects or promotions. When appropriate, making complaints and significant follow-up communications in writing may also create a clearer record of what the employer knew and when. At the same time, employees should not improperly download, forward, or retain confidential, proprietary, or otherwise protected company information. California law provides protections against retaliation for employees who engage in certain protected activities, including reporting or opposing unlawful workplace harassment or discrimination. Potential retaliation is not necessarily limited to termination or a formal demotion. Depending on the circumstances, other actions affecting an employee‘s work or employment opportunities may also be relevant. Because each case depends on its specific facts, a California retaliation attorney can evaluate the employee‘s complaint, the employer’s stated reasons for its decisions, the timing of subsequent events, and available evidence to determine whether the conduct may support a legal claim.

Retaliation after reporting harassment in tech can be difficult to recognize because it may be disguised as ordinary management or technical decisions. A harsh code review, project reassignment, delayed promotion, negative performance rating, or access change may have a legitimate explanation when viewed alone. But when an employee experiences a significant pattern of negative treatment after reporting harassment or discrimination, the circumstances may deserve closer attention. Employees should pay attention to changes in how they are treated, particularly when those changes begin soon after a workplace complaint. Preserving appropriate documentation of performance history, assignments, reviews, complaints, and subsequent workplace actions may help establish what changed and when. California tech employees who believe they have experienced retaliation after reporting harassment or discrimination may benefit from speaking with an employment attorney to understand their rights and determine whether the circumstances may support a retaliation claim.