Here are the links to my curated collection of my past works for companies I've worked before.
Links are verified as of 10th August 2026 (certain links may be broken if content is archived)
I worked as a content developer to write weekly technical articles for their support knowledge base. We look through the support cases from their support backend, and identify issues faced by customers that have been resolved by our support staff to become topics for our articles. This would then create a knowledge base so that future similar cases that our support staff would encounter would be able to reference customers to directly, and reduce the overall calls coming in to our support.
Our articles are researched, reproduced which required trained familiarity with Esri products, written in certain templates for standardized style, tested by technical editors, and verified by a copy editor before publishing. I eventually transitioned to a copy editor from my content developer role, gatekeeping and ensuring that articles written by our content developers abide by our writing standards, and have passed all checks before being published on the support knowledge base.
Here are some of my sample work I've written as a content developer:
- How To: Download and install an Esri software ISO file
- How To: Turn on debug mode in logs for Drone2Map for ArcGIS
- Error: The network dataset has no edge elements. It may be unbuilt
- Error: WARNING 000564: Input feature 0: falls outside of output geometry domains
- Problem: Unable to save the settings of a hosted feature layer after enabling editing
- Problem: Analyzing a layer to be published as a feature service with the Sync capability causes an error
- FAQ: How is traffic data calculated in the ArcGIS Online World Traffic Service?
- FAQ: What are some best practices for raster storage?
In Digital Route, I was an embedded technical writer in several development teams, documenting whatever documentation changes that is required as they develop issues in their respective swimlanes. Adopting the scrum methodology of software development, I attended daily standups with the development teams, tracked ongoing development issues, identified if there were any documentation requirements to be made, communicated with developers and other relevant stakeholders (this can vary from the product owner to customer-facing implementors) to review and verify the documentation, and overseeing the publication of documentation to its latest state upon release.
Since most of my time there was documentation maintenance, it is quite difficult to showcase my documentation work done during my time at Digital Route for their range of Usage products (MediationZone, Usage Engine Private Edition, UsageCloud. However, there are occasions when I have to create new documentation for new features that were developed. Below is one such documentation that I've created to be added as part of the user manual for UsageCloud
I have also contributed documentation work to open source projects on GitHub.
- Issue: Docs: tutorial, write your first country pack
- Description: The project required a tutorial for creating country packs that are preset configurations that would populate foundational setups. Aside from writing the tutorial itself (in markdown) according to their contribution guidelines and style guide, the doc also had to be embedded to other pages in the repo and their doc site through their static site generator doc structure.
- PR: 362, 363
- Final Output: Write a country pack