Stories / Behavioral Flashcards

1
Q

developed customer and product requirements

A

3 - transform NEXTUSER from a retargeting tool into a CDP product

Change direction of the product
Context
Business analyst
Messaging limiting with limited triggers
Not unique solutions
User journey
Saving the data we collected in our system and looking at it from a business perspective there was one common denominator across all our clients.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

convinced engineering to build a particular feature

A

1 - Workflow interactions

Duplicate feature
Value of the platform
Information needed to understand the performance of workflows
Marketer key decision maker
Bypass funnels to create interactions
Concern from developers
Give him my information
Increase stickiness and retention rate
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

made a trade-off between two technical alternatives

A

4 - Reporting dashboards - Aggregates

Problem with aggregate calculations throughout the platform
Aggregates KPIs are counts
Calculate ID count for each day
No complain because small enough
Use recursion
O(n)
Hyperloglog 
Drawback - within 3% of accuracy.
Cost savings
Less frustrations
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

created the product roadmap, vision and strategy

A

3 - transform NEXTUSER from a retargeting tool into a CDP product

Change direction of the product
Context
Business analyst
Messaging limiting with limited triggers
Not unique solutions
User journey
Saving the data we collected in our system and looking at it from a business perspective there was one common denominator across all our clients.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

led a team

A

3 - transform NEXTUSER from a retargeting tool into a CDP product

Change direction of the product
Context
Business analyst
Messaging limiting with limited triggers
Not unique solutions
User journey
Saving the data we collected in our system and looking at it from a business perspective there was one common denominator across all our clients.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

dealt with a difficult team member

A

1 - Workflow interactions

Duplicate feature
Value of the platform
Information needed to understand the performance of workflows
Marketer key decision maker
Bypass funnels to create interactions
Concern from developers
Give him my information
Increase stickiness and retention rate
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

executed a plan that grew top line results

A

3 - transform NEXTUSER from a retargeting tool into a CDP product

Change direction of the product
Context
Business analyst
Messaging limiting with limited triggers
Not unique solutions
User journey
Saving the data we collected in our system and looking at it from a business perspective there was one common denominator across all our clients.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

took initiative when not asked to do so

A

3- transform NEXTUSER from a retargeting tool into a CDP product

transform NEXTUSER from a retargeting tool into a CDP product

Change direction of the product
Context
Business analyst
Messaging limiting with limited triggers
Not unique solutions
User journey
Saving the data we collected in our system and looking at it from a business perspective there was one common denominator across all our clients.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

made an important decision under time pressure

A

2 -

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

analyzed a large data set

A

4 - Reporting dashboards - Aggregates

Problem with aggregate calculations throughout the platform
Aggregates KPIs are counts
Calculate ID count for each day
No complain because small enough
Use recursion
O(n)
Hyperloglog 
Drawback - within 3% of accuracy.
Cost savings
Less frustrations
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

gained consensus

A

1 - Workflow interactions

Duplicate feature
Value of the platform
Information needed to understand the performance of workflows
Marketer key decision maker
Bypass funnels to create interactions
Concern from developers
Give him my information
Increase stickiness and retention rate
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

adjusted your project plan to accommodate unforeseen issues

A

2-

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

juggled multiple projects at once

A

5 - Pomodoro

1- Use the pomodoro technic
2- Have an excel sheet that lists 16 slots of 30 minutes.
3- I do my list from one day to the next
4- Now I always have 40 to 60% of my list that will end up being moved.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

managed the complete product life cycle

A

3 - transform NEXTUSER from a retargeting tool into a CDP product

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Stories

A
Implementation of the AB test feature
User profiles
Segments
Funnels 
Clusters
Labels
Automatic segments
Data feeds
Product feed 
Recommendations 
Personalization automation
k means clustering
LogN
Multivariate
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What are your weaknesses?

A
  • Implementing tracking for product optimization

- Spending time for review of user metrics on existing features.

17
Q

Tell me about a time when you failed.

A
  1. Provide the context and the situation that led to the failure.
  2. Discuss the failure and its impact on the organization.
  3. Highlight your contribution to the failure.
  4. Walk through how you mitigated the failure.
  5. Reflect on how you made your organization more resilient to future failure.

Segment feature, failure to use.

18
Q

What makes a good PM?

What is a good PM’s process?

A

V1:
1- Self learner
2- Story teller
3- Multi talented.

V2:
1- Creativity
2- Passion
3- Market understanding

What is a good PM’s process:
○ Build
○ Measure
○ Learn

Measured by outcome, not by output.
Works against key metrics.

19
Q

How to say no

A

Saying “NO” by validation
Saying “NO” by prioritisation
Saying “NO” by providing an alternative
Saying “NO” by saying “YES”