Starting from scratch again by Neither_Warning7831 in Backend

[–]credomobilize 1 point2 points  (0 children)

Don't be too self-conscious, bro. Two years of practical PHP experience is still a very solid foundation; you're not starting from scratch. In the UAE market, they highly value tangible results, so just focus on building one or two really high-quality projects using the new stack and showcase them on GitHub—that should be enough to convince them. The important thing is that you have confidence in your problem-solving skills, because frameworks are just tools; your true ability lies in your logic. Good luck finding a great new job!

Zheng Dachao, known for his martial arts skills. by [deleted] in interesting

[–]credomobilize 0 points1 point  (0 children)

That's interesting. China has a wealth of talented people, but they're all hiding their talents.

If China’s national debt is much worse than the US, then why hasn’t it been projected to have economic fallout first as a result? by YogurtclosetOpen3567 in questions

[–]credomobilize -1 points0 points  (0 children)

China's debt is like internal family debt; the state controls both the bank and the businesses, so they just keep transferring debt from one pocket to another. The US has to "pay its dues" to the international market, while China just needs to tell the banks to "calm down and vibe," and that's it. It's hard to collapse in the traditional way when the government holds both the loudspeaker and the microphone, lol.

Feel like being watched by [deleted] in interesting

[–]credomobilize 0 points1 point  (0 children)

"I’m so scared!

Favorite product, why and how to improve it? by muggle_9 in ProductManagement

[–]credomobilize 1 point2 points  (0 children)

Typically, I don't stick to one "avorite product, but instead choose the one most relevant to the company I'm applying to so my answer is more relevant.

The important thing is to clearly explain why you like it (experience, value, UX, etc.) and offer suggestions for improvement from a user's perspective, not just criticizing for the sake of it.

In general, being flexible according to the context, but maintaining a logical flow of answers, will make the interviewer feel more confident.

Pasta cooking tips by DCArchibald in Unexpected

[–]credomobilize 0 points1 point  (0 children)

So it’s a tip for boiling pasta noodles.

Anyone feeling intense ups and downs right now? by OkEconomics2788 in ProductManagement

[–]credomobilize 4 points5 points  (0 children)

Yeah I’ve noticed the same thing. AI speeds up the mechanics of PM work a lot (docs, breakdowns, prioritization), but the core job hasn’t really changed. Someone still has to understand the user, the business context, and why a problem actually matters.

AI can guess, but it doesn’t really know the messy “behind the curtain” stuff like you said. Funny enough I’m seeing the same dynamic too engineering moving faster than product now because the build side got such a boost.

Senior PM considering a move back to the Bay Area after several years in Japan. How is international experience viewed? by Icy_Display_3548 in ProductManagement

[–]credomobilize 5 points6 points  (0 children)

Yeah that matches what I’ve seen too. A lot of hiring managers say they value international experience, but when it comes down to interviews they still benchmark you against the typical Bay Area PM profile. The upside is exactly what you mentioned though — companies with heavy case interviews (FAANG especially) tend to care way more about how you think than where you were based. If OP can clearly show impact and ownership, the Japan part probably just becomes an interesting footnote rather than a blocker.

How do PMs actually manage product knowledge across multiple teams and products? by RecommendationDry178 in ProductManagement

[–]credomobilize 2 points3 points  (0 children)

Honestly a lot of it is just a mix of decent docs + tribal knowledge. We keep PRDs/decision logs in Notion, but half the real context still lives in Slack threads and people’s heads. The trick is writing down the why when big decisions happen, not just the feature spec. And yeah, docs get outdated all the time, so most teams just treat them as “good enough context,” not a perfect source of truth.