Neelam Malaviya

I'm a dedicated professional with a passion for technologies and ecommerce. I'm bringing 4.5 years of experience into web development and project management. I pride myself on delivering high-quality outputs to my clients. It's been 4.5 years into the Shopify ecosystem. So I really, deeply understand how Shopify works, including its algorithms for new additions and everything. I'd like to tell you how I got into Shopify. Initially, I'm a computer engineer, and I started my career working as a business development executive. In that role, I was the bridge between my clients and the development team. I slowly started understanding how the technology works and how Shopify actually works. Due to that interest, it really helped me dive deeper into Shopify. Then I decided to make my career in Shopify. It's been almost 4 years working with Shopify, and I have around 6.5 years of experience in the technology industry. I'm a problem solver, and I take on challenges as part of my work. I really understand the context of a problem statement. So I try to understand it first, then make a plan, and decide how to make it functional.

So I would be very honest here. So it's been I have just used a tab in for my past two projects only. The reason was the project was already set up, which I just needed to redesign some of the components using the Talend CSS and Talend CSS already provides some reusable components like we're sorry, credentialing CSS. Right? So I don't have a deep knowledge about how to refactor using the Tailwind CSS, but I know how the basics work like using the CSS 3 and SASS. But, yeah, I know how Tailwind works.

In my past project, I worked closely with the Figma designers. They were designing the prototypes, and I was responsible for converting that Figma prototype into the liquid template. The reason we were very strict about the pixel-perfect design was because the client was very strict about it. We had to consider different devices, such as iOS devices, Android devices, laptops, and tablets. For example, we needed to take care of the Pixel 4 and 5. When converting the Figma prototypes into liquid, my first priority was to understand the component first. For instance, if there was a product we were designing, we needed to reuse that product's customer information, for example, in a collection or recommended section. I designed the snippet of that product card so that we could reuse it again and again, and we didn't need to rewrite the same code multiple times. This is how I practiced to avoid revisions.

To improve our time, I take the step to use this size so that we can easily minify the CSS, and also with Shopify, when designing web pages, we need to take care of the CSS and HTML part because, ultimately, this is the main thing. Whenever the pages load, CSS and JavaScript are the main things that take time. So, what I might practice is that I used to write by following the Bootstrap model every time because, for example, if it's a from-scratch project, I design the interface and try to use the same class for similar components instead of writing custom CSS every time. This way, it won't take time every time to load different CSS. And I try to make all the CSS in different files so that I can easily modify.

So, for the GitHub, it's been two years that I have been using it to manage the Shopify team especially. And I had an experience creating the shopping workflow for the Shopify team over the GitHub. So, for example, I'd like to give you an example. In my past project, we had four different stores with identical code for design and code. Everything was the same for all four stores, just the domain was different, for example, dotd, co.uk, au, etc. What best practice is, we just have to create a branch for different features, and it should be live on all four stores together. We created a workflow something like that. So, with the live thing, the master theme is already connected with all four stores, so we just don't need to push code to different stores instead we just need to push it and create a PR for merging with the master, or only once in a time. And, yeah, GitHub, I used to work with the GitHub desktop, which is very UI-friendly. And every time, I just didn't need to write commands for myself. So that's why I really love working with the Git desktop and GitHub.

Experience. Sorry. Okay. So, yeah, so liquid. So, liquid, according to my experience, is very similar to JavaScript because, ultimately, in Shopify, we are creating templates. Right? So, whenever this, in terms of the syntax, I would say it's also very easy. Like, we just need to take care of the curly braces and all. So, syntax is very easy, but I and it's like around 3, around 3.5 years that I have been working with liquid, especially before that, I was just working with HTML and CSS, and then I moved to JavaScript. And after working with JavaScript, liquid became easy for me. So yeah. I would say.

Project manager. So, yeah, I have been a part of a team in my past project where we had a team of 6 people and a project manager. Every day, whenever there were new features coming, we would discuss them in our daily meetings and attend the scrum meeting. Every time, according to my experience, I never had to rush over things and explain everything. The reason was that there was a project manager who assigned us tasks. And according to that task, we needed to manage and prioritize things through discussion with the project manager. That's what the development process makes easy. Instead of performing all the duties, such as determining the next task, its priority, and deadline, and so on. I guess I'm truly flexible when working with a project manager because that ultimately makes my life as a developer easy, especially in complex projects, not just small ones.

So as I mentioned earlier, I don't have really great experience working with the template because I had only used it for past two projects and, gladly, for redesigning a few components only. They were already based on CSS components that we had used from the. So I really don't understand, so I would be very honest here.

Shopify. Okay. So, recently, in one of my projects, there was a task, like, we needed to synchronize the data from the 3rd party web application. So, ultimately, it was the same client. Like, they had a web application and were taking test routes from users. So, they stored symptoms data into a MySQL database. They wanted to synchronize it with Shopify. And, there is the Shopify REST API, which provides customizing data, but they also have a new facility to store symptoms tags from 3rd party applications directly into Shopify customer tags. So, I found one way to do that. In that case, we were writing a script using the Shopify customer API to update the customer. That's one way to do it. Another way, if there aren't many users, is to import the data into an Excel sheet using the import feature, and then update the customer tag using the Shopify flow. Shopify flow is one of Shopify's default applications. I created a flow in that system. For example, if I found a customer with the same email address, I needed to create a condition that if it found a similar email ID, then it would take an action to update the customer tag with that data. This was a recent experience I had with Shopify, which was quite difficult. But, in this way, we can find a solution. Using the Shopify flow is maybe easy.