We sat down with Unqork Solutions Architect Rachel Moose to get a glimpse into her day-to-day and find out what makes Unqork unique.
Q: Can you start by telling us what you do at Unqork? What does your day-to-day look like?
Rachel: I’m a Solutions Architect at Unqork, and I’ve been with the company for five months now. I generally work on large scale projects and dedicate all of my focus on that one project. Right now, my day-to-day is spent building out an application for a financial services client.
When I first started this project, I did a lot of research into the various types of integrations that the client would use—a lot of these are integrations I’ve never worked with or even heard of before. As the project has gone on, we’re working on not only setting up these integrations but making sure that’s done in a sustainable way that makes sense for the architecture of the platform and the number of users.
Have you always been in the tech space? How did you find yourself at Unqork?
Before Unqork, I was an Integration Engineer for a company called Trustpilot. I was helping our enterprise customers utilize the Trustpilot API and serving as the technical point of contact for clients—I really became an expert on the Trustpilot API.
I found Unqork in a really serendipitous way, actually. An external recruiting company reached out to me, and it coincidentally happened to be a recruiting company that I used to work for. I started my career as a technical recruiter, and that was my first job ever.
It wasn’t a long period of time, but because it was the company I used to work for many years ago, I knew exactly what that recruiter was going through. So I listened to his pitch and I told him, “You know, I used to work for your company and I know how hard your job is. I’d be happy to hear more about this company you’re pitching.” Of course, that company turned out to be Unqork.
When he started talking about it, he told me that Unqork was looking for developers who didn’t want to code anymore. I was like, “Oh, that’s perfect, that’s exactly me.” I was happy at my old job, so I wasn’t going to leave it unless it was something I was really excited about. I took a chance and took an interview, and I just ended up loving the environment and everybody I spoke with. Unqork definitely gave me that excitement that made it worth exploring the opportunity.
How did your background as an Integrations Engineer translate into your current role at Unqork?
My experience with APIs at my previous job was the most helpful factor in learning Unqork, since it really is built off of API calls and making submissions to the database. I had a really solid understanding of REST APIs coming in, and I think that helped a lot.
Is there a particular project that you’re most proud of having worked on at Unqork?
When I was first starting out, I worked on a project for the Environmental Protection Department of New York. It was a really neat project because it was something that you could look up and know that you had contributed to it. The financial services project I’m on right now is really exciting, but I know I will never personally interact with it.
This Environmental Protection project was something I could Google and look at my work. It’s always kind of cool when you can send somebody something that you built and say, you know, “Look what I did!”
As someone who already identified as a developer who didn’t want to work with code, can you tell us your predictions for the use of no-code in the future? Do you have any advice for people looking to get started with no-code?
I love working with a no-code platform because I truly believe that that’s going to be the next big thing. It’s exciting to work somewhere that you really think is going to be the next big, recognizable name. It’s amazing to see it grow and see how many things we’re going to accomplish.
I really think it makes sense for all kinds of companies and enterprises to be moving to no-code. For anyone who’s interested in learning no-code, I guess I would prepare for how popular and it’s going to be. I think it’s important to prepare for the amount of future traction you’ll get with a new skill, and the different kinds of work it will give you access to a couple of years down the road.
To learn Unqork, you just have to get your feet wet. You have to dive into the platform, use it, and just completely immerse yourself by playing around with the platform. Look at examples, read through the Unqork resources, and watch videos. It’s very hands-on.
What do you think makes Unqork special?
I love my team. They’re brilliant, they’re diverse, and everybody brings a lot of different kinds of knowledge. I wouldn’t compare Unqork to anywhere else that I’ve worked before—it’s really different. It has a completely different energy, like we’re all in this together. We’re all working to make this company the best it can be and to make this product (and the applications that we’re building!) the best they can be. I’ve really enjoyed being a part of that.