The Things about Job Title

[My original post from linkedin https://www.linkedin.com/pulse/things-job-title-zan-kai-chong/%5D

Switching from the job title data scientist to machine learning engineer amuses a lot of my friends. They wondering since when I become a lecturer again (note : machine “learning”). Despite my wrongful explanation, I start thinking what is my real job title other than those words printed on my name cards.

Analytically, I should list down all my job functions. Then build the heat map or histogram from all the words in the description and then identify the common words by applying the max(count) or corr function. Okay, sounds right. Here we go.

First, I work on AWS platform. As a trustworthy power user, I stress-test the costly computing instance and provide my helpful IT support to new comers (lady is preferable). I also use EMR (very expensive computer clusters) like-a-boss occasionally for big data stuff. Occasionally, I speak AWS jargon as if I am real AWS engineer.

Okay. You saw the word “big data”. Of cause , I am (acting like) a big data engineer as I work on peta-ful (new word to describe peta bytes) data. These petaful data are our asset to track you. We may not be as good as Cambridge Analytica. But we know many things about you and what you did last weekend. The more you attach to your phone, the more we know you.

In short , it is fun to work in analytics company. Well, my real job title? I am wondering as well . Perhaps , I should just call myself “engineer“.

I was in a great self-involved until my civil engineer friends start mocking me with a photo.

Advertisements

Venturing into Data Science

After seven years of academy life at UTAR, I decided to move on to the data science industry to explore the opportunity in big data transformation.

It is a hard but necessary move to me. I will leave the full story to offline face to face discussion if our frequency and space-time are right.

Here are my observation after six months working in data science industry. Majority of Malaysia industries are business-driven entities — business comes first and research be the second (or last). Usually, R&D or r&D departments are hardly survive in the evolution (a.k.a company restructure / reorganization) considering the output are always less convincing in the board meeting. One of the common practice is to embedded the R element as part of the product development such that some tangible output are there.

Another interesting thing is, the term research varies a lot in industry. It can refer to operational research, product research, applied research, etc. Definitely it is not the research that allows you to sit down to for the whole month just to derive an elegant but less useful equation to them.

After all, I am the  latter type of person. I guess it gonna takes another few months before my boss realizes that I am working on a niche research topic instead of building the requested machine learning model.