Priyank . Email & Phone Number

Noida, Uttar Pradesh, India

I was a member of the Unified Profile Service, a sister team of the Adobe Experience Platform [kind of Customer Experience Management (CXM)]. My primary contribution involved developing, maintaining and operational improvement of services responsible for creating merged user profiles and exporting this data to various destinations. This data was then utilized by downstream services for purposes such as running campaigns. e.g. - sending promotional emails based on specific conditions.- Operational Tools.- Support for deployment of multiple long running applications.- Wrote New Spark Job Launcher Service using Tapir.- Added optimization to export from the Snapshot to reduce full read time of all the profiles. - Improvements in the scheduling logic of the jobs . - Root Caused and Fixed the problems in the Spark job that was happening due less optimal use of Akka Streams and introduced back pressure. - Code changes for multi cloud movement. - Regional expansion

Bangalore Urban, Karnataka, India

I was a member of a sister team at Amazon Pay focused primarily on software for merchant onboarding and compliance. During my tenure, I contributed to building a domain validation service using AWS services. This service was crucial for ensuring compliance and preventing Amazon Pay from being used for illegal activities. Additionally, I played a role in enhancing/simplification of APIs used for merchant registration, aimed at operational improvements within Amazon Pay.

Bangalore Urban, Karnataka, India

I was a member of a sister team within Amazon's Elastic Search Service (AES), dedicated to developing an advanced monitoring service. This service was designed to monitor both the Control Plane (which orchestrates resources and manages Elastic Search clusters) and the Data Plane (comprising the Elasticsearch software).During this experience, I gained hands-on experience in building services and frameworks from the ground up using GoLang. I utilized multiple AWS services for infrastructure and CI/CD.- Migrated, updated, added, and fixed bugs in the monitoring code - * Kibana Health – Kibana is used to visualize the time series data. Monitor was used to monitor the health of respective Kibana index. * Domain Resource State * KMS – Keys are used for encryption at rest and encryption in transit. This monitor is used to check the state of keys. * All Node Out of Service * Split Brain Detection * Cognito Resources – Used to check various pools and their state. * Snapshot (s3) related - DynamoDB access layer (for monitoring service)- Alpha Integration Tests (for monitoring service)- Monitoring service launch and prod readiness.- Region build of monitoring service [for special regions]- Multi tenancy feature [Cost reduction and to reduce down time (ops improvement)]- Changes to test fixes locally [One box setup (ops improvement)]- Integration with AWS Config Service. (ops improvement)- Integrated/Modified Golang KPL[Kafka Producer Library] (like added shard mapper) and KCLas new per data store requirement- Improvements in AES Canaries.

Bangalore Urban, Karnataka, India

- Fixed issues and Integration Tests in the software components that are used in Grocery supply chain (outbound flow).I was a member of the team responsible for developing the software components used to manage the outbound flow of Flipkart’s warehouse supply chain. Through this role, I gained valuable exposure to the operations of warehouse supply chains and contributed to it’s software's implementation.

Bangalore Urban, Karnataka, India

- Support for resizing the root volume of virtual machines in Apache CloudStack (limited to increasing size only).Whenever a respective hypervisor introduces new features, adjustments are required in Apache CloudStack to accommodate these changes. Following the release of VMware ESXi's feature to increase root disk size, we have implemented code in CloudStack to support this capability.- Exempting network sub-net from usage calculation.Several companies utilize CloudStack for delivering Infrastructure as a Service (IaaS). To accurately bill customers, network traffic is used as one of the parameters. In this work, We enhanced CloudStack by introducing the capability to exclude virtual machines connected via specific sub-net ranges (from being billed).GitHub Link for the contributions that are made public - https://github.com/apache/cloudstack/pulls?q=is%3Apr+author%3Apriyankparihar+is%3Aclosed

Bangalore Urban, Karnataka, India

- Primarily worked on integration of Net-Scaler Control Center with CloudStack. Apache CloudStack - is an open-source cloud computing platform designed to manage and deploy virtual machines. It is mainly used to provide Infrastructure-as-a-Service (IaaS)NetScaler provides functionalities related to application delivery, load balancing, and traffic management.NetScaler Control Center is designed to provide centralized management and monitoring capabilities for NetScaler appliances deployed in an enterprise environment. So In this work we have added capability in the Cloudstack to manage NetScaler appliances /instances via NetScaler Control Center.

Master Of Engineering - Meng, Computer Science

Bachelor Of Technology - Btech, Computer Science

Education record