Pooja Patil

Hi. My name is Puja. Um, I've been working in ONIT India Private Limited since 2018. It's been more than 6 years. I've been working here prior on it. I I used to work as a Java developer. I have 2.5 years of experience in Java. Let me correct. I have 2 years of experience in Java. And now, uh, I'm working as a lead solution engineer. Here, I have a team. We are around 13 people, including me. I lead that team. My roles and responsibilities are to assign a task to the team, get updates on time, assign the task equally amongst the team, to unblock the team if they have any queries, to guide them, to mentor the new joiners. Then, um, I'm a part of interview panel as well over here. Yeah. That is my professional introduction. Uh, personally, I'm married. Um, my husband has a firm. It's, uh, AC Sales and Services. I have a daughter. She is 6 years old, and I'm a bit quiet person. I like listening to new music. Yeah. That's all. Thank you.

So here, I handle multiple client projects and sometimes it happened. In the past, when I had to meet a deadline for one client, then at the same time, I had to finish some task on the other client as well. So in that scenario, I used to split my time between two high priority clients, then I'm pretty sure I work very well under the pressure. So lots of time I handle that situation and while working between teams, we have, I mean, I have to make some critical decisions, which task needs to be assigned to which team member because each and everyone is different, each and everyone's skills are different, speed is different. So lots of time I have to think about the task, the client and the team member's skill as well. So as per all these criteria, I have to assign the task. Thank you.

My experience it

What is given to an architecture? How can it be beneficial in design?

Usually, I have to review the task. I have to review the task completed by the team members. I follow the design document. Then, personally, I follow the steps to make sure the config is asked for the design document. So Whenever the client, um, team member needs any help, I offer my help. I I think my expertise would be beneficial for the other team members. So whenever I think it is required, I go ahead and help team members. Thank you.

How do you explain a complex software architecture to a nontechnical stakeholder? I drive client presentations as well. So, um, whenever I think about any critical configuration, critical workflow, I I try to explain as user's point of view, not as a technical person. I better understand that the person is listening listening to me. He's 0 x p he has a zero experience in technical work. So sometimes I use a real world scenario to explain the configuration to the client. And this is a part of my profile. I usually go to the client calls for review the design documents, to collect any additional requirements from the client, to present our configuration to the client, followed by to discuss the tickets they have raised on a daily basis.

So as per my experience, the key components of the software design document would be All the possible permutation combination should get covered specific to that scenario. Clarity would be a key component. Clarity in the sense requirement clarity. So I think whenever we discuss a design document with a client, a technical person should be there to understand what client really needs. Sometimes whenever the business analyst review the design document prepare the design document, it may happen that client might want something different, and, um, a technical person may have understood that in a different way. So I personally feel whenever the design document is getting prepared, we should discuss it with the client along with the technical person. That I would prefer.

So whenever I get time, I try to learn about new things, but it may not be possible. Whatever the things we are learning, all those fields, we cannot implement into our daily basis tasks. But, yeah, I try to implement the logic behind that technology, the concept, whatever I could use from the new thing. I definitely try that onto the my current profile.

So while mentoring, I would not prefer to start with the complex configuration, complex build to discuss with Prior that, I would prefer to give a simple tasks to the new team member to understand the scenario. I would if this scenario had come occur has occurred, if I have to explain a complex build to the new joiner, I would split that build into a small chunks. We can say into a small, uh, sub workflows. And I would explain those small workflows along with the real world examples. And, um, whatever we have learned so far, I would try to explain with a concept that we have learned as of now so that the new joiner can easily relate the configuration, the workflow that we are discussing about. So, um, yeah, I would not directly start with the complex build. I would split into I would split that build into small chunks. Then along with the real world scenarios, I would explain those small subtasks with the new joiner sequentially so that, um, a new joiner would not get confused, and, uh, he will get time to understand the complexity. Thank