At MIT there was a class that every EECS student had to take and most people hated, 6-UAT. I like to call it learn to speak for software engineers.
People disliked it for one of 2 reasons:
- The class is obvious and I'm not learning anything
- The class is bullshit and I don't agree with what it's teaching
In my case, this was my favorite class while at MIT, and it was the difference between passing all technical interviews and failing team match / culture fit and then just having an easy time at this cultural part of the interviews.
The main thing I learned is: American tech companies don't care about skill claims, claims about what you learned, what you can do, etc. Saying: I have 10 years of experience in C++ is close to useless at showing that you know how to code in C++. This is filtered and ignored. There is not even distrust, it's just background noise.
What matters the most is results, and you should always lead with results. No one will care about what tech stack you used, or what you learned (which is strange, given that job descriptions are usually focused on these types of requirements). They care about what was the result of the project. It is better to say: improved a database 5% in performance saving X amount of money in March 2025, than it is to say: worked on databases for X years using technologies A, B, C. The latter will get you rejected, the former will drive a conversation. Once you have the conversation you can answer about the stack or technology.
Specific facts carry the idea of reliability and expertise, even if the facts cannot be cross checked, while processes or learning (10 years of experience in X, etc), is ignored even if it can be proved and cross checked.
If you ever intend to rewrite your resume to apply to American companies, keep this in mind.
No comments:
Post a Comment