A finance graduate turned software developer. Pursued 2 startup ideas together with 2 friends and failed miserably. The silver lining? Now I am a senior ruby developer, both an efficient contributor and enthusiastic leader/mentor for team.
- In this 7-mins talk, I laid out the cons, and then the pros, of using Rails to build an API. And voice my opinion why you should.
- Successfully mentored junior engineer without ruby experience to be a competent rails developer
- Designed from scratch and launched the Mekari Internal Billing system with a team comprising of 2 junior engineers in 2 months
- Lead a bilingual and distributed team, spanning 3 time zones and 3 islands, without any missed sprint commitments.
- Designed and shipped a full-cycle accounting integration to Jurnal in under 1 month.
- Maintain high standard of code coverage, ranging between 94% to 95%
- Led a team of 4 developers, with 3 of them juniors. Coached and mentored them to be an effective contributors to the team.
- Designed and delivered new version of student enrollment system with only a fresh-grad junior developer as the team member
- Initiated, conceptualized, and delivered internal notification system for student enrollment process 60% faster than scheduled by utilizing Slack channel
- Designed and Built an internal APIs that are responsible as attendance system and grading student scores that manage to be more scalable, modular, and efficient than the legacy versions.
Worked together with inhouse and outsource developers to develop University Management System and personally building email delivery API for internal use without an engineering lead in the team.
- Individually researched, designed, and developed Live online class feature using Zoom.us
- Build, implement, and document email delivery system API using Mandrill