Did Goldman Sachs Overstep in Criminally Charging Its Ex-Programmer?
A month after ace programmer Sergey Aleynikov left Goldman Sachs, he was arrested. Exactly what he'd done neither the F.B.I., which interrogated him, nor the jury, which convicted him a year later, seemed to understand.
Context & Ripple Effects
The case began in July 2009, when the F.B.I.'s arrest of Sergey Aleynikov a month after he left Goldman Sachs turned a routine engineering departure into a federal prosecution. By March 2011 a jury had convicted him and a judge handed down an eight-year sentence for code theft, even as the Vanity Fair account notes neither the interrogating agents nor the jurors could clearly articulate what he had actually done.
What changed with this feature is the framing rather than the facts: a mainstream magazine is openly asking whether Goldman Sachs overstepped by pressing for criminal charges against its own ex-programmer, and the story traveled widely the same week through Forbes, DealBook, Forbes' Tell blog, and market-commentary accounts like Nanex — evidence that skepticism about the prosecution had moved from legal blogs into business-media consensus.
First-order effects
- Aleynikov remains inside an eight-year sentence handed down in March 2011, and the renewed scrutiny lands on Manhattan federal prosecutors and Goldman Sachs, whose referral put the criminal machinery in motion.
- Goldman faces a fresh round of reputational exposure at precisely the moment its trading technology practices are being narrated publicly, not just litigated.
Second-order effects
- Other banks watching the backlash have a live test case for how aggressively they refer departing engineers to law enforcement over source code, since the visible cost of the Aleynikov prosecution now includes unfavorable national press.
- Defense counsel and civil-liberties voices gain a high-profile template for arguing that trade-secret disputes between employers and coders belong in civil court, not criminal dockets.
Third-order effects
- If the pattern holds, the boundary of what counts as 'theft' when a quant or programmer moves between trading firms becomes a contested legal question rather than an employer's unilateral call, shaping how Wall Street writes employment and IP agreements for technical staff.
- The case feeds a longer-running tension between the F.B.I.'s willingness to treat proprietary code as stolen property and courts' difficulty defining that property — a fault line that will resurface every time a financial firm's algorithms walk out the door in an engineer's head.
The trend: Wall Street's use of criminal prosecution to police departing technologists is meeting growing media and legal resistance, forcing a re-examination of how trade secrets in source code should actually be enforced.