Many people ask me, “datafox, what exactly do we talk about when I book a Coffee Chat with you?” It’s not just a one-way consultation; it’s a “stress test” for your career assumptions. Recently, I had a conversation with a student who is pursuing a master’s degree in the UK and considering returning to Taiwan for career development.

Below is a summary of our conversation’s highlights, along with my genuine perspectives on these topics.

1. Cross-Domain Career Transition: Don’t Project Others’ Scripts onto Yourself

In our conversation, we discussed the case of “medical background transitioning to AI” (which is actually a brilliant story from another friend, Iressa).

  • My Take: Career transition isn’t just about learning new tools; it’s about building an entirely different “skillset.”
  • Key Reminder: Many feel anxious looking at online success stories, but you must clearly distinguish: What are your core competencies? What is merely someone else’s halo? For example, my transition from finance to computer science relied on rebuilding my foundational logic, not just solving leetcode problems.

2. Demystifying the Google Interview Process: Facts Over Rumors

There are many misconceptions about Google’s internship interviews. In our chat, we clarified several key points:

  • Process Breakdown: From resume screening, HR behavioral interviews, online coding tests, to the most crucial Team Match.
  • Key to Getting Hired: Many believe that a phone call from a manager during the “Background Check” can determine acceptance. This is incorrect. At Google, your interview performance and fit with the team are central. Background checks are for verifying authenticity, not for replacing interview evaluations.
  • Internship Quality: I shared my experience participating in a “Generative AI Customer Service System” project at Cathay United Bank. The focus isn’t on the company’s reputation, but rather on whether you can clearly articulate your specific contributions (e.g., agent training or architecture optimization), instead of exaggerating.

3. Coding Interviews: Banning “Blind AI Use,” Not AI Itself

This is something I particularly emphasized in our conversation. We are in the age of AI, and interviewers, of course, know you’ll use tools.

  • The Real Test: Interviewers don’t care if you can write code; they care if you can explain time and space complexity and why you chose a particular algorithm.
  • Beware of Sycophantic Behavior: If, during preparation, you blindly ask AI for answers without contemplating the underlying reasoning, the moment the question is slightly altered in an interview, the breakdown in your logic will be the moment you’re out.

4. UK vs. Taiwan: The Harsh Reality of the Job Search Ecosystem

The interviewee shared the employment challenges faced by master’s graduates in the UK (such as his brother at Durham University).

  • Market Differences: The tech industry ecosystems in the UK and Taiwan are vastly different. Taiwan boasts strong hardware integration and emerging AI application demands (e.g., VCs’ desire for discerning technological innovation).
  • Networking: A Coffee Chat isn’t for obtaining a referral; it’s for gaining “first-hand information.” Proactively reaching out to alumni and understanding a team’s real pain points is far more effective than haphazardly scattering resumes on LinkedIn.

Want to Chat? If you also want a conversation that cuts to the chase and addresses pain points, feel free to book my Coffee Chat. But remember: bring your logic; I don’t entertain flattery, only genuine thought.