Showing posts with label data product manager interview questions. Show all posts
Showing posts with label data product manager interview questions. Show all posts

Product Manager Q&A

What is the best way to interface with customers? 

  • Face to face meetings
  1. I believe face to face meetings are the best if you have the luxury to meet your customers. During your f2f meetings, you can see how your customers are using your product and you will be able to gain some valuable insights. 
  2. For ex: If you have a business product then ask for customers for the flow diagrams that include your product in the flow. Ask them about any client proposals that they are working on and have worked on. Study those as nuggets of information can be found there. As a data PM, it is always useful to read these plans to understand how and where your products are used.

  • Phone calls
  1. If f2f meetings are not possible then go with phone call. Try to schedule a regular phone call with your customers to understand the pain points. 
  2. Ask them directly: Is there something you would like us to improve for you. What works best for you? What needs to be improved? Most often they have their answers ready.

  • Emails
  1. In come cases, just the emailing works. If this is the case then make them a priority and respond them within reasonable times. Sooner the better.! This shows them they you care about delivering a quality product. 
  2. If they are requesting a feature from you and you know its going to take time, try to be open about the timelines. Ask them if there is anything they would like you to do while the much needed feature is in process. This softens the customers a bit and they are open for negotiation. 

---------------------------------------------------------------------------------------------------------------------


What's the best way to work with the executives?

  1. Executives are busy people and they appreciate brevity. What is important to you might not be important to them. So we always have to be mindful of their time. 
  2. They care a lot about strategy than tactics. They care about business and product goals more than day to day execution. 
  3. Any suggestions that move the needle in direction of business goals will gain their attention. So to make any interaction valuable with them, focus on strategy and tell them on how you can help them better achieve the goals.
  4. While talking to them its important to talk about revenue generation, strategy, important KPIs that relate back to strategy, product metrics that are helping achieve the KPIs.
  5. While working on a problem, they are looking for solutions and which solution will work best for them. They usually care less about day to day execution but its best to have that information handy when asked! 
  6. Don't provide wrong answers to them. If you don't know, tell them you will get back to them after looking into it.
To summarize while working with executives:
  1. Talk about:
    1. Strategy
    2. KPIs
    3. Business and Product Goals
    4. Solutions to existing problems. 
  2. Avoid talking about: 
    1. Tactics
    2. Only problems
    3. Wrong answers

---------------------------------------------------------------------------------------------------


What's your approach to hiring? 

Hiring the best is always the motto of any organization but other dimension to hiring is 'How well this person will solve the business problem at hand'. Here are few common dimensions to consider while hiring: 
  • Business goals
  1. Let's say my team is really swamped and they could use some help then I will hire someone with specific skills set. I will work with the team manager to identify a specific skill-set that will benefit the team. And if I know exactly what projects we have to deliver and if we get a person with the exact skill set then I will go ahead with that person.
  2. However if I am hiring for an long term business goals then I will hire someone with determination and eagerness to learn. Someone who might not have demonstrated bigger professional achievements but is willing to explore and take on challenges.  I will look for someone who has done some projects on the side that explains their motivation to try new things and new challenges.

  • Cultural fit
  1. Every organization is different. I will conduct cultural fit interview based on situation. If company is fast paced then I will pick a candidate who likes such an environment. 
  2. If company is stable and not looking for much innovation then will pick a candidate accordingly.

  • Love for company's product offering
  1. It best to see if they are interested in company's product offering. If someone hates the company's product then there is no point hiring them. Their work will reflect it in the product. If they are not doing it with love then why affect quality of the product. 


----------------------------------------------------------------------------------------------------------------------------

How do you know an industry is ripe for disruption?

These points can provide some insights into it. But they are just the pointers, you will have to do some research to strengthen your insights. 
  1. Power is consolidated
  2. Consumers are using outdated Technology
  3. Business pratices aren't changing despite -ve feedback
  4. The research backs you up
  5. Reference: Link
----------------------------------------------------------------------------------------------------------------------------


In 2 mins, describe what a PM does. 

  1. A PM is a person who works tirelessly with different departments to constantly fill in the gaps that arise while product development, research, testing, legal, operations, resourcing teams etc. 
  2. PM works with the Legal team to fill gaps between technical teams and Legal fine prints. 
  3. Works with procurement teams to ensure appropriate deals/tools/resources are procured for the product to be delivered in time.
  4. Works with Engineering to translate business requirements to technical requirements. 
  5. Works with Executives to keep them aware of progress and assures them their business goals and key KPIs are achieved. 


Product manager design question #2

How would you implement Google Chrome for Kids navigation.

As usual we will tackle this design question with keeping Goal in mind. We will then list out the personas, their use-cases, features, metrics to track, and prioritization.

Goal: Safe browsing for kids.

Personas:
  1. Toddler
  2. Young kids
  3. Teenagers

Use-cases:
  1. Education
  2. Browsing
  3. Entertainment

Solutions/Features
  1. Profiling: While setting up the browser the parent/authority will set the profile in a manner so that safe browsing is always enabled. Payments are automatically disabled in this profile.
    1. Pros: Serves the purpose
    2. Cons: Extra setup and some technical expertise.
  2. API call:
    1. When call is initiated from the safe profile then safe results are surfaced.
    2. Payment fails if the call is initiated from the safe profile. This ensures that child doesn't order digital products by mistake.
    3. Pros: Serves the purpose.
    4. Cons: Requires expertise as to which content makes sense v/s which does not.
  3. Notification: If weird/questionable content is requested then notification is sent to the authorities for review.
    1. Pros: Proactive notifications ensure parents are on top of their kids searches.
    2. Cons: Chances of false positive. If kids is required to do some weird searches for their biology class then it will result into false positives.
  4. Override for parent functionality wherein they can use the same browser for their use.
    1. Pros: Convenience. No need of second browser on same machine.
    2. Cons: Chances are kid could learn how to override defeating the whole idea.
  5. Reporting a summary of their kids searches.
  6. Mature APIs based on search results and customer satisfaction.

Metric:
  1. Customer satisfaction: Need to ensure that parents are satisfied with the product. And children are able to use it with ease.
  2. Implementation complexity: Based on customer satisfaction, we will prioritize features based on implementation complexity. High complexity features can start earlier. Features on which a lot of other features are dependent can start earlier.

Prioritization:

  1. Profiling as it a basic feature & API call as its part of the basic feature as must haves in MVP.
  2. Override is also MVP as otherwise the browser will be unusable for the parents.
  3. Notification, Reporting, Mature APIs can be part second release.

Product management: Marketing Frameworks: Cheat Sheet


During Product management interviews a lot of interviewers ask 'How will you market a product?' Reason is a lot of positions require interaction with the marketing teams, hence the question. For these type of questions, its best to answer with some frameworks. Here are 3 such frameworks to help construct your answers.

  • AIDA
  • REAN
  • Marketing mix – 4Ps

AIDA:

This framework is useful for convincing the customer to buy your product. Here is the description of each of its phases

  1. Attention: Get customer’s attention.
  2. Interest: Get them interested in your product by telling them how it is going to solve the problem.
  3. Desire: Make customers want your product by telling them how it will help them.
  4. Action: Enable them to purchase the product.


REAN:

This framework is useful to maintain the relationship with the customer and keep them engaged so they remain your loyal customer.


  1. Reach: Reach out to existing or new customers.
  2. Engage: Engage with them by understanding their needs and relate it to the product features.
  3. Activate: Motivate customer to purchase your product.
  4. Nurture: Keep engaging with them to know their pain points and solve it at regular intervals.

Marketing mix – 4Ps


  1. Product: 
    1. What are the product’s features and how does it caters to the customer’s needs. 
  2. Price:
    1. Determines the customer personas who are buying the product or willing to buy the product. 
    2. How many customers purchase the product.
    3. Different prices for different channels like online, offline, retail stores, door to door marketing, etc
  3. Promotion:
    1. All forms of Ads, PR, word of mouth, sales,
  4. Place:
    1. Online or offline or at home. For ex:
      1. Online: Amazon or ebay or retail site
      2. Offline: Physical store, kiosk at mall
      3. At-home: Gym instructor coming to home for personal training.

Hope you liked this cheat sheet as it will come in handy for the interview process. If you want cheat sheets on more topics, then please comment down below. I will be happy to create them for you. 

Distributed datastore Basics - Part 3

Commodity computers like normal desktop that we use at home.

Why you need to scale?
Performance is degraded as customers are complaining that requests are taking more time.

Vertical Scaling: 
Upgrade the server to handle volume of requests easily. Upgrading single server's capability much more. 

Horizontal Scaling:
  1. Add more machines to the cluster. 
  2. Cheaper than vertical scaling. 
  3. If service is not heavily used then more machines from the cluster. Service is not impacted since you are adding more machines to direct the traffic and removing the machines so requests are served by some or the other machine at any given point.
  4. We can store the machines in different continents. 
Conclusion:
  1. Vertical scaling is cost efficient in short term as you are buy less H/W. Horizontal scaling is cost efficient in long run. 
  2. Vertical scaling is not fault tolerant as its only one machine. 

Advantages of distributed systems: 
  1. Fault tolerance:
    1. If server in a country goes down then requests can be directed to another server in another country.
    2. User will see more latency but the service remains available. 
  2. Low Latency:
    1. You can place the server near to where most requests are originating in case of HS but in VS there is only few servers so users will wait for their response. 
    2. Time taken to send and receive the request will go down. Only time consumed will be the time taken by the service. 

Qualitative v/s Quantitative Research

Qualitative Research

  1. Primary exploratory research
  2. Gain insights into: 
    1. Underlying reasons, motivations, and opinions, problems
  3. Hypothesis for potential quantitative research
  4. Unstructured or semi-structured. 
  5. Data collection methods:
    1. Group discussions 
    2. Individual interviews
    3. Participation and Observation 
  6. Sample size is usually small.

Quantitative Research
  1. Quantify the problem by generating data or stats. 
  2. Uses stats to measure data and observe patterns. 
  3. Structured. 
  4. Data collection methods:
    1. Online surveys
    2. F2F or telly interviews
    3. Online polls

Project management interview questions & answers - Part III

How have you contributed to the success of the project? 
By:
  1. Understanding end goals.
  2. Understanding my role and each team's roles.
  3. Identifying Interdependencies and stating them early on. 
  4. Cross functional and periodic communication via emails, standups, meetings. 
  5. Setting up milestones and periodic checking enabling team to collaborate well.   
  6. Accepting and managing problems.
  7. Recognizing and rewarding the teams. 

How would you increase efficiency of your development team? 
By:
  1. Document Coding and dev standards.
  2. Implement CI integration. 
  3. Release often if possible.
  4. Schedule demos.
  5. Follow test driven development. 
  6. Creating detailed tasks. 
  7. Review backlog
  8. Resolve blockers. 
  9. Have short meetings.
  10. Support initiative 
  11. Rely and trust your team's expertise, where ever possible. 


If you come about an early delay in one of your milestones what would you do?
  1. Catch them early by monitoring the progress of the project and staying in touch with leads through out the project. 
  2. Notify stakeholders: Update them on delay and revised schedules. 
  3. Call for a meeting: Dev, technical teams, vendors, stakeholders, customers and update them on the delay. 
  4. Gather the right resources: Re-allocate the resources. 
  5. Reschedule: Check if some activities that were planned sequentially can be done parallely.
  6. Re-prioritize: List out all the activities that are not yet done. Move the important ones to the top of the list. 
  7. Document the updated plan and send it out to everyone.  

How to decide between traditional project management v/s Agile methologies?
Use traditional when:
  1. Long and detailed planning is required. 
  2. Processes is linear and all the tasks are scheduled sequentially. 
  3. Requires a formal CM process. 
  4. Prioritization is fixed.
  5. Customer feedback can be taken at the end and incorporated into future releases. Customer involvement is low. 
  6. Organization is very centralized. 
  7. ROI is achieved at product release.
  8. Ex: Hardware or non-customer facing projects like infrastructure or technology changes. 
Use Agile when: 
  1. Process and decision making is iterative.
  2. Need customer feedback right away and can be incorporate right away.
  3. Organization is de-centralized. 
  4. Prioritization changes based on business requirements and customer feedback. 
  5. Small amount of work is picked up to be done. Rest can be updated and prioritized based on inputs. 
  6. Customer involvement is high.
  7. ROI is achieved often and is iterative. It determines what the future releases. 

What are the various states of the project? - RYG. What do they stand for? How to move the project from R to G?
Green: Project is within budget, timeline, and expectation.
Yellow: Project might fallout of budget, timeline or expectation and is it risk. Requires special attention from team involved. If needed from higher ups.
Red: Some aspect of the project has fallen behind or encountered major setback or is over budget
How to move R to G: Have a plan on paper, get a buy in, and get it approved. Once everyone agrees to the new set of parameters then move it to G from R.
Some teams move G to Y or R to get feedback from upper management so that they can get their expertise involved to get it done.

Project management interview questions & answers - Part I

Big Data Basics

NoSql:
  1. Data is highly unstructured.
  2. Doesn't follow stringent structure of RDBMS enabling speed and agility. 
  3. DBs are distributed and data can be distributed across multiple nodes and servers. 
  4. Allows for horizontal scaling: As the data grows add more nodes without impacting performance.
Big Data: 
  1. Big Data refers to large collection of data (that may be structured, unstructured or semi structured) that expands so quickly that it is difficult to manage with regular database or statistical tools.
  2. HDFS does not offer native support for security and authentication.
  3. Cluster has nodes

Hadoop v/s conventional DB:

Hadoop:
  1. Data is distributed across many nodes and processing
  2. Write once, read many. Once you write the data, you can delete it but can't modify it.
  3. Archival data: Telephonic call or transaction data
  4. Doesn't support SQL at all.
  5. It is an ecosystem of tools, technologies, and platforms.
  6. Runs on many commodity H/W and uses commodity S/W.
  7. Supports Hbase that is a NoSQL distributed DB.

Conventional DB:
  1. Conceptually all data sits in one server/database.
  2. Data can be modified.
  3. Support SQL


Hadoop layers:
  1. Bottom layer/Layer 1: Commodity Cluster Hardware
  2. Middle layer/Hadoop Layer/Layer 2: MapReduce, HDFS
  3. Top layer/Tools layer/Layer 3: RHadoop, Mahout, Hive, Pig, HBase, Sqoop
  4. RHadoop: Supports statistical language R
  5. Mahout: Machine learning
  6. Hive/Pig: NoSQL
  7. Sqoop: Getting data into and out of the Hadoop file system

Advantages:
1. Scalable
2. Cost effective in terms of processing large volumes of data.

=== Hive ===

  1. It provides SQL intellect so that users can write such queries called as HQL to extract data from hadoop.
  2. These SQL queries are converted to MapReduce queries. These queries in turn will communicate with HDFS.
  3. Great platform to write SQL writes to interact with HDFS.
  4. Not RDMS, or OLTP or real time updates or queries 
  5. Nice features:
    1. Supports different file formats like sequence/text/avro/orc/rc file. 
    2. Metadata gets stored in RDBMS
    3. Provides lots of compression techniques. 
    4. SQL queries are converted into MapReduce or tez or spark jobs. 
    5. UDF can include mapreduce scripts can be plugged 
    6. Specalized joins helps improve query function


Hive v/s RDBMS:
Hive:

  1. Enforce schema on Read and not on write. So you can write any kind of data till you read it. 
  2. Supports storage of 100PetaBytes of data.
  3. Doesn't support OLTP
RDBMS:

  1. Schema on Write. Won't let insert any data if its out of schema. 
  2. Allows storage of around 10PB of data. 
  3. Support OLTP
Impala:

  1. It is not mapreduce
  2. It is Massively Parallel Processing engine on top of Hadoop to query and analyze the data sets. 
  3. Utilizes Hive metastore to store table structure
  4. With the help of external tables, data resides in the Hadoop file system and structure in the metastore.
  5. Popular for Data scientists and analysts. 


Hive v/s Pig v/s Spark
Hive:

  1. Gives non-programmers ability to query and analyze Hadoop DBs
  2. Abstraction layer on top of Hadoop
  3. Batch oriented framework
  4. Useful for structured data. 
  5. Users can use SQL like interface to interact with backend Hadoop platform. 
  6. Supports:
    1. Batch query processing: For huge datasets. 
    2. Interactive query processing: For real time data processing. 
  7. Hive queries get converted into MapReduce jobs. 
  8. Predefined or UDF(User Defined Functions) can be used to perform certain action. 
  9. In hive: 
    1. select * will create a fetch job but not map reduce
    2. Aggregation functions like min, max, etc will create a map reduce job. 
Pig:
  1. Requires some programming knowledge to query and extract the data. 
  2. Abstraction layer on top of Hadoop
  3. Batch oriented framework. 
  4. Useful for structured, semi-structured, and unstructured data. 
  5. Pig has 2 parts: Pig Latin and Pig runtime. 
    1. Pig runtime converts the job from Pig to MapReduce
  6. Popular amongst data engineers
Spark: 
  1. In memory processing, you need to know java to utilize spark. 
  2. Faster but is low level since it requires coding knowledge.
  3. Useful for structured, semi-structured, and unstructured data. 
Decision making between Hive, Pig, Spark
  1. If you have unstructured data then go with Pig or Spark. 
  2. If you have structured data then go with Hive and load the data into Hive. 
  3. If you want faster processing go with Spark. 
  4. If you are fine with waiting few hours then go with Pig or Hive. 
  5. If you have technical knowledge then go with Spark -> Pig -> Hive. 
Few notes:
  1. Solr: Elastic search tool. Searches for words within documents. 
  2. Sqoop is used to import data into Hadoop. Pig is used to process that data. 
  3. Hbase: column family NoSql DB

NoSQL

NoSQL Data models: key-value  Aggregate model.  key or id is used to get the data.  Lookup is based on the key.   document Aggre...