An Unqork Developer at LTM, Hari Priya S began her journey as a Creator in 2023. Since then, she has earned her Certified Unqork Creator certificate, and in 2025, she became one of the top contributors in the Unqork Community, answering more than 100 questions from her peers.
What development experience did you have before discovering Unqork?
I started my career with an internship on the Java stack, gaining hands-on experience on a project that used Java, Spring Boot, SQL, HTML, and more. This provided a solid foundation for understanding backend logic, API development, and basic frontend structures.
Soon after beginning full-time work in 2023, I was assigned to a project built on Unqork. I was able to apply my existing knowledge, which made it easier to understand Unqork’s architecture and get up to speed quickly.
How long did it take you to start building applications in Unqork?
I began my journey by attending Unqork Boot Camp. Within a month, I gained a solid understanding of Unqork components and how they work together. After completing the Boot Camp, I started building small proofs of concept (PoCs). Meanwhile, I earned my Novice Configurator certificate. By then, in about two months, I was capable of developing requirements for our client.
Tell us about the most exciting solution you have built with Unqork.
I have worked on multiple applications within the insurance domain. The most interesting use case so far has been a broker portal that included end-to-end placement and a policy lifecycle based on that. Our goal was to make the entire process smoother and more efficient for the end user, from initiation and renewal through submission, binding, premium invoicing, policy issuance, and endorsement.
By consolidating all these aspects into a single application, we reduced manual effort and improved visibility across the entire lifecycle.
Does the ability to go so quickly from ideation to working prototype change the way you collaborate with business partners?
With Unqork, we don’t just discuss business requirements at a high level when talking with business partners. Instead, we can quickly turn requirements into a working proof of concept, sometimes in just a few hours or days. This allows us to demonstrate the PoC to the business, helping them clearly see how the final product will function.
They can then provide feedback immediately, which accelerates the development process. If the client suggests an enhancement, it’s very easy for us to accommodate that request.
Does Unqork’s architecture make it easier to embed security and governance during builds? How about managing security and governance post-deployment?
With Unqork, we can incorporate security into the application from the start. Unqork’s role-based access control (RBAC) also offers some unique features. For instance, we can apply RBAC at both the component and module levels. Regarding data protection, we ensure that only necessary data is stored, avoiding sensitive information.
If we need to make changes to an application, it is much easier and more secure with Unqork. There’s no need to analyze the code. We can quickly understand how a component is configured and then update it with minimal security risks.
Has earning Subject Matter Expert status helped you in your career?
Yes, definitely. I contribute regularly and have earned many badges for my participation. The leads I collaborate with appreciate my consistent input to the community, and it has positively influenced my other team members. I am now looking forward to earning my Subject Matter Expert badge soon.
Do you have any advice or best practices you’d like to share with other Creators?
First, when building an application, always keep performance in mind from the very beginning. This enhances the user experience and reduces future maintenance efforts. For example, you might need that component to perform better later. Getting it right the first time means you won’t have to reconfigure it later.
After completing a requirement, review it again to see if there are ways to optimize, such as removing unused or unnecessary components. You might also consider using parallel triggers instead of sequential triggers to improve efficiency and reduce execution time.
If you make changes to a module, it’s important to add notes in its version history. This helps the team quickly identify recent changes and revert if bugs appear. Remember to ensure error handling is consistent across all API modules. This makes debugging easier if any calls fail.
Always test frequently as you progress. Don’t wait until the entire requirement is finished. Regular testing helps catch errors early.
Most importantly, engage with the Unqork Community. It offers new ideas for common challenges, and sharing your insights can benefit other members, too.