Power User Spotlight: Rajat Sharma, Xceedance

What development experience did you have before discovering Unqork? 

My background was rooted in traditional development. I used JavaScript and other frontend technologies, and I was also involved in full-cycle development, from gathering requirements and building logic to creating frontend UI components and optimizing performance. 

So for me, Unqork was a natural evolution, because Unqork provides the speed and abstraction of a low-code platform, but also supports all the flexibility and architectural depth of traditional coding.

How long did it take you to start building applications in Unqork? 

Obviously, there’s a learning curve on any new system, but I was pleasantly surprised how fast I got up to speed. Within the first few weeks, I was able to create modules, set up workflows, and integrate APIs within my applications. And within a month, I was able to create POCs that I could leverage as part of larger solutions. 

Tell us about the most exciting solution you have built with Unqork. 

So far, the most exciting solution has been a streamlined workflow application that automated a complex, multi-step business process. The exciting part was how quickly I was able to create POCs, which I could then show the business. This gave us all a sense of the tangible progress we were making. 

Also, building a prototype quickly meant I could get feedback in real-time from the business, which allowed me to make continuous improvements and enhancements to the working prototype. 

Does the ability to go so quickly from ideation to working prototype change the way you collaborate with business partners? 

Yes, definitely. Usually, there’s a gap between the requirements you get from the business and what you perceive they need. With Unqork, I’m able to bridge the gap and take out a lot of the guesswork by quickly creating a prototype. I get visual clarity right away, and instead of focusing on the syntax of the platform, I am actually building the logic. 

This also helps build excitement with business partners. They feel like they are taking more ownership in the solution we’re building. This builds more trust in the fact that we’re building a good product with all the requirements they want. And ultimately, they get the solution they want faster and with less rework. 

Does Unqork’s architecture make it easier to embed security and governance during builds? How about managing security and governance post-deployment?

With the Unqork platform, security is very much embedded in your builds, which is not the case with traditional coding, where you have to build and manage a separate security layer. With Unqork, security is totally governed by the platform. And you can apply role-based access at the environment, workspace, module, or even the component level. 

And when it comes to data, we can also rely on schema validation to validate our data. And if we are submitting our data in the Unqork platform itself, the security of that transmission is handled by Unqork. 

The same is true for governance. With Unqork, we can track each and every action by a Creator or other users. Even disaster management is handled by the Unqork platform itself.

Why did you start contributing to the Unqork Community? 

First, I found it to be one of the best ways to learn, grow, and connect with other Creators around the world. Whenever I run into an issue, I just go to the community and check the related posts.

Then, because I got to learn so much from the Unqork community, I thought, why not give back to the community myself? That is really what community is all about. So, over time, contribution just became a habit and a passion. 

Has earning Subject Matter Expert status helped you in your career? 

Yes, it has definitely helped. First, it has built trust among my leadership team. And when my peers and manager heard about my SME status, they were genuinely very excited. I was seen as a go-to person to help with any challenges related to Unqork. Also, they liked it because it helped grow awareness of our expertise in Unqork space. 

Do you think 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. If someone asks how to do something, you can quickly try a solution yourself and validate it. Then, instead of writing out a solution in a message, all you have to do is share a link, and then they can see exactly how you did it and validate it themselves. This really helped in terms of collaboration. You both get on the same page much faster. 

Do you have any advice or best practices you’d like to share with other Creators? 

Yes, I have three pieces of advice to offer. 

First, for new Creators, I recommend using best practices throughout your configuration lifecycle. You will find that best practices are very well documented in the Unqork Documentation Hub. Not only will this make your configuration cleaner, it will also make your application more scalable and reusable down the road.

Second, try to be active in the Unqork Community, both by asking questions and sharing your own experience and the solutions you’ve found. It is a very vibrant community of Creators, and there is always someone ready to help. If it’s a really in-depth question about architecture that no one can help with, the people from the Unqork product team are continuously checking for open questions as well. 

Finally, I would say, keep on experimenting and trying new things. And based on that experience, provide Unqork feedback when you can, so they can keep improving the platform, whether that means writing an email to the support team or providing enhancement ideas via Unqork community.A new study from HFS Research, in collaboration with Unqork, exposes a striking paradox at the center of enterprise AI adoption: while 84% of organizations expect AI to reduce costs and 80% expect productivity gains, 43% report AI will create new technical debt.