Taking the path in computer science means studying about how computer works, observing how computer works, and finally, making computer work as expected. There are lots of field of expertise when it comes to computer science, and one of them is web technologies.

In a short glimpse, web technologies can be divided into two major part : front-end and back-end. Front-end deals on how the end user see and interact with the web through web browser, while back-end deals on everything that's happening behind the user side, like server routing, database management, DevOps, and lots of other things. Both are major component, goes hand-in-hand, can't be separated, and both deals on almost very distinct stuffs.

Job Hunting!!!

At the time I'm writing this article, I'm a part-time front-end web developer at eftax co.Ltd, in which the headquarters located in Osaka, Japan. I am developing the web application using React.js as the main framework. I got the information from alumni that already work there, and even though I felt that I lacked the skill, I still did it anyway. It was a #YOLO moment, honestly.

As I'm striving to become a full-stack web developer, acing both back-end and front-end is a must. When I first applied for the job, I was and still pretty confident with my back-end skill, and also aware on how bad I was on front-end. Back then I only know back-end Javascript using Node.js. I felt that it was a bad thing and could be my weakness, so I changed my focus to gather experience on learning to become a good front-end web developer.

Before this, I had an experience having internship as a back-end (eventually became full-stack) web developer at Chatbiz.id, and it was the first time where I tried React.js. I did learn a lot, especially React.js, that I wanted to develop my skills even further on this framework.

I saw the requirements to apply was to be able using React.js framework. And so I studied React.js while waiting for the notification, made several side projects, and watched lots of tutorial videos.

After several weeks, I got an email of invitation for interview. I was really surprised that time. And so, my next preparations involved practicing myself on common interview questions. As I applied for a front-end developer, I also practiced several questions about front-end technologies and workflow (i.e. git, agile scrum, how javascript works). The hardest part was to keep my composure, not to panic on my occasional stuttering. It gave some pressure as the interview was held in full English.

Eventually, I made it. I got accepted. And here is where things started.

Working!!!

When I first joined, there was a lacking on boarding process, which made me pretty confused at first. This encouraged me to be the active actor, the one who started asking questions about the workflow and the technical aspects. I was given a list of the technology stack we're using and also the brief explanation on the current project we're working on.

Several days later, there was a SCRUM meeting in which we talked about the goals from the current and for next sprint. I was encouraged to take a task, as learning by doing projects is one of the most effective way to learn new things. And so, I took one task that I first looked as a small task, which turned into a big task later on.

About Japanese Working Environment

If you've heard that Japanese work ethics are hard and difficult, then I can confirm that statement because it also applies here. Working with efficiency and effective is our main guidelines. As a college student, all the tolerance such as revision and late are no more. Working on professional environment means you need to be professional on working with your task.

Our Daily Working Life

Working in a project which consists of several team members requires a good communication skill and awareness of others. Applying Agile SCRUM as our main workflow, each one of us take one or more available tasks to work on. The task needs to be done/finished in a single sprint, which in here spans for 2 weeks. In case it's not finished, it can be brought to the next sprint. In case you finish it earlier, then by approval you can take another task from the list.

As a front-end web developer, our main job is to implement the design that given by the UI/UX team. The designs are distributed in Figma for easier access. But it doesn't just stop there. After we implement the design, we need to make sure that every element works as expected, as we need to work on state management of the features. When it's done, then it's time for creating merge request (or pull request), getting reviews, applying reviews if any, and do the review-apply cycle until the team approves. After that, we're allowed to take another task. There is a cycle the goes seemingly infinitely.

On a bigger frame, there are milestones that addresses the project as a whole. For example : MVP (Minimum Viable Product) is done on July 2020. We use this as a constraint to never let a single task take too much time for it to be completed.

What I Get Here

Honestly, there are just so many things that I learned just from being a front-end web developer alone here. I can get to know on the proper best practices and maintaining the quality of my code, while also getting more experience in using git version control.

Communicating with people overseas, embracing our diverse culture, and having fun at the end of the month. I was taught to work more professionally, bot individual and as a team member.

It was such a blast, and I'm deeply grateful that I got the chance to have this experience.

Thank you for reading!

Loading...

There will be awesome contents here

My First Part-Time Web Developer Experience