← Back to QuantathonMinix Quantathon
Official Guidelines

Quantathon Guidelines 2026

Mandatory guidelines for all registered participants of the Internal Quant Hackathon (Quantathon).

Contents

  1. 1. Team Composition
  2. 2. Eligibility
  3. 3. Allowed Markets, Data & Trading Rules
  4. 4. Technical Environment & Support
  5. 5. Submission
  6. 6. Judging Criteria & Methodology
  7. 7. Event Mode, Duration & Timeline
1

Team Composition

Team size

2–4 members per team. Solo participation is also allowed.

Cross-department teams

Encouraged and allowed.

Team changes after registration

Rosters are locked at registration. If a member becomes unavailable during the event, the remaining members may continue as a smaller team — no new members may be added mid-event.

Registration

Each team (or solo participant) registers once, before the event start, and is issued one team ID (see Section 4, Technical Environment & Support).

2

Eligibility

Who can participate

All employees.

Balance with live-floor duties

Hackathon work is done outside live-floor trading responsibilities. Participation must not disrupt or compromise regular live-floor operations or business responsibilities — employees on live-floor duty should schedule hackathon activity outside market hours or with manager sign-off.

Conflict of interest

Quant/trading-desk employees may participate, but must not use internal strategies in their submission.

3

Allowed Markets, Data & Trading Rules

Approved exchanges

NSE — Index Derivatives segment only.

Trading mode

Live paper trading and backtesting only.

Trade horizon

Intraday only — no overnight or positional holds.

Market data

Internal data feed via the MOSS sandbox environment only.

Research tooling

The internal research platform or the compute cluster.

AI code-generation tools

Participants may use any tool of their choice.

4

Technical Environment & Support

Environment & login

Each team (or solo participant) gets a separate environment ID and one shared team login — one login per team, not per member.

Support channel

Each team gets a dedicated Zoom support channel with an assigned point of contact (POC) to resolve queries.

5

Submission

Confidentiality

Any proprietary internal trading strategy cannot be used in this Quantathon.

Originality

The strategy must be the team's own work.

Presentation

Every qualifying team must present and explain their strategy to the panel.

Post-hackathon rights

Winning strategies may be reviewed by the quant/trading desk for potential adoption, at the company's discretion.

6

Judging Criteria & Methodology

The panel will run every submitted strategy against hidden, out-of-sample data, using an in-sample/out-of-sample Monte Carlo split — no team sees the exact test data in advance.

Primary criterion

Profitability on the hidden out-of-sample dataset.

Recommended secondary / tie-break criteria

Risk-adjusted return (e.g. Sharpe ratio), maximum drawdown, and consistency across the Monte Carlo runs.

Disqualifying condition: A strategy that goes negative on P&L at any point during its run, or is manually altered after being submitted and started, is excluded from ranking regardless of its final result.

For the full points breakdown, see Scored on Substance on the event page.

7

Event Mode, Duration & Timeline

Mode

Online.

Duration

3 days — 25–27 September.

This is the full guidelines document issued by the Core Organizing Committee. It governs in case of any conflict with other summaries on the event page.