Experienced data engineer with 6 years of expertise in complex, custom-designed, and scalable software development projects. Specialized in data engineering using PySpark, Python, Kafka, AWS services, and other backend tools. Proficient in developing robust REST APIs using FastAPI and Flask, as well as web scraping and automation using Python libraries. Strong object-oriented programming skills and knowledge of design patterns. Adept at processing large datasets using data pipelines with PySpark, AWS, and other DevOps tools. Skilled in working with PostgreSQL, MongoDB, and other databases.
Data Engineer & Backend Developer
MSBC Solutions Pvt Ltd (Contractual)Consultant
Virtusa Consulting Pvt LtdFull Stack Developer
NEST TECH UK BASED (Contractual)Full Stack Web Developer
Tetra Quark InnovationFull Stack Developer
Focus LabsPython Developer
PiChain Innovations Pvt LtdPython
NodeJS
MySQL
MongoDB
Redis
Kafka
Jenkins
AWS
Azure
Git
Bitbucket
Javascript
angul
Flask
FastAPI
Django
Node.js
Express.js
PostgreSQL
AWS (Amazon Web Services)
AWS EMR
AWS Lambda
AWS S3
Docker
REGEX
Selenium
requests
Terraform
Redis
RabbitMQ
Celery
Kubernetes
Metabase
DynamoDB
Project 1- KYC APPLICATION & Copilot Management (KYC WEB APPLICATION & APP for Copilots Management)
Technologies Utilized: Python | Request | Selenium| AWS EC2 | MongoDB | AWS S3 | Kafka| Flask | FastAPI | Docker | DevOPS| Azure | Github | RESTAPI | PyTest | Unittest
Roles and Responsibilities: Backend Developer| Team Size 2
Project 2 - AWS and Azure Resource Automation (Terraform-based Resource Creation Automation)
Technologies Used: Python | Azure | DynamoDB | State Machines | API Gateway | AWS Services | Azure Blob | Github | Data Factory | Data Lake | Data Bricks | Azure Logs
Roles and Responsibilities: Backend Developer | Team Size 4
Project- Reltio Platform MDM Modernization (PySpark)
Technologies Used: Python | PySpark | PostgreSQL | AWS EMR Serverless | AWS Lambda | AWS S3 | Jenkins| Docker | REGEX | Azure Data Lake | Azure Data Factory
Roles and Responsibilities: Backend Developer| Team Size 3
Objective:
The project aimed to automate infrastructure management tasks using Terraform configurations, ensuring secure access, efficient resource provisioning, and comprehensive monitoring.
Key Features Implemented:
Objective:
The project aimed to establish and manage a robust Master Data Management (MDM) system tailored for the healthcare industry, ensuring accurate and reliable data management across various sources.
Key Responsibilities and Activities:
Technologies Used:
Benefits:
Project Details:
1. One-Click Verification and Data Extraction API
Objective:
Developed and deployed a FastAPI-based API to automate document verification and extraction from multiple web portals.
Key Responsibilities and Achievements:
2. Legacy API Performance Optimization and Migration
Objective:
Reduced response times for legacy APIs by 90% through request-based optimization techniques and migrated over 70 APIs to the new approach.
Key Responsibilities and Achievements:
3. Backend Service for Portfolio Management System
Objective:
Designed and developed a comprehensive backend service for a Portfolio Management System to streamline investor onboarding processes.
Key Responsibilities and Achievements:
4. Software-as-a-Service Platform for Custom Chatbots
Objective:
Developed a Software-as-a-Service (SaaS) platform tailored for custom chatbots catering to industries such as health and safety and the IT sector.
Key Responsibilities and Achievements:
Technologies Used:
Benefits:
Objective:
The project aimed to develop a feature-rich chat application to facilitate instant messaging and real-time communication among users.
Key Features Implemented:
Yeah. Hello. Uh, my name is Mohammed Ali. I have almost, uh, 6 years of experience in IT industry. Mostly, I have worked at the back end developer. So coming to the text stack, um, I'm good at Python, uh, and the framework Flask and, uh, FastAPI. And, uh, coming to the database, I am good at, uh, post phase, uh, Oracle, uh, SQL database, and coming to North SQL database, which is MongoDB and, uh, AWS services like DynamoDB, uh, AWS Lambda, uh, API Gateway, uh, Middlewares, and EMR serverless, and, uh, EMR, uh, and, uh, you know, AWS state machines and AWS state machines and, uh, AWS hardening, post processing, Terraforms. Uh, I have knowledge on that, and I have worked on this project. So, um, uh, apart from these other projects, I have worked on this, uh, PySpark, uh, data pipeline where our data has to be processed from a pipeline, and the final data, uh, has to be, uh, added to the data database like post grades, uh, after preprocessing and, uh, auditing the data. So apart from that, I have built a software as a service, um, for the Copilot management where an organization can onboard multiple, uh, their, uh, subsidiaries and the sub organization. And, uh, its users can be managed, uh, from that, uh, that SaaS product, and, uh, we can also manage their, uh, you know, uh, uh, manage their subscription, like a freemium or premium subscription, uh, for their chatbots. So this software this, uh, the project also includes, like, um, this product also includes, like, um, 1 to 1 chat, uh, group chat, and, uh, features like blocking, read receipts, all these things. Yep. Apart from, uh, these 2 projects, I have worked on, uh, scrapping the data, uh, scrapping data from multiple websites, like, uh, for the purpose of AML KYC and, uh, for the purpose of, uh, business loans and all other, uh, based on the requirement of the client. So the tech stack I used in scrapping was Python and the selenium request based extraction techniques and, uh, scrappy as well. Uh, Yeah. So these are the summary about my work.
Analyzing Python code block identify the design pattern using and explain why it might not be the most efficient approach for extending functionality. Let's notify. Send message. Sending message. Email notify. Send message. So here, uh, we are using super class again and again inside the method called email notifier inside the class called email notifier and SMS notifier. This should not be, uh, done. So according to me, I believe, uh, 1 class should be there, uh, of base notifier, and the email notifier and SMS notifier should be a method which should be inheriting the from the, uh, class called, uh, base notifier. And from there, it should be sending the message. So this is this 1, this is my understanding. I have built a notification service using Kafka, uh, and, uh, it requests, uh, you know, of Firebase for the push notification and the email templates and the SMS service for SMS notification.