From Telecommunications to Full Stack Product Engineering
A factual career timeline from Polban and Hacktiv8 to teaching, trading systems, business software, and Vidio.
My path into software engineering did not start with a computer science degree. It started in telecommunications at Politeknik Negeri Bandung.
That background still shapes how I think. A system is made of boundaries, signals, failure modes, and people who depend on it. Software gave me a faster medium for applying those ideas.
Telecommunications, 2017 to 2020
I studied Telecommunications Engineering at Polban from 2017 to 2020 and graduated with a 3.00 GPA. The program covered physical infrastructure and the logic used to move information reliably.
My final academic work became a published applied research paper. Publishing did not make me an expert, but it taught me to make a claim visible, connect it to evidence, and let other people inspect it.
In January and February 2020, I also worked as a Network Engineer Intern at Wave Communication. That short placement gave the classroom material an operational context.
An intensive move into software
From 2020 to 2021, I joined Hacktiv8's Full Stack JavaScript program. I completed it with a final score of 101.3 out of 105.
The important change was not learning one framework. It was learning to move through a full application:
- Translate a requirement into smaller behaviors.
- Model data.
- Build a server contract.
- Connect a client interface.
- Debug the whole path.
- Explain the decisions to another person.
The tools have changed since that program. The habit of tracing a system from intent to evidence remains.
Trading products, 2021 to 2022
I joined Samuel Sekuritas Indonesia as a Software Developer in April 2021. The role crossed several generations of product technology.
I worked on web applications with Next.js, NestJS, and TypeScript. I contributed to STAR mobile trading products on Android with Java and maintained iOS work written in Objective-C. I also worked with Linux and NGINX infrastructure.
Financial products made reliability concrete. A confusing state, missing update, or careless deployment is not an abstract code-quality issue. It affects a person making a financial decision.
I left Samuel Sekuritas in November 2022.
Teaching JavaScript, 2022 to 2025
In November 2022, I returned to Hacktiv8 as a JavaScript Instructor. I taught and mentored students through JavaScript, React, Vue, MongoDB, and related full-stack topics.
Teaching changed how I review code. A review is not only a list of defects. It should show the learner what to notice next time. Daily feedback, stand-ups, one-on-one discussions, grading, and curriculum work made communication part of engineering rather than an extra skill.
I also built automation around repeated teaching operations. The goal was not to remove judgment. It was to protect time for the parts where judgment mattered.
That role ended in December 2025.
Concurrent product work and continued study
I began working as a Software Developer at Harmoni Mitra Tekno in January 2025. The work spans practical business software across web and mobile surfaces.
Alongside professional work, I am pursuing a Bachelor of Computer Science at BINUS University, with graduation expected in December 2026. Studying while working creates a useful loop. Formal concepts can be tested against real product constraints, and work exposes questions worth studying more carefully.
Vidio, 2026 to present
In January 2026, I joined Vidio as a Full Stack Engineer in the Subscription and User team. The team uses test-driven development and pair programming.
At this scale, collaboration is part of the system. Tests preserve behavior, pair programming makes reasoning observable, and careful boundaries let many engineers change a product without every change becoming a gamble.
The thread through the timeline
The roles look different: network operations, a bootcamp, trading systems, instruction, HR software, and streaming. The thread is a preference for practical systems that people can understand and trust.
I am still learning how to build them well. The goal is not to collect more technologies. It is to become better at finding the important constraint, making the work visible, and leaving the next person with a clearer system.