Reasoning
Structure uncertain problems, state assumptions, quantify trade-offs, and update when evidence changes.
Evidence: timed math, probability, and decision work
01 / Thesis
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
A PJS preparation standard derived from recurring public signals. Every capability must become observable work, not vocabulary.
Structure uncertain problems, state assumptions, quantify trade-offs, and update when evidence changes.
Evidence: timed math, probability, and decision workTranslate thought into clear programs, debug from first principles, and explain complexity and failure modes.
Evidence: independent implementation under reviewConnect data, features, signals, positions, costs, evaluation, and research boundaries without hiding gaps.
Evidence: reproducible research and attributionDesign for reliability, observability, recovery, ownership, and the consequences of real operation.
Evidence: tests, monitoring, incidents, and runbooksMake technical reasoning concise, collaborative, and useful across research, trading, and engineering.
Evidence: live defense, writing, and feedbackSeparate facts from inference, disclose uncertainty, admit mistakes quickly, and improve the system.
Evidence: calibrated claims and documented revisions03 / Visible system
A PJS inference from repeated language across official role descriptions. It is not an internal reporting chart.
Signals, experiments, pricing, models, strategies, execution, and risk.
Software, ML platforms, Linux, networks, market connectivity, and compute.
Cross-functional analysis, process design, priorities, and delivery.
Client needs, products, execution, regional coverage, and feedback.
Financing, reporting, tax, controls, constraints, and automation.
04 / Hong Kong role atlas
Availability changes. Each card links to the official source captured for this snapshot.
05 / What seniority reveals
Mentorship, classes, real projects, simulation, broad exposure.
Signal: learning velocityStrong foundations, guided responsibility, precise reasoning, collaboration.
Signal: potential with rigorDomain depth, production ownership, platform improvement, cross-team delivery.
Signal: demonstrated leverage06 / Evidence gates
PJS does not publish arbitrary readiness scores. Progress is measured through observable artifacts, pressure tests, and revisions.
Recover the idea, assumptions, interfaces, and boundaries without hiding behind terminology.
Produce the core logic independently and make the design choices explicit.
Challenge correctness, edge cases, leakage, robustness, and failure behavior.
Show how the work is configured, observed, recovered, and maintained.
Survive follow-up questions, alternatives, trade-offs, and a live change request.
07 / Repeated hiring signals
08 / Evidence boundary
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