← Home
Partner Basecamp · Org Profile

EPAM

5 cohorts  ·  0 feedback entries  ·  0 open actions
Programme record · EPAM

Quantitative data from post-programme surveys. NPS, participation, and benchmark against programme average across all cohorts attended.

Pooled NPS
too few to report
n=8 D2 · need ≥20
Cohorts attended
5
CohortCityDatesD1 nD2 nNPSProg avgGapP/Pa/D
C12San FranciscoMay 28-29, 202632-50+50-100
P 0%/Pa 50%/D 50%
C12San FranciscoMay 28-29, 202620
C18San FranciscoJune 22–23, 202622+0+35-35
P 0%/Pa 100%/D 0%
C19San FranciscoJune 24–25, 202633-33+55-88
P 0%/Pa 67%/D 33%
C20San FranciscoJuly 14–15, 202611+100+35+65
P 100%/Pa 0%/D 0%
Capability Profile
Persona mix
Developer 25%Architect 42%T.Lead 33%
AI proficiency
Applying 17%Independent 50%Frontier 33%
Seniority mix
Sr Prac 67%Mgr 33%
Content depth
Too basic 56%About right 44%
Pace
Too slow 22%Well paced 67%Too fast 11%
Relevance (mean)
4.0 / 5
D1 confidence (mean)
4.6 / 5
Confidence Δ (D1→D2)
n=8 · too few
Confidence growth by domain
Build Δ
n=1 · too few
Design Δ
n=1 · too few
Commercial Δ
n=1 · too few
Persona × Seniority
PersonaIndividual ContributorSr PractitionerMgr / Sr MgrDirectorSVP / C-Level
Architect21
Developer11
Transformation Lead
Persona × AI Proficiency
PersonaLearningApplyingIndependentFrontier
Architect122
Developer11
Transformation Lead11
Strategic Insights
Advanced readiness: 33% at Frontier level — partner is ready for complex implementation engagements
Feedback log · EPAM

Anecdotal feedback from partner reps, stakeholders, and other sources. Each entry is sourced and benchmarked against survey data where available. Hearsay entries are flagged — weight accordingly.

No feedback logged yet. Run org_intake.py to add entries.
Action items · EPAM

Org-specific actions arising from survey data and feedback. Programme-wide actions are tracked separately in programme-actions.yaml.

No open action items.