Project Coordinator · PMO Analyst · Junior PM

Projectsthatland.

I coordinated five developers across three concurrent projects, kept the board honest, and wrote down what every decision cost. Computer systems engineer by training — I can follow the conversation as well as schedule it.

View my work ↗
Sarishma Kumal
1.5+
years coordinating
software delivery
Selected work

Where I've delivered

Hire me ↗
01

Mindrisers

Project Coordinator · Feb 2024 – Jul 2025 · Nepal

Software development company. Reported to the Project Manager, coordinating five developers across three concurrent client projects — including Recruit Nepal, a recruitment platform with separate candidate, recruiter and employer portals, and Digital Palika, an ERP system for local government financial decision-making.

  • Ran the board in Jira, chased daily progress and tracked time against plan
  • Coordinated with the Product Owner on requirements and priorities
  • Reported progress to the Project Manager and flagged slippage early, not at the deadline
  • Removed blockers by working through them directly with the developers
  • Tested features before client release, tracked defects to resolution
  • Wrote feature lists, requirements and user manuals
02

Uni Compass AI

Co-founder & product lead · 2026 – present

Employability platform for international students at UK universities — the job market conventions nobody explains to them, from CV norms to which roles a visa permits.

  • Scoped twelve screens end to end and held that scope under pressure
  • Keep a decision log recording each call with its accepted cost
  • Set weekly reporting rules so status can't drift optimistic
  • Validated with real students and university staff
  • Benchmarked the interface against a live competitor
What I do
  • Project coordination
  • Status reporting
  • Requirements & documentation
  • Testing & defect tracking
  • Risk identification
  • Scope control

Clear scope.
Honest status.

Most delivery problems are not technical. They are someone finding out too late. My job is to make sure the picture on the board is the picture in the room — which means chasing progress before it is asked for, and saying a date is at risk while there is still time to do something about it.

Tools
  • Jira
  • Agile & Scrum
  • Figma
  • Canva
  • Claude Code
  • Microsoft Office
Decision register

Six calls, and what each cost

A decision without a stated trade-off is just a preference. Every record carries its price — including the one I got wrong and reversed.
01BRAND RISK

Renamed the company mid-project after a trademark collision

Context
We were trading as "UniPath AI" until I found a collision with UiPath, a listed company in an adjacent software category.
Call
Rename immediately and rebuild the identity around a compass metaphor, rather than carry the risk forward.
Cost
Lost the existing brand work and absorbed a rework cycle — better than building equity in a name we might be forced to drop.
02MONETISATION

Made the free tier the entire MVP core

Context
Acquisition runs through campus ambassadors and sharing, which only works if the free product is worth recommending unprompted.
Call
Give the core platform away. Reserve premium for deeper CV analysis, AI mock interviews, version history and visa-aware matching.
Cost
Revenue deferred on purpose. Charging early would have throttled the growth loop the strategy depends on.
03REVERSAL

Overturned a decision I had already locked

Context
We had locked the CV Quality Score as internal-only, hidden from students.
Call
Reversed it. The score is visible, with a status label, one "Fix this first" card and a pass/fail checklist per category.
Cost
Reopened settled design work and conceded the first call was wrong. A hidden score gave students no reason to come back.
04SCOPE

Held full scope instead of cutting to hit a date

Context
The obvious move under time pressure was to cut features and ship something narrower.
Call
Hold all twelve screens — a partial employability tool doesn't solve the problem a student actually has.
Cost
A longer timeline, accepted with eyes open and recorded at the time rather than discovered late.
05BENCHMARK

Benchmarked the interface against a live competitor

Context
For a product asking students to trust it with their CV, credibility matters more than novelty.
Call
Benchmarked the feedback screen against CareerSet for navigability, and set the visual direction to sit inside category expectations.
Cost
Less room for a distinctive look, traded for an interface students already know how to read.
06DRIFT CONTROL

Ran every new feature back against the original value map

Context
Scope drift is the standard failure mode for a product designed across months.
Call
Cross-check each gap against the business proposal's value map, so new ideas must earn their place.
Cost
Slower to add features, and some genuinely good ideas were held back for failing the test.
How I work

Five steps, every time

01
Benchmark
Look at what already exists before designing anything. Credibility beats novelty.
02
Scope
Define what is in and what is out, and write it where everyone can see it.
03
Decide
Log the call and the cost accepted with it, at the time — not afterwards.
04
Track
Keep the board current and chase progress before anyone has to ask for it.
05
Report
Weekly, to fixed rules, so a status means the same thing every time.
PARTLY DONECounts as in progress. Never as done.
RED · OFF TRACKMissed external deadlines only.
AMBER · AT RISKInternal slips — visible, not escalated as failure.
BLOCKEDListed under in progress, never buried in an annex.
EVERY UPDATECarries a wins line and a completed count.

The red-versus-amber line is the part I'd defend in an interview. Mark every internal slip red and people learn to ignore red. Reserve it for external commitments and a red flag still means something when it appears.

Background

Engineering, then delivery

2019 – 2023
BSc (Hons) Computer Systems Engineering
University of Sunderland, UK — studied at ISMT College, Kathmandu
2024 – 2025
Project Coordinator
Mindrisers, Nepal — five developers, three concurrent projects
2025 – 2026
MSc Management with Marketing
University of Huddersfield, London — completing September 2026
In progress
PRINCE2 Foundation
Principles, people, business case. Scrum methodologies — Coursera
Get in touch

Let's build
something that ships.

Looking for a paid graduate internship or entry-level project role in the UK IT and digital sector. Available from October 2026 — London, hybrid or remote, or anywhere in the UK.

sarishmakumal9814@gmail.com
linkedin.com/in/sarishmakumal
+44 7491 774318