Gunasheelan G, an Unqork Developer at LTM, has been creating with Unqork since 2023. Over the past three and a half years, he has achieved both his Certified Unqork Developer certification and Unqork Subject Matter Expert (SME) status. He is now among the top 10 all-time contributors to the Unqork Community.
What development experience did you have before discovering Unqork?
Before becoming an Unqork Creator, I completed internships in JavaScript and front-end HTML and CSS. During that time, I had the opportunity to build a few proofs of concept (POCs). Three and a half years ago, I got my first professional job, and that is when I started my journey with Unqork.
How long did it take you to start building applications in Unqork?
With the help of managers and colleagues, I was able to learn quickly. The Unqork Community also helped me get up to speed. Within three to five months, I had already started building applications independently with Unqork, including modules, workflows, and components.
Tell us about the most exciting solution you have built with Unqork.
The most exciting solution so far has been the work I have done on a broker portal that enables users to create and renew insurance policies. Our insurance client serves multiple markets, so for every onboarding event, we have to exclude markets that are not relevant.
To minimize development work, we decided to build that logic dynamically using a data table that serves as a data collection and handles all inclusions and exclusions across markets. Not only did this save us development time up front, but it also makes it much easier to onboard new markets.
Does the ability to go so quickly from ideation to working prototype change the way you collaborate with business partners?
Compared to the custom development projects I have worked on, Unqork offers a much smoother experience. It allows you to develop client requirements quickly, share them with the business team, and receive immediate feedback.
This helps us move faster and provides opportunities to incorporate enhancements the team might not have considered during initial requirements gathering.
Does Unqork’s architecture make it easier to embed security and governance during builds?
Yes, Unqork definitely simplifies these processes. It manages underlying security features such as Role-Based Access Control (RBAC), so by configuring the page correctly, you ensure that only authorized individuals can access it. All the logic stays on the server side, which means we don’t need to do much extra work — just follow the best practices.
Why did you start contributing to the Unqork Community?
In my early days using Unqork, I often visited the Community to find solutions. I frequently encountered multiple people offering different solutions for the same use case. Each person had their own perspective based on their requirements. This was very helpful and improved my logical thinking.
Has earning Subject Matter Expert status helped you in your career?
Yes, definitely. When I earned badges and shared them on LinkedIn, my teammates and manager reshared many of my posts. I also made new connections on LinkedIn, expanding my network. Most people in the Unqork Community know my name and see me as a Subject Matter Expert, and that has been very helpful in my career.
Have you found that the ability to create POCs and test solutions in the Unqork training environment sandbox enhances your ability to collaborate with other members of the Unqork Community?
Yes, that’s really helpful. For example, if you were working in Java, you would need to share the code. Then, they would have to download it and run it on their system, which requires a lot of effort. Sometimes, the logic works in your system but not in theirs.
With Unqork, you only need to share the UI link. Anyone in the community can click the URL and quickly see the logic on the page.
Do you have any advice or best practices you’d like to share with other Creators?
First, I recommend that new Creators follow all the documentation and best practices as they get started.
I also suggest keeping all business logic within the server-side execution modules to better control anonymous user access and reduce execution time. This means using UI components only for the front end.
Also, remember that if you encounter a problem, such as an error message, there may be multiple solutions. Try to resolve the issue with the fewest components and operators possible. And don’t forget, you can always check the Unqork Community. Someone may have already posted a helpful solution to save you time.