Open to work
36.1716° N, 115.1391° W  //  Las Vegas, Nevada
Engineering Project Manager

Jaison Dsouzaships systems.

Turning ambiguous scope / into measurable product outcomes

PMP-certified delivery lead with 7+ years steering software, SaaS, health-tech, and data-driven products across engineering, product, QA, analytics, and operations teams.

PMPPSM IPSPO I7+ YEARS95% FORECAST ACCURACY
Jaison Dsouza
Jaison Dsouza
SCROLL
+30%
Team throughput
lifted
−35%
Post-deploy
defects
−40%
Release
blockers
3 wks
Faster MVP
per cycle
Overview

A project manager who thinks in dependencies.

I lead delivery where the path isn't drawn yet. The work starts as a tangle of competing priorities, half-formed requirements, and teams spread across five time zones — and my job is to give it structure, sequence, and a date you can trust.

Over seven years I've built technical project plans, roadmaps, work breakdown structures, risk registers, and release-readiness gates for SaaS, health-tech, and data products. I translate ambiguous scope into acceptance criteria and sprint commitments, then hold the line through delivery.

The result is the same wherever I land: more predictable releases, fewer defects, faster MVPs, and stakeholders who always know where things stand.

At a glance

BaseLas Vegas, NV
RoleEngineering Project Manager
FocusSaaS · Health-tech · Data
LanguagesEnglish · Hindi
How I work

Ambiguity in. Predictability out.

A simple operating model I bring to every team, whatever the stack or the stage.

01

Make the plan legible

Break scope into a work breakdown structure, map the dependencies, and commit to a date the team can defend — not a hopeful one.

02

Surface risk early

A living risk register and release-readiness gates mean trouble shows up in a standup, not on launch day.

03

Communicate to the audience

Engineers get detail; executives get decisions and trade-offs. Everyone always knows where things stand.

04

Close the loop

Retrospectives and postmortems turn into systemic fixes, so the same defect or delay doesn't return next cycle.

What I do

The toolkit behind a clean delivery.

Each of these is a lever I pull to take a release from ambiguous to predictable.

Technical project plans & roadmaps

Plans, milestones, and release schedules teams can actually run against.

Agile / Scrum / Kanban

Sprint planning, ceremonies, and flow tuned to how the team really works.

JIRA administration & automation

Workflows and automation rules that erase hours of manual sprint admin.

WBS & resource planning

Breaking scope into work, then matching it to the people and time available.

Risk, dependency & issue management

Risk registers and dependency trackers that surface trouble before it lands.

Release readiness & QA oversight

Go/no-go gates and UAT that keep defects out of production.

Forecasting & estimation

Commitments backed by data — 95%+ forecast accuracy over 24 months.

Executive communication

Status, risks, and mitigation framed for the people who fund the work.

Retrospectives & process optimization

Turning postmortems and findings into systemic fixes that stick.

Track record

Where the work landed.

Aug 2022 — PresentLas Vegas, NV
01

Project / Product Manager

Mvation Worldwide Inc.
  • Led end-to-end delivery of scalable SaaS platforms across 3 concurrent engineering workstreams — project plans, sprint roadmaps, milestones, dependency trackers, and release schedules.
  • Built JIRA workflows and automation that erased ~6 hrs/week of manual sprint admin and lifted team throughput by 30%.
  • Owned a 150+ story backlog, translating ambiguous requirements into WBS, acceptance criteria, and sprint commitments at 95%+ forecast accuracy over 24 months.
  • Drove alignment across product, engineering, QA, and ops in 5 time zones — cutting release blockers 40% and accelerating MVP delivery by 3 weeks per cycle.
  • Established release-readiness gates, risk registers, and retrospectives that reduced post-deployment defects by 35%.
Apr 2021 — Jul 2022Dubai, UAE
02

Project Manager

Kitopi
  • Managed storefront analytics and software delivery across product, engineering, marketing, and ops — using behavioral data to reprioritize the Q3 roadmap within 6 weeks.
  • Tracked schedules, launch dependencies, UAT plans, and go/no-go criteria across 3 regional storefronts.
  • Led 12 incident postmortems; converted findings into systemic fixes that cut downtime from 4.2 to 3.1 hrs/month.
  • Delivered stakeholder status on release progress and risk, protecting $200K+ in digital ad spend from wasted targeting.
Apr 2019 — Jan 2021Bengaluru, India
03

Senior Product Support Manager

Practo
  • Managed 50+ enterprise healthcare escalations per quarter, improving resolution SLA from 72+ to under 48 hrs.
  • Built a 200-article knowledge base and 3-tier escalation framework — onboarding down 40%, repeat escalations down 22%.
  • Partnered with product and engineering to ship 9 bug fixes and 4 enhancements informed by support patterns and UAT.
Oct 2017 — Apr 2019Bengaluru, India
04

Product Support Manager

Practo
  • Supported 100+ tickets/week at 94% CSAT, triaging production issues and keeping customers and stakeholders informed.
  • Partnered on 3 major launches; pre-release UAT feedback prevented 7 P1 defects from reaching production.
In practice

The artifacts behind the outcomes.

Representative examples of how I structure delivery — the planning, the flow, and the risk discipline.

Delivery roadmapREPRESENTATIVE
LQ1Q2Q3Q4
Discovery & scope
Architecture
Build — MVP
Hardening & UAT
Launch & stabilize
Sprint boardREPRESENTATIVE
To do 5
Define API contract
Auth edge cases
In progress 2
Checkout flow
Payment retries
Done 8
Onboarding v2
Rate limiting
Risk registerREPRESENTATIVE
RiskSeverityMitigation
Vendor API rate limitsHighCache + backoff; fallback path
UAT slips past freezeMedDaily go/no-go; buffer sprint
Cross-team dependencyMedShared tracker; weekly sync
Data migration gapsLowDry-run + reconciliation

// Illustrative samples to show method — not actual client data.

Credentials

Certified, educated, equipped.

Industry certifications verified on Credly, plus the academic foundation and the toolkit I work in.

Education

MCA — Master of Computer Applications
St. Aloysius Institute of Management & IT (AIMIT), Mangalore · 2014–2017
BCA — Bachelor of Computer Applications
St. Mary's College, Shirva · 2012–2014

Tools & methods

JiraConfluenceAgile / ScrumKanbanSprint planningRoadmappingBacklog managementUser stories & acceptance criteriaWBSEstimation & forecastingRisk registersDependency trackingRelease readinessUATRetrospectivesRoot-cause analysisStakeholder managementExecutive reporting
Next step

Let's build something predictable.

Open to engineering project and product management roles. Send a note below, or reach me directly.

Email copied