In software engineering, code reviews are an essential part of the development process. They help teams identify bugs, improve security, maintain coding standards, and share technical knowledge. Constructive criticism is not only expected, it is necessary. But what happens when technical feedback becomes personal?
A code review that repeatedly belittles an employee, excludes them from technical discussions, or includes inappropriate or gender-based comments may be more than a difficult workplace interaction. When these behaviors form part of a broader pattern, they may raise concerns about workplace harassment, discrimination, or retaliation. For developers experiencing gender bias in software engineering, it can sometimes be difficult to determine where legitimate technical criticism ends and inappropriate workplace conduct begins. Employers, meanwhile, have an important responsibility to ensure that feedback systems do not become vehicles for discrimination, harassment, or retaliation.
When Does Technical Feedback Cross the Line?
Not every negative code review is unlawful. Software development requires employees to receive and sometimes deliver critical feedback. A reviewer may legitimately identify significant technical problems, recommend changes, or reject code that does not meet established standards.
The concern arises when feedback is no longer focused on the work and instead becomes a repeated attack on the employee.
Potential red flags may include:
- Repeatedly questioning an employee’s intelligence or competence rather than addressing the code itself
- Applying noticeably different standards to similarly situated employees
- Publicly humiliating or mocking a developer
- Dismissing contributions without a legitimate technical explanation
- Consistently interrupting or excluding an employee from technical discussions
- Making gender-based or sexual comments during code reviews or engineering meetings
- Using performance feedback to demean an employee rather than provide constructive guidance
For example, telling a developer that a particular function creates a security vulnerability is legitimate technical feedback. Repeatedly telling that same employee that they are “too incompetent to understand” basic engineering concepts is fundamentally different. The legal significance of conduct depends on the circumstances, including its frequency, severity, context, and whether it is connected to a protected characteristic or protected activity.
Signs of Retaliation in Code Reviews
Code reviews and performance evaluations can also become problematic when they are used to retaliate against an employee who has previously raised concerns about workplace misconduct. Retaliation may initially be difficult to recognize because an employer can generally provide legitimate criticism and address genuine performance problems. The issue is whether an adverse change in treatment is connected to an employee’s protected activity, such as reporting discrimination or harassment.
Potential warning signs can include a sudden change in the tone or substance of reviews after an employee makes a complaint. An employee who previously received positive feedback may suddenly receive unusually negative evaluations, heightened scrutiny, or criticism that is inconsistent with their prior performance record.
Other potential indicators include:
- Increased monitoring or scrutiny after a complaint
- Negative performance reviews that are unsupported by prior feedback
- Exclusion from projects or technical decision-making
- Unexplained changes in responsibilities
- New performance expectations that appear unusually difficult to satisfy
- Comments or conduct suggesting that an employee should not have reported a concern
These circumstances do not automatically establish unlawful retaliation. However, a significant change in treatment following a complaint may warrant closer examination.
Retaliation as a Threat to Future Reporting
Another reason retaliation is particularly concerning is that it can discourage employees from reporting misconduct in the first place. Imagine an engineer observes inappropriate comments from a colleague and reports them to management. Shortly afterward, the engineer begins receiving unusually harsh code reviews, is excluded from important projects, and is told that their “attitude” is creating problems for the team. Even if the employer never explicitly says, “Do not report misconduct again,” the employee may reasonably feel that speaking up has damaged their career. This harmful effect can undermine an employer’s workplace policies and reporting systems. Employees who believe that reporting harassment will result in professional consequences may choose to remain silent.
Sexual harassment retaliation can take many forms, and the legal analysis depends on the specific facts and applicable law. An employee who believes they have experienced retaliation should consider documenting what occurred and seeking advice about their rights and available options.
When Can Conduct Contribute to a Hostile Work Environment?
The phrase “hostile work environment” is often used broadly to describe an unpleasant workplace. Legally, however, the standard is more specific. A difficult manager, an unpopular coworker, or a single critical code review does not necessarily create a legally actionable hostile work environment. However, the broader pattern may matter.
Repeated demeaning comments, gender-based insults, inappropriate sexual remarks, exclusion from workplace activities, and other discriminatory conduct may become more significant when viewed together. Whether the conduct meets the applicable legal standard depends on the circumstances and the law governing the particular workplace. For developers, this can be especially complicated because technical criticism is an ordinary part of the job. A workplace may attempt to characterize problematic behavior as simply “tough engineering culture” or “high standards.” But professional standards should apply consistently. A rigorous engineering environment does not require employees to tolerate personal attacks, discriminatory treatment, sexual comments, or retaliation for raising concerns.
Why Documentation Matters
Documentation can be important for both employees and employers. Employees who believe they are experiencing harassment or retaliation may want to preserve relevant code-review comments, emails, workplace messages, performance evaluations, and records of complaints. Keeping contemporaneous notes about significant incidents may also help establish a timeline. Employees should preserve records lawfully and should not access confidential information they are not authorized to access.
How an Employment Attorney Can Help Hold Companies Accountable
When workplace conduct raises concerns about discrimination, harassment, or retaliation, an employment attorney can help an employee understand how the law may apply to their circumstances. An attorney can help review relevant communications and performance records, identify potential legal issues, explain available options, and advise the employee about applicable deadlines and procedures. For employers, employment counsel can play a preventative role as well. Attorneys can help companies develop and update workplace policies, train managers, evaluate reporting procedures, conduct or advise on workplace investigations, and identify potential areas of legal risk. The goal is not to eliminate legitimate workplace feedback. It is to help ensure feedback and performance management are conducted lawfully, consistently, and professionally while remaining constructive and beneficial to the workplace.
What Should Developers Do If They Suspect Harassment or Retaliation?
Employees who believe they may be experiencing harassment, discrimination, or retaliation should consider taking several practical steps:
- Document concerning incidents. Keep track of significant comments, reviews, meetings, and changes in workplace treatment.
- Preserve relevant communications. Retain emails, messages, code-review comments, and performance evaluations that may be relevant.
- Review workplace policies. Understand the company’s procedures for reporting harassment, discrimination, and retaliation.
- Consider reporting concerns. Depending on the circumstances, an employee may choose to raise the issue through an appropriate reporting channel.
- Pay attention to changes after reporting. Document significant changes in reviews, assignments, responsibilities, or treatment.
- Consider speaking with an employment attorney. Legal rights and deadlines can depend heavily on the facts and applicable state and federal law.
Technical Feedback Should Not Become a Tool for Harassment
Strong engineering teams depend on honest feedback. Developers need to be able to challenge one another’s ideas, identify problems, and insist on high standards. But professionalism and technical rigor are not mutually exclusive. When code reviews become a repeated source of personal humiliation, gender-based criticism, inappropriate comments, exclusion, or retaliation, the issue may extend beyond ordinary workplace disagreement. For employees, recognizing patterns can be an important first step toward understanding their options. For employers, creating clear standards, training reviewers, providing meaningful reporting channels, and responding appropriately to complaints can help prevent problems before they escalate.
At Makarem & Associates, our employment attorneys represent employees and advise employers on workplace matters involving harassment, discrimination, retaliation, and other employment-law concerns.
If you believe that code reviews or other workplace practices have been used to discriminate against you or retaliate against you for raising concerns, or if your company needs guidance on preventing and responding to workplace misconduct, contact Makarem & Associates to discuss your situation and understand your legal options.
Call: 213-269-4013