AI summary
Round 1 93% · Fast track growth
Seven years of progressively senior delivery roles, all at verified SaaS companies. Led a billing platform rebuild across 14 teams, with a published postmortem. Strongest JD alignment in the pool.
Cover letter
Specific and backed by evidence. References our platform migration post and maps her rollout across three regions at Lumen Grid to it. Motivation is scope, not title.
Skill match
- Agile / Scrum at scale96
- SaaS release delivery94
- Stakeholder management91
- Risk & dependency mapping89
- Technical fluency (APIs, infra)86
Employer check
3 of 3 verified
- Verified
Lumen Grid · lumengrid.io
Senior Technical Project Manager · Mar 2022 – Present
- Registry
- Incorporated Feb 2015
- Claimed tenure
- 4.6 yrs
- Headcount
- 820 employees
Registry active · 2,400+ web mentions · SOC 2 report public
Verified: Established 11 yrs ago. Tenure matches 3 public engineering blog bylines.
- Verified
Brightpath Software · brightpath.dev
Technical Project Manager · Jun 2019 – Feb 2022
- Registry
- Incorporated Sep 2011
- Claimed tenure
- 2.7 yrs
- Headcount
- 310 employees
Registry active · Series C filing · 900+ web mentions
Verified: Established 15 yrs ago. Former manager confirmed role on reference network.
- Verified
Corva Systems · corvasystems.com
Associate Project Manager · Aug 2017 – May 2019
- Registry
- Incorporated Jan 2008
- Claimed tenure
- 1.8 yrs
- Headcount
- 1,450 employees
Registry active · Listed on Euronext Growth
Verified: Established 18 yrs ago.
Career path
Fast track growth
- 2017Associate PMCorva SystemsJoined
- 2019Technical PMBrightpath SoftwarePromotion
- 2022Senior TPMLumen GridPromotion
- 2024Senior TPM · Billing programme leadLumen GridPromotion
AI interview
31m 12s · completed Oct 24, 10:42
Q1Walk me through a SaaS release you delivered across several teams. How did you keep scope, dates and stakeholders aligned?
93“The billing platform rebuild at Lumen Grid: 14 teams, 9 months. I ran a single dependency map in Jira Advanced Roadmaps, a fortnightly steering review with finance, and a weekly risk burn-down. We shipped two weeks late but with zero P1s at cutover.”
Concrete scale, named tooling, honest about the slip. Strong signal on programme governance.
Q2Two engineering leads disagree on whether to cut scope or slip the date. Leadership wants both. How do you run that conversation?
89“I'd put the tradeoff in front of leadership as two costed options instead of asking them to pick a side. Usually one lead's concern is really about a single risky epic, so we de-scope that and keep the date.”
Mature framing. Moves the decision to the right owner with data.
Q3How do you decide when a Scrum cadence is helping a programme versus slowing it down?
88“When ceremonies stop changing decisions. On the infra team we moved to Kanban with a monthly planning sync because sprint goals were fiction for work driven by interruptions.”
Pragmatic, not dogmatic about Agile.
Q4Your CV says you led a 14-team billing migration. What was the hardest dependency, and what would you do differently?
90“Tax engine vendor's sandbox lagged production by a full release. I'd negotiate a contractual sandbox SLA up front next time; we lost three weeks to that.”
Specific, verifiable detail consistent with the Lumen Grid engineering blog.
Scores
- CV93
- Employers96
- Interview90
- Presence94
Presence & integrity
Average 90
97%
Gaze on screen
0
Tab switches
Clear
AI-written
