Cloud Developer
Python
SQL
Active 6 days ago
Download CVCV
Overview
Technical skills
Projects
Timeline
Roles
Overview
Frontend app engineer (Middle) specializing in building CRUD React single-page applications with form-driven admin UIs. The strongest proven skill is React-based SPA development demonstrated by components such as src/components/Crop.js, src/components/Home.js and src/components/modal/ChemicalModal.js. There is little evidence of advanced frontend architecture, measured performance work, automated tests, or robust accessibility engineering in public code.
Phone
Technical skills
Languages
2
Python
SQL
Frontend
3
React.js
Tailwind CSS
React Router
DevOps
16
AWS
Amazon S3
Amazon CloudWatch
Amazon EC2
AWS Lambda
Amazon EventBridge
GitHub
GitHub Actions
Docker
Git
GitLab
Linux
Apache HTTP Server
CI/CD
Docker Compose
Nginx
Other
5
MySQL
Gunicorn
DNS
IAM
PHP-FPM
Projects
AWS Auto Scaling & Monitoring with CloudWatch
Implemented an EC2 Auto Scaling setup driven by CloudWatch metrics to maintain application availability and elastic capacity. Configured CloudWatch alarms and alerting mechanisms to support proactive monitoring. Applied AWS monitoring and scaling concepts to improve resilience under changing workloads.
Docker 3-Tier Web Application
Designed and deployed a Docker-based 3-tier web application with Nginx as a reverse proxy, PHP-FPM for application processing, and MySQL for data storage. Used Docker Compose to orchestrate containers and created isolated Docker networks to limit direct database access. Configured a persistent named volume for MySQL so data survives container restarts.
AI-Powered DevOps Log Analyzer
Developed a log analysis platform using Flask and MySQL to help detect and troubleshoot application and server issues. Added automated severity classification and root-cause analysis to speed up debugging and suggest relevant Linux/DevOps commands. Containerized the service with Docker and Docker Compose and deployed it to AWS EC2 using GitHub Actions for CI/CD.
Timeline
Cloud Engineer Intern
·
Junior
Cravita Pvt Ltd
·
Internship
Provisioned and managed AWS EC2 instances with IAM roles and security group rules to control access. Implemented automated backup and disaster recovery workflows using AMIs and EBS snapshots together with AWS CLI and shell scripts. Built monitoring using CloudWatch dashboards/alarms and configured EventBridge rules to improve visibility and incident response.
Amazon EC2
IAM
Amazon CloudWatch
Amazon EventBridge
Bash
Middle Frontend Developer
Confidence: Medium App Engineer
Frontend app engineer (Middle) specializing in building CRUD React single-page applications with form-driven admin UIs. The strongest proven skill is React-based SPA development demonstrated by components such as src/components/Crop.js, src/components/Home.js and src/components/modal/ChemicalModal.js. There is little evidence of advanced frontend architecture, measured performance work, automated tests, or robust accessibility engineering in public code.
UI Component Architecture
3/10
How interface parts are built
Component boundaries exist (pages, modals, utility components) and composition is used, but there is no evidence of a custom design system, tokens, or advanced composition patterns.
Evidence
Farmer-Management-System/AgroTech-frontend-main/src/components/Crop.js: page component composing FarmerDetails, CropModal, Notification and Loader
Farmer-Management-System/AgroTech-frontend-main/src/components/modal/ChemicalModal.js: reusable modal component with local form state and validation
Farmer-Management-System/AgroTech-frontend-main/src/components/Home.js: list page composing AddFarmerModal and Notification
Responsive & Cross-browser
2/10
Works on all screens and browsers
Basic responsive rules are present (media queries and Tailwind usage) and browserslist is configured, but there is no evidence of advanced layout strategies (container queries, RTL, feature detection).
Evidence
AI-Powered-DevOps-Log-Analyzer/templates/index.html: CSS @media (max-width: 700px) responsive adjustments
Farmer-Management-System/AgroTech-frontend-main/tailwind.config.js: Tailwind configured for src/**/*
Farmer-Management-System/AgroTech-frontend-main/package.json: browserslist entries
Performance Optimization
1/10
Speed of the interface
No measured or deliberate performance work is present; there is no evidence of code-splitting, virtualization for lists, or bundle analysis artifacts.
Evidence
Farmer-Management-System/AgroTech-frontend-main/src/components/Crop.js: renders full table of items without virtualization
Farmer-Management-System/AgroTech-frontend-main/src/components/Fertilizer.js: maps all items into table rows without pagination or virtualization
Accessibility & Semantics
2/10
Usable for everyone
Forms use native labels and inputs which is good baseline semantics, but there is no ARIA on custom widgets, no explicit keyboard/focus management for modals, and no CI a11y tooling evident.
Evidence
Farmer-Management-System/AgroTech-frontend-main/src/components/modal/ChemicalModal.js: uses <label> and inputs for form fields
AI-Powered-DevOps-Log-Analyzer/templates/index.html: uses native textarea for log input
State Management & Data Flow
2/10
Managing data in the app
Uses React useState/useEffect and fetch for server-state with basic error handling, but lacks request cancellation, optimistic updates with rollback, cache invalidation strategies or state machines for complex flows.
Evidence
Farmer-Management-System/AgroTech-frontend-main/src/components/Crop.js: fetchCrops and per-crop cost fetch via fetch inside useEffect with try/catch
Farmer-Management-System/AgroTech-frontend-main/src/components/Home.js: fetchFarmerData with basic error handling and subsequent re-fetch after mutations
UX & Visual Polish
3/10
Look and feel quality
Good UX touches exist such as modals, client-side form validation and notification banners plus a Loader component, but there are no skeletons, undo flows, or nuanced perceived-performance improvements.
Evidence
Farmer-Management-System/AgroTech-frontend-main/src/components/modal/ChemicalModal.js: client-side validation and modal UX
Farmer-Management-System/AgroTech-frontend-main/src/components/Crop.js: Notification usage and Loader import
Expertise
React· Middle
Technologies
Tailwind CSS
React.js
React Router
AWS· mentioned only
DevOps· mentioned only
Docker· mentioned only
Docker Compose· mentioned only
Linux· mentioned only
Nginx· mentioned only
PHP-FPM· mentioned only
Recommendations
- Build internal CRUD dashboards and admin interfaces where the developer can own end-to-end UI, forms, modals and API integration.
- Harden existing frontends for production by adding request cancellation, optimistic update patterns, pagination or virtualization for large lists, and unit/integration tests.
- Improve accessibility and UX polish by adding ARIA roles, focus management for custom modals, skeleton loaders, and CI a11y checks.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Intern Backend Developer
Confidence: Low Generalist
A junior-level generalist with hands-on experience in front-end build and lint configuration and an interest in DevOps. The strongest proven skill is configuring front-end tooling and linting as shown in portfolio/eslint.config.js and portfolio/vite.config.js. There is no public, human-authored backend code or infrastructure automation to evidence API design, data-layer work, messaging, security, or operational engineering.
API Design
How well APIs are designed
Not evidenced in public code
Data Layer & Database
Working with databases
Not evidenced in public code
Scalability & Performance
Handling load and speed
Not evidenced in public code
System Architecture
Overall system structure
Not evidenced in public code
Security & Auth
Protecting data and access
Not evidenced in public code
Reliability & Observability
Stability and monitoring
Not evidenced in public code
Recommendations
- Entrust with front-end build and quality work such as maintaining Vite configurations, eslint rules, and developer tooling improvements.
- Assign to small DevOps tasks that involve containerization and CI/CD for front-end apps, for example creating pipeline steps to build, lint and deploy the portfolio site.
- Have them pair with a backend engineer to implement and document simple REST endpoints and deployment patterns so they can gain backend and API experience.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Intern DevOps Engineer
Confidence: Low
An aspiring DevOps and cloud engineer at an early-career level with a focus on AWS-based deployment concepts. No human-authored code artifacts were provided to prove technical skills, so there is no concrete artifact to cite as a proven strength. Public files do not evidence implemented CI/CD pipelines, IaC modules, container orchestration configs, observability or incident documentation, so those capabilities are not demonstrated here.
CI/CD Pipelines
Automated build and deploy
Not evidenced in public code
Infrastructure as Code
Managing servers with code
Not evidenced in public code
Containerization & Orchestration
Working with containers
Not evidenced in public code
Observability & Monitoring
Watching system health
Not evidenced in public code
Reliability & Incident Response
Keeping systems up
Not evidenced in public code
Cloud & Cost Optimization
Smart use of the cloud
Not evidenced in public code
Recommendations
- Create and publish a handful of human-authored, focused artifacts such as a Terraform module with remote state and locking demonstrating environment separation and lifecycle rules.
- Add a CI/CD pipeline example (reusable workflow or GitHub Actions) that includes caching, job matrix, deploy gates and a simple rollback step to demonstrate pipeline engineering decisions.
- Publish a Kubernetes or ECS deployment manifest with tuned readiness/liveness probes, resource requests/limits, and a PodDisruptionBudget to show resilience and orchestration reasoning.
- Add at least one observability artifact such as a Prometheus alerting rule tied to an SLO and a dashboard-as-code JSON or Grafana YAML to evidence monitoring and alerting design.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
