ABOUT

Why Trajectory exists

Trajectory started much earlier than university.

After A Levels

Right after A Levels, I remember thinking I had to start making “serious” decisions. What field to go into, what skills to focus on, what kind of career I wanted to build.

But the problem was, I did not really understand what any of those paths actually looked like.

There was a lot of advice, but very little clarity.

  • Most of it was generic.
  • Some of it sounded impressive but did not apply to my situation.
  • And a lot of it only made sense in hindsight, not when you are just starting out.

That uncertainty carried into university.

At FAST and beyond

At FAST, especially trying to move toward FinTech and early-stage startups, the complexity only increased.

Roles overlap. Paths are not linear.

You see people doing product, growth, data, operations, all with different trajectories, but no clear map of how they got there.

Without a consistent mentor, it often felt like making decisions in isolation.

You choose courses, internships, and projects without fully knowing how they connect over time.

And in a fast-moving space, those early decisions compound quickly.

What Trajectory is for

That gap is what Trajectory is built for.

Instead of giving you one answer, it shows you multiple realistic paths from where you are today. A safer path, a faster path, and a higher-upside path. Each with its own timeline, skill requirements, and trade-offs.

Three paths

Safer path

Faster path

Higher-upside path

The goal is not to predict your future.

It is to make your options visible.

So instead of guessing, you can see how different choices might play out and decide what actually fits you.

This is something I wish existed when I was trying to figure things out.

Built by someone still navigating it.

You should not need perfect guidance to make better decisions.