/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Ex-Goldman Sachs programmer found guilty of stealing computer code in split verdict three years after first conviction was reversed

Ex-Goldman Programmer Found Guilty  —  For the second time in five years, Sergey Aleynikov was convicted on charges of stealing confidential computer trading code …

New York Times

Context & Ripple Effects

Sergey Aleynikov walked out of Goldman Sachs' high-frequency trading group into a Chicago job paying roughly three times his $400,000 salary — the move that triggered charges of stealing the bank's confidential trading code. His first conviction was reversed three years ago, and this retrial has now produced a split verdict convicting him a second time.

The stakes go beyond one programmer: prosecutors treated Goldman's trading software as protectable property worth criminal prosecution rather than a civil dispute over an employee departure.

First-order effects

  • Aleynikov faces sentencing on the new conviction — the prior track record shows the court willing to impose years-long prison terms for trading-code theft.
  • Goldman Sachs gets judicial confirmation that its high-frequency trading code qualifies as stolen confidential property, strengthening its hand against departing engineers.

Second-order effects

  • Banks and trading firms watching the case have reason to harden code-access controls and exit procedures for quantitative developers, since the courtroom route to protecting algorithms now looks viable even after an appellate reversal.
  • Federal prosecutors gain a template for pursuing employee source-code theft criminally — a path already being tested against developers at IBM and other firms accused of moving code to new employers or foreign recipients.

Third-order effects

  • If the pattern holds, departures of senior engineers carrying code become a criminal-law problem rather than a private contract dispute — a shift visible in the later string of convictions and sentences against engineers who moved proprietary work between employers, including Intel engineer Varun Gupta's probation sentence for sharing secrets with Microsoft and the IBM developer's guilty plea over source code intended for China.
  • The line between an engineer's portable skills and the employer's intellectual property gets redrawn by juries case by case — though Aleynikov's own saga, where an appeals court later overturned this second conviction, shows how unsettled that boundary remains.

The trend: Employee code theft is migrating from HR and civil-contract territory into federal criminal prosecution, with juries increasingly treating proprietary source code as stealable property.