Asset Management

• The team meets once a week, then divides the work between research and the platform.
• On the research side, members study portfolio risk metrics and models, decide which ones are useful and write each fund's report from the calculated KPIs.
• On the development and operations side, members implement those models, add tests and keep the CI/CD pipeline ready for production.
• Both sides meet in the report. Research sets the requirement, development implements it and the fund manager receives the result.

• The platform itself: 210 Python modules behind seven task workspaces, with CI/CD and a nightly pipeline that replays every transaction and recomputes the analytics after the close.
• A risk report per fund, with KPIs, mandate breach alerts and recommendations, sent to the fund leads.
• Research articles on risk and portfolio management.

You start with the project files and onboarding material, so you understand the dependencies and the whole workflow before changing anything. Then you pick a front: on code, you build a platform improvement alongside a current member; on reports, you write one section under supervision, with the existing reports as your reference.

This team suits people who like building systems and tend to notice what could work better. Students designed the platform, chose its methodology and still run it, so a member can follow one feature from the initial research to its use by a fund manager. Every risk analyst is also allocated to a fund and therefore understands how the portfolio behind their report is managed.

Risk has a lot in common with Quantitative Trading: Python, models and portfolio data are part of both. Risk uses them to assess exposures, limits and model reliability for funds managed by people. Quant teams use them to construct strategies or build the systems that execute those strategies.

vs Portfolio Optimisation →

Both teams research portfolio models in Python. Portfolio Optimisation builds and validates an allocation or strategy. Risk independently measures the exposure and mandate compliance of portfolios managed by the fund teams.

vs Strategy Application →

Both teams operate production data systems. Strategy Application uses model output to place unattended orders. Risk uses portfolio data to produce controls, reports and recommendations, while the fund manager makes the final decision.

vs Macro →

Both teams contribute to the same fund decisions. Macro explains the economic and geopolitical setting. Risk checks the portfolio through measured exposures, limits and model validation.

The team checks independently whether the risk taken matches each fund's mandate, objectives and profile, which surfaces excessive concentration, shifts in exposure or deteriorating risk before any of it becomes material. A finding goes to the fund lead with the quantitative context behind it, and the team follows the response. The final call stays with the manager. Because the number has to survive that conversation, the team validates the data, tests the models and keeps every result traceable, and a change passes code review, automated tests and the data-quality gate before it reaches production.

The dashboard carries a tutor that opens from whatever KPI or chart you are looking at: 33 reviewed concepts, 16 lessons, 18 methodology guides and a seven-level path with prerequisites and a capstone. It exists because a risk number nobody understands is not a control, it is decoration. No formula or worked number in it is generated by a language model.

• The work is divided into thematic desks: Macro Dashboard, Monetary Policy and Rates, Key Regions covering the US, Europe, China and emerging markets, and Markets. Each member follows one desk in depth.
• At the weekly meeting, each member adds the latest developments from their desk to that month's overall view.
• In the final week of the month, the normal meeting becomes a presentation of the report. The rest of TIC can attend and give feedback.
• The current desk structure is provisional and the team can change it when the work calls for a different split.

• The Monthly Macro Report: the month's picture, ending in what it means in practice for the three funds.
• Research articles for the TIC Journal, going deeper on one theme from a single desk.
• A monthly presentation of the report, open to the rest of the club for feedback.

Before contributing to the monthly report, you study the main subject of your assigned desk in depth. Depending on the desk, that may be the mechanics of interest rates and monetary policy or the current geopolitical environment. You present the work to the team and use it as the basis for your regular contribution.

This team is for people who already follow the economy and current affairs without being asked to. You will learn to read indicators such as CPI, PMI and yields and to work the data in Excel, and no prior knowledge of them is expected. Because the report is recurring and collaborative, deadlines matter here more than in a team working at its own pace.

Macro has more in common with Investment Banking than with Quant. Both do research that ends in a written conclusion and a view someone has to defend. The difference is the unit of analysis: Macro works at the level of an economy, a region or a market, Investment Banking at the level of one company.

vs Investment Banking →

Investment Banking researches one company and the deal or position that follows from it. We work at the level of an economy, a region or a market, and the reading we produce is the context those decisions sit in.

vs Risk →

Both teams contribute to the same fund decisions. Risk begins with measured portfolio exposures and model validation. Macro begins with the economy, monetary policy and geopolitics, using indicators to support its reading.

The team splits into thematic desks, currently the macro dashboard, monetary policy and rates, the key regions covering the US, Europe, China and emerging markets, and markets. Each member owns one desk and follows it in depth, and the monthly report is where those separate readings have to agree with each other. The split is provisional and changes when the team decides it should.