I am leading PIM(MFGDM) core projects technically and taking care as a SM and Tech lead where I rigorously follow Agile practices with planning, Grooming, and Retro with the team. I participate in and initiate cross-team alignment meetings. I have handled requirement gathering, development, deployment, and release with the help of the team.
Assisted the team in navigating challenges, anticipating risks, and implementing strategic solutions for both immediate and long-term goals. Developing a roadmap for technical solutions for each project.
Created a safe space for all developers to ask questions, share ideas, and express concerns. Offer guidance and support to help them solve problems independently.
In Autodesk, I have handled multiple scrum teams technically and taken care of onboarding those teams as well.
I have prepared specific best practices, technical documents, PR review guidelines, and DOD documentation for the team.
In Autodesk, I mainly work on PIM components/services, AWS/ACP services, and the deployment process.
Below are the few projects I worked with Autodesk.
Projects:
Configurations in FT.
- Considering the product knowledge I gained at Autodesk, understanding the challenges, customers' pain points, and needs, I used those skills during the requirement gathering for the configuration feature project implementation. As a result, the previous estimation was 2 slices, but my team and I discovered multiple workflows, edge cases, and a new slice (7/8) rectified and delivered as part of the configuration project. This slice, 7/8 epic requirement, was provided by the dev team, and we were successfully able to deliver the defined and additional scope of the configuration project within the timeline.
- Worked on the New Configuration feature in Fusion Team.
- Worked on post-release customer issues.
- Worked on configuration listing, performance tuning, and optimization.
Block Project Transfer.
- Developed an API to determine whether a hub is holding any PIM or ME-related data. As a result, PT has been blocked from FT.
- Initially, they required blocking the PT, and a few months later, they had a requirement to unblock the PT. This was handled via a feature flag and one new API implementation, and I was actively engaged in development and with stakeholders throughout various phases to clarify requirements, review solutions and plans, and share status updates and progress.
PIM as a critical service for fusion.
- Client delivery repo/skills(C++) is new to the team and with the help of SPE, PO, and Architects able to streamline requirement and implementation path for this project.
- Worked on client delivery and PIM mono, and made PIM a mandatory service to keep up the fusion online.
- As a part of this, I have implemented pimCircuitBreaker, through which the health of PIM services is monitored in Fusion.
- Analytics board has also been made to track the working potential of this feature and continuously observe to track different Ups/Downs of PIM and fusion.
Export of Nested CD and Assemblies with Xrefs to Configs.
- Worked on front-end and back-end to send/process required payload to PIM-MONO import and export job.
- Have made a smooth integration and alignment with the Fusion import jobs when the designs are being exported from Fusion Teams.
- Have also arranged an analytics board to track the working/utility of this feature.
PIM Service Regionalization.
- PIM service infrastructure setup and deployment to new region EMEA is completed. A part of this project.
- Currently, I am handling PIM Service regionalization Automation, and as a part of this, I am helping the team to develop and implement automation to enhance the efficiency of engineering processes, and create or refine tools to enable the other team to work more effectively.
Dual Home.
Dual Home is to shift the source of truth away from WIP and towards MFGDM by achieving data parity between the two platforms.
- As a part of phase 1, I supported a few Jira tickets and created functional tests for client code that do not need to call the Forge Backend on every run. This library is already implemented by the coffee team, and we enhanced it to decrease code duplication. Whenever there is a requirement to integrate forge-api-mock and make this repository viable and easy to integrate/import throughout the organization.
- Currently Dual home phase 2 work is going on , I am working on refactoring core work epic , which were initially created by the SDK and lib as a part of phase 1 by the coffee team.
- Solution document/approach finalisation/implementation is in process to prepare one generic API to create/update the document asset.