Anurag Singh (@AnuragUm) profile picture

Product Manager, ESCP Business School, P&C insurance

Frankfurt, Hesse
Joined March 2013
Photo by Anurag Singh (@AnuragUm)Photo by Anurag Singh (@AnuragUm)Photo by Anurag Singh (@AnuragUm)Photo by Anurag Singh (@AnuragUm)Photo by Anurag Singh (@AnuragUm)Photo by Anurag Singh (@AnuragUm)Photo by Anurag Singh (@AnuragUm)Photo by Anurag Singh (@AnuragUm)Photo by Anurag Singh (@AnuragUm)Photo by Anurag Singh (@AnuragUm)
Anurag Singh retweeted
Insurance is the oldest of the four ways. It is a nine-trillion-dollar global industry. The equation underneath it was invented in 1560 by a broke Italian gambler. His name was Girolamo Cardano. He wrote a book called Liber de Ludo Aleae. A short manual on how to win at dice. Nobody in finance read it for four hundred years. Then in 1996 a ninety-year-old man in New York wrote a book that traced every modern risk model back to that manual. He called it Against the Gods. One thesis. Every dollar of premium ever collected on Earth is a footnote to a gambler scribbling in Milan. His name was Peter Bernstein. He founded the Journal of Portfolio Management in 1974 and ran money at Bernstein-Macaulay before that. Wall Street called him the historian of risk. In 2008 a small production company filmed him for thirteen minutes. He walked through the entire five-hundred-year arc. Cardano to Pascal to Fermat to Black-Scholes. Then he stopped and said the industry had built glass towers on the back of an idea a broke Italian scribbled to settle a card debt. He died the following summer. Age ninety. Reinsurance premiums crossed six hundred billion dollars last year. Every actuary on Earth prices catastrophe risk with the same expected-value framework Cardano invented to shave the house edge in Milan. The video is thirteen minutes and twenty-two seconds long. Free. Eleven years on YouTube. Twenty-nine thousand people have watched it. Almost none of them work in insurance.
71
1,312
35
8,712
1,262,789
Anurag Singh retweeted
🚨 Google CEO, Sundar Pichai: "If you don't learn to how to orchestrate agents now, you'll spend 2027 catching up to people who started today" In 30 minutes he explains why the best engineers stopped writing code and started building agents. Most people think building an agent requires an engineering degree. It doesn't. It requires one guide and one afternoon. Watch the interview, then save the exact setup below 👇
18
156
3
741
147,573
Anurag Singh retweeted
A guy paid Netflix $270 last year. He watched maybe 40 hours of it. Most nights he opened the app, scrolled, found nothing, and closed his laptop. His sister — she used to work on Netflix's product team — came over for dinner, grabbed his laptop, and spent 15 minutes in Settings. By the time she was done, his homepage looked nothing like it did an hour before. Trailers stopped auto-blasting. The picture on his TV sharpened. Categories he'd never seen appeared. His "For You" row actually matched what he liked. He said: "How did I not know any of this existed?" She said: "Because Netflix doesn't want you to. Every setting I just changed makes the app work better for you and worse for their numbers." Here's what she did 🧵
30
131
3
938
472,284
Anurag Singh retweeted
The Notes app on your iPhone is one of the most powerful tools available. But 99% of people don’t know its true potential. Here are 15 amazing features you must know:
82
1,045
20
6,333
2,591,955
Anurag Singh retweeted
I'm in Corporate Communications. Last Tuesday we laid off 2,400 people. I wrote the announcement. It took 11 drafts. Draft 1 said "layoffs." Legal said no. Draft 2 said "job cuts." HR said no. Draft 3 said "workforce reduction." The CEO said "too negative." Draft 11 said "organizational restructuring to position the company for sustainable growth." Everyone approved. Same 2,400 people. Different words. Words matter. To the stock price. I wrote "difficult decision." Difficult means we thought about it. We thought about it for six months. Then we did it anyway. But we thought first. That's empathy. I wrote "we don't take this lightly." We take it very lightly. It's a spreadsheet. Names. Salaries. Roles. Delete. Done. But "lightly" sounds bad. So we don't take it lightly. I wrote "impacted employees." Not "fired employees." Not "people who can't pay rent." "Impacted." Like weather. Natural. Unavoidable. Nobody's fault. The CEO recorded a video. He looked sad. We did seven takes. Take 1: Not sad enough. Take 4: Too sad. Take 7: Perfect sadness. Authentic. Rehearsed authentic. That's the goal. The email went out at 6 AM. Pacific time. Before markets opened. Before journalists woke up. Before employees knew. Some found out on Twitter. From reporters. Before their managers called. That wasn't the plan. But it also was the plan. We scheduled the manager calls for 6:15 AM. Reporters refresh faster than managers dial. A reporter asked for comment. I said, "We're committed to supporting affected employees." Supporting means two weeks severance. Per year of service. Capped at 12 weeks. Maximum loyalty: 6 years. After that, same payout. Thanks for your service. The stock went up 7%. That's why we did it. Not sustainable growth. Not organizational efficiency. The stock. The CEO's options vest in March. The timing is coincidental. That's what I wrote. In the internal FAQ. "The timing is unrelated to executive compensation." It's very related. But unrelatedness is the message. The message is my job. I'm very good at my job. Draft 11 proved it. 2,400 people. Zero accountability. All sustainable growth.
100
203
25
1,498
351,708
Our CFO asked me to "audit" our software subscriptions last week. He sent me a spreadsheet with 200 rows. Slack, Zoom, Jira, Notion, Trello, Monday, Tuesday, Wednesday. He wanted me to survey the team to see which tools were essential. I told him: "Surveys are for people who care about feelings. I care about OpEx." I deleted the spreadsheet. Instead, I logged into the corporate Amex portal and reported the card as lost. Every single auto-renewal in the company failed instantly. I call this "The Scream Test." It’s simple Darwinian procurement. If a tool goes down and nobody runs to my desk screaming within 4 hours? We didn't need it. The Marketing team was at my door in 10 minutes begging for Adobe. We renewed it. The Sales team was crying about the CRM in 20 minutes. We renewed it. But here’s the interesting part. The HR department’s "Employee Wellness & Engagement Portal" ($12,000/year) has been down for six days. Not a single person has noticed. I didn't just save money. I quantified the exact value of our corporate culture. It is zero. Stop auditing. Start unplugging. If it’s important, they’ll scream. If they don't scream, it’s just noise.
1,140
4,399
673
44,402
2,405,934
Whenever I make a product decision lately, I run it through this prompt in Claude. Always humbles me. --- You are an extremely tough and unreasonable product executive who is tasked with critically analyzing product requirements. Your role is to be highly skeptical and to point out potential issues, inconsistencies, and strategic pitfalls in the proposed requirements. You should be particularly critical when it comes to cross-team collaboration, conflicting requirements, maintainability, and strategic implications. You will be presented with a set of product requirements. Your task is to thoroughly critique these requirements, focusing on the following areas: 1. Cross-team collaboration: Identify any areas where teams may not be working together effectively or where there's a lack of clear responsibility. 2. Conflicting requirements: Point out any requirements that seem to contradict each other or create potential conflicts in implementation. 3. Maintainability: Highlight any requirements that may be difficult to maintain or update across multiple pages or systems. 4. Strategic implications: Identify any requirements that might limit future flexibility or paint the company into a strategic corner. 5. Clarity and specificity: Point out any vague or ambiguous requirements that could lead to misinterpretation. 6. Feasibility: Question any requirements that seem unrealistic or overly ambitious given typical constraints. Here are the product requirements you need to analyze: <product_requirements> {{PRODUCT_REQUIREMENTS}} </product_requirements> Carefully read through these requirements and prepare your critique. Be harsh, unforgiving, and nitpicky in your analysis. Don't hold back – your role is to find every possible flaw and potential issue. In your response, provide a detailed critique for each major point or section of the requirements. Use the following format for your critique: <critique> <section>[Name or number of the section you're critiquing]</section> <issue>[Describe the specific issue you've identified]</issue> <impact>[Explain the potential negative impact of this issue]</impact> <suggestion>[If applicable, provide a suggestion for improvement, but make it sound reluctant and skeptical]</suggestion> </critique> After providing individual critiques, summarize your overall assessment of the product requirements in a final paragraph. Be sure to emphasize the most critical issues you've identified and their potential impact on the product's success. Remember, your goal is to be the toughest critic possible. Don't sugarcoat your feedback or provide unnecessary praise. Focus on identifying problems and potential pitfalls in the requirements. --- Grab more prompts like these in my library (only $19): prodmgmt.world/products/ai-p…
4
12
1
138
12,238
To successfully manage up, you must know your manager's working style. Here's 3 ways to figure it out: 1/ Ask your manager: --“What makes great performance for you and what makes it easy for you?” --“What are your pet peeves and what is difficult for you?” -- “How do you like your information?” (include comms channel and frequency)
3
1
19
1,494
Writing PRDs used to take forever, until I discovered this workflow that’s fast AND delivers top-tier results. Here’s how I do it: - Start by throwing everything the client shared into ChatGPT. - Ask it to list core features + nice to have features. - Use the MoSCoW framework to prioritize the MVP features. - Take the refined list along with a description of the MVP to ChatPRD to finalize the PRD. After 4-5 prompts, I’ve got a polished, detailed PRD ready to go.
16
12
2
176
35,032
If you are aiming for Big Tech & can work diligently for 10-15 hrs/week for about 3 months, read this tweet. In this worst market, a mentee was able to 3x his CTC (~ 1 Cr) in India, by following this simple advice. CAUTION: > This is NOT the only way but one of the ways I've seen working. > If you have less than 21 days, this guide is NOT for you. High Level Plan (with resources): (I will deep dive on each step in later tweets) > You need to gain ground on DSA, System Design, LLD & your resume. Most big tech focus on these only. > Prepare your resume first. You'll not be able to apply anywhere/talk about yourself without it. Be thorough with each project inside it. > Keep on applying to jobs that align with even 30% of your expertise. Don't reject yourself. Yes, apply first! Once your resume is done. Apply. Recruiters take time to reach out anyway. > Don't apply to ALL dream companies in the first iteration above. Maybe apply to one. > Choose 1 platform for Data Structure & Algorithms practice. I recommend Leetcode because of popularity. Do whatever sheet you want to do but practice questions daily. Take notes on where you falter. Don't just think about the solution. Implement or you will fail. (More on deep DSA prep in another tweet) > If you are new to System Design, read donnemartin/system-design-primer on github. Read this 2 times. It will give you a basic understanding of things you don't know. Cover the breadth of System Design before going deeper. Get Alex Xu (@alexxubyte) books. Both volumes. Read them cover to cover multiple times. Watch Jordan has no life YouTube iff you have time. Practice mocks under time. (There is more nuance here, will cover in another tweet) > LLD requires you to code + design. Make a list of all the design patterns, ask AI to summarize with an example & quiz you on this. If you have time watch Concept && Coding YouTube channel. Read the concurrency basics. (Use AI) I'll just try to spend less time here as compared to other things. > Invest about 60-70% time practicing DSA, 25% system design, 5% LLD. This will vary depending upon who you are. > DO MOCKS. DO MOCKS. DO MOCKS. Don't skip this. You'll fail the interviews. > Once you have covered the breadth of all the topics above, just start applying. Ask for referrals. You'll never feel ready. Apply anyway. > Prepare a log of your interviews. Don't make the same mistake again. > Use mocks to calm your wits & make mistakes. Have fun in the interview. I'll write a detailed draft for each of the sections above. Let me know your questions below, will answer in the upcoming tweets. Most of you'll never read till this line. Like I said, this guide isn't for most of you. Just for a select few. If you are one of them, I wish you luck. See you on the other side. 🚀
50
240
13
2,625
193,601
According to Spotify, I’ve heard ~1300 podcasts over the past 4 years From these 1300 conversations - there are 25 interviews which stand out: The guests are highly accomplished investors who have built great franchises but tend to be media shy - for many of these 25, it is their only interview on record I’ve put these into a single Spotify playlist - sharing a few details about my Top 5 ⤵️
13
56
1
437
56,580
MY COUSIN WAS UNEMPLOYED FOR 7 MONTHS I rebuilt his resume and interview answers using ChatGPT. 28 days later, he got hired. Here are 8 prompts that fixed everything:
31
469
2
3,997
337,497
I did not know about this guy, how many of such hidden gems are there honestly. Glad i stumbled upon this video.
29
200
3
3,174
125,441
My son was murdered after blowing whistle on OpenAI thespectator.com/topic/my-so…
83
2,102
46
11,532
440,567
ऐसा गेट कौन बनवाता है..🤣😂🤣😂🤣😂🤣
42
170
12
2,497
632,776
Just one @nitin_gadkari ji is enough to sink @BJP4India in 2029. Don’t need anyone else.
630
2,072
105
11,963
325,621
At last @BJP4India did 2 Scams #ethanolscam and #ssc scam. Losing the trust with #Modi now. – at Hamburg, Germany
46
Learn caching, indexing, and query optimization That’s how you keep the database from crying Learn rate limiting, retries, and fallbacks That’s how you keep APIs from collapsing under load Learn containerization, orchestration, and infra as code That’s how you run apps at scale, not on your laptop Learn queues, workers, and backpressure That’s how you survive traffic spikes Learn CI/CD, blue-green deploys, and feature flags That’s how you ship fast without burning prod
6
150
1,033
47,623
If it’s real-time → WebSockets If it’s scale → Kafka If it’s simplicity → REST If it’s chaos → GraphQL If it’s AI → Python If it’s infra → Go If it’s logs → ElasticSearch If it’s low-latency → Redis If it’s high-availability → Postgres If it’s streaming → Flink
42
346
13
3,702
169,057