PJS Pengyi JS
North Star OS
HK snapshot · 31 Jul 2026
Original editorial illustration of a quantitative research workspace overlooking Hong Kong

Independent benchmark / North Star

Prepare to the standard.
Prove it with evidence.

PJS turns public Jane Street roles and materials into a demanding preparation standard for reasoning, coding, quantitative research, production ownership, communication, and intellectual honesty.

01 Public signals 02 Capability standard 03 Evidence loop

01 / Thesis

Jane Street is a North Star, not a borrowed identity.

The objective is not to imitate a logo or claim equivalence. It is to translate visible expectations into capability contracts, pressure-test them, and produce evidence that survives technical questioning.

02 / North Star standard

One specification across six capabilities

A PJS preparation standard derived from recurring public signals. Every capability must become observable work, not vocabulary.

01

Reasoning

Structure uncertain problems, state assumptions, quantify trade-offs, and update when evidence changes.

Evidence: timed math, probability, and decision work
02

Coding

Translate thought into clear programs, debug from first principles, and explain complexity and failure modes.

Evidence: independent implementation under review
03

Quant research

Connect data, features, signals, positions, costs, evaluation, and research boundaries without hiding gaps.

Evidence: reproducible research and attribution
04

Production

Design for reliability, observability, recovery, ownership, and the consequences of real operation.

Evidence: tests, monitoring, incidents, and runbooks
05

Communication

Make technical reasoning concise, collaborative, and useful across research, trading, and engineering.

Evidence: live defense, writing, and feedback
06

Intellectual honesty

Separate facts from inference, disclose uncertainty, admit mistakes quickly, and improve the system.

Evidence: calibrated claims and documented revisions

03 / Visible system

One firm-wide problem-solving loop

A PJS inference from repeated language across official role descriptions. It is not an internal reporting chart.

01Market / business problemFind the consequential question.
02Reason + experimentData, models, counterfactuals.
03Build + productionizeTools, systems, connectivity.
04Trade + operateExecution, clients, controls.
05Learn + improveFeedback, teaching, iteration.
TRM

Trading, Research & ML

Signals, experiments, pricing, models, strategies, execution, and risk.

TECH

Technology

Software, ML platforms, Linux, networks, market connectivity, and compute.

SP

Strategy & Product

Cross-functional analysis, process design, priorities, and delivery.

IST

Institutional

Client needs, products, execution, regional coverage, and feedback.

F&O

Finance & Operations

Financing, reporting, tax, controls, constraints, and automation.

04 / Hong Kong role atlas

Read by stage and system layer

Availability changes. Each card links to the official source captured for this snapshot.

05 / What seniority reveals

I

Internship

Mentorship, classes, real projects, simulation, broad exposure.

Signal: learning velocity
N

New graduate

Strong foundations, guided responsibility, precise reasoning, collaboration.

Signal: potential with rigor
E

Experienced

Domain depth, production ownership, platform improvement, cross-team delivery.

Signal: demonstrated leverage

06 / Evidence gates

A capability is real only when it survives the next gate.

PJS does not publish arbitrary readiness scores. Progress is measured through observable artifacts, pressure tests, and revisions.

01

Explain

Recover the idea, assumptions, interfaces, and boundaries without hiding behind terminology.

02

Implement

Produce the core logic independently and make the design choices explicit.

03

Test

Challenge correctness, edge cases, leakage, robustness, and failure behavior.

04

Operate

Show how the work is configured, observed, recovered, and maintained.

05

Defend

Survive follow-up questions, alternatives, trade-offs, and a live change request.

07 / Repeated hiring signals

  1. 01Reason clearly under uncertainty.
  2. 02Learn quickly without pretending to know.
  3. 03Turn thought into working code and systems.
  4. 04Communicate precisely across specialties.
  5. 05Connect local work to firm-wide outcomes.
  6. 06Own production, feedback, and improvement.

08 / Evidence boundary

Official sources first.

PJS uses official Jane Street public pages as primary evidence. Organization maps are labeled as inference. Private strategies, internal reporting lines, exact headcount, compensation, and unpublished systems remain unknown.

Open official Hong Kong roles Open official Hong Kong office page