Find a Salary negotiation coach to negotiate with Meta, Google, etc. Don’t leave thousands on the table.

Given AI's long-term strategic impact, I believe foundational knowledge of AI is essential for any PM aiming to drive sustained product success. I focus on three core learning themes for preparation: 1. Learning ML Concepts (via focused online courses/certifications): You'll need to learn the basic science behind AI. This means understanding core Machine Learning concepts - what a model is, how it 'learns' from data (training), and the difference between giving it labeled examples versus letting it find patterns on its own. You don't need to code it, but you must know how it works to define what's possible. 2. Practically Driving Business Value with AI (via identifying side projects, Capstone or even opportunities at your current company): Focus on how AI can deliver real business results. This means identifying opportunities where AI can directly increase efficiency, reduce operational costs, or significantly enhance the speed and quality of the user experience beyond what standard software can do. 3. Designing for Uncertainty (via focused online material): You must learn to design for failure. Traditional software either works or crashes, but AI is always 'sort of right.' The PM's job is to design the product experience to manage user expectations, clearly communicate when the AI might be wrong, and build reliable backup plans (like a human review) to maintain user trust.

The time for preparation could depend on a lot of factors and there is no one size fits all solution. Are you a student or working professional? Is this your first job or a job switch? What is your problem solving style? How comfortable are you in coding within a time period? What is the format of the interview? Generally, a full time preparation takes 2-3 months while a part time preparation could long for 5-6 months. Instead of a generic timeline, validate your personal readiness based on your specific case. There is no single right answer.

1. Behavioural / Leadership: People leadership (mentoring engineers, supporting promotions, building culture), Conflict resolution (approaching conflicts with empathy and objectivity), Stakeholder management (bridging engineering and business), Data-driven decision making, Scaling leadership. 2. System Design: Problem framing, High-level architecture, Trade-offs, Evolution over time. 3. Coding / Technical: Baseline coding ability, Algorithmic thinking, Code review mindset, Practicality over cleverness, Breadth of exposure. 4. Project Retrospective / Learning: Outcome clarity, Planning rigour, Execution ownership, Metrics & impact. 5. Leadership Stories: Developing Others as Leaders, Leading Through Change, Conflict Management, High-Stakes Decisions with Limited Info.

• ability to design end-to-end data pipelines • understanding of ETL/ELT approaches • SQL and schema design • OLTP vs OLAP • data warehouse / lake concepts • handling of batch vs streaming • experience with tools/platforms like BigQuery, Snowflake, Databricks, Spark, Kafka • thinking around data quality, deduplication, late data, backfills, and observability

1. Don't limit yourself to just 1 library if you've never used other Python ML libraries. For example, if you only used Tensorflow consider adding Pytorch and other ML libraries to your resume. 2. If you're pivoting from a non-ML role, work on a ML project and add that to your resume. Emphasize how much you worked with ML in past roles. 3. Include projects with LLMs and Generative AI tech in case your past experience is just regular ML or Deep Learning.

The best Strategy & Operations resumes don't just list what you owned, they show the impact of the connective tissue between functions. Hiring managers for these roles are looking for someone who can hold complexity without losing the thread of WHY we're doing something, and what impact we're trying to have. Lead with the outcomes you drove across the organization, not just within your lane, and make it obvious that you've operated where there was no playbook.