Exceptional Promise: Material prep questions

Hello,
I am a UX Researcher at a product-led entertainment/streaming company and I plan on applying to GTV under digital tech. I have a few clarification questions beforehand and would appreciate any insights. Thanks in advance!

  1. Can I use my salaries/offer letters from two tech companies (my current and former) as two separate documents under MC? Or it is not recommended?
  2. For OC1, I am planning to use a Variety article talking about the product I’ve worked on as part of my evidence. The article does not mention my name though, just the product and how it is a new experience in the field. Is that fine?
  3. I am providing background information, a description of my work/contribution to the project, and results/impact in my documents in addition to screenshots of my work, its mention in internal/external sources, etc. Each section is around 3-6 sentences. I am wondering whether this is too verbose? I felt like I should give more context because UX researcher is not the most common occupation/application for digital tech.
  4. I led the creation of user sentiment measurement at my company. This is now included in tracking across all A/B tests. I also developed a sentiment to churn conversion metric to show revenue impact for the company. This is now used as one of the core KPIs at my company. Would this be a good MC? I also plan on getting a reference letter from a VP.

Hi @khu_ngu

  1. Salary documents are considered the weakest evidences and are insufficient to prove any criteria. Using two spots for a weak evidence is not the best strategy.
  2. Depends on what other evidence you are using to back your claim of attributing the innovation to yourself.
  3. It is not verbose but don’t fall into the trap of just providing a lot of written self-claims without strong backing evidences to validate the claims.
  4. It can be used in MC or OC3. MC is about impact in the industry hence choose projects that are larger in impact & scale and demonstrate that you are a potential leader in the industry. Whereas OC3 is about impact at company with quantified company metrics.
1 Like

Your salary documents from current and previous roles can be combined into a single mandatory evidence PDF. I recommend including a brief explanation of why you’re using payslips rather than contracts, and consider adding tax documents like Form 16 or I20 (or its equivalent) to strengthen this financial evidence.

The Variety article about your product shows market impact but needs supplemental evidence connecting you directly to the innovation. I suggest pairing it with internal documentation of your specific contributions to the project, along with a reference letter explicitly detailing your role in creating this new experience.

Your document structure sounds appropriate in length. Focus on quantifying results - specifically highlight how your user sentiment measurement directly influenced company KPIs and revenue. The VP reference letter should explicitly confirm your leadership in developing these metrics and their organizational adoption.

Your user sentiment work demonstrates clear commercial impact through measurable outcomes, making it strong for mandatory criteria. Emphasize the scale of implementation (company-wide tracking) and concrete business outcomes in both your evidence summary and recommendation letter.

As a UX researcher, your challenge is making technical contributions visible. Use before/after adoption metrics and include screenshots of dashboards where your metrics are used in decision-making. This tangible proof strengthens less traditional tech roles in the application process.

1 Like

@pahuja and @Akash_Joshi thank you both for the helpful feedback! I appreciate it.

To directly connect myself to the product mentioned in the Variety article, I am using example questions from the survey I’ve programmed and conducted (and showing my name on the screenshots) and the results showing as graphs I’ve analyzed and presented.

For sentiment work, I plan on showing 1-my work developing/researching it, 2- code repo for the metric, and 3- some internal documents showing that it is now a KPI used across the whole company and for different products. I am hoping that will be enough for MC!

1 Like