Pravin Mali
Java Developer
Java
Data Layer & Database: 5/10
API Design: 4/10
System Architecture: 4/10
Active 6 days ago
+91 (9356) 609321 Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
Backend-focused Java engineer (senior-level borderline) with a strength in building API-first microservices and integrating auth and event-driven messaging. The strongest proven skill is implementing auth and gateway enforcement as shown by JwtUtil.java and JwtAuthenticationFilter.java together with the API gateway AuthController. Public code lacks systematic production operational artifacts such as metrics/alerts, robust retry/backoff strategies and deployment manifests, limiting evidence of runbook-level SRE work.
Technical skills
Java• Middle
Java
Spring Data JPA
Spring MVC
Spring Security
Hibernate
Spring Boot
Databases
MySQL
NATS
Redis
PostgreSQL
Frontend
Web Components
Vite
React.js
DevOps
Git
Rest API
Self-Healing
QA
Postman
AI/ML
AI Agents
Timeline
Backend Development Intern
•
Junior
Infosys Springboard
•
Internship
Completed a project-based backend internship focused on Java and Spring Boot. Implemented RESTful APIs and used JPA/Hibernate to integrate backend services with a PostgreSQL database. Contributed to full-stack features by building responsive frontend components and connecting them to backend endpoints. Used Git for version control and followed debugging and testing best practices.
Java
Spring Boot
Hibernate
PostgreSQL
Rest API
Git
React.js
Java
Spring Boot
NATS
PostgreSQL
Spring Security
Spring Cloud
Spring Data JPA
Lombok
Java
Spring Boot
Spring Data JPA
Spring Security
PostgreSQL
React.js
Git
Postman
Middle Backend Developer
Confidence: High API Engineer
Backend-focused Java engineer (senior-level borderline) with a strength in building API-first microservices and integrating auth and event-driven messaging. The strongest proven skill is implementing auth and gateway enforcement as shown by JwtUtil.java and JwtAuthenticationFilter.java together with the API gateway AuthController. Public code lacks systematic production operational artifacts such as metrics/alerts, robust retry/backoff strategies and deployment manifests, limiting evidence of runbook-level SRE work.
API Design
4/10
How well APIs are designed
API-first microservices with a gateway and reactive client code; reasonable error handling patterns but limited versioning, pagination and idempotency design.
Data Layer & Database
5/10
Working with databases
Data layer uses JPA repositories and transactional boundaries plus a clear transactional outbox pattern for async delivery, showing deliberate schema and integrity choices.
Evidence
pravin1808/MicroServices-Application/user_service/src/main/java/com/civicpulse/user_service/service/UserService.java
pravin1808/MicroServices-Application/user_service/src/main/java/com/civicpulse/user_service/config/SecurityConfig.java
pravin1808/CivicPulse/src/main/java/com/civicpulse/civicpulse/service/AdminService.java
Scalability & Performance
3/10
Handling load and speed
Some event-driven decoupling and gateway-based routing are present, but there is little documented caching, explicit load-control, or tuned performance work.
Evidence
pravin1808/MicroServices-Application/user_service/src/main/java/com/civicpulse/user_service/service/UserService.java
pravin1808/MicroServices-Application/api_gateway/src/main/java/com/civicpulse/api_gateway/controller/AuthController.java
pravin1808/MicroServices-Application/api_gateway/src/main/java/com/civicpulse/api_gateway/filter/JwtAuthenticationFilter.java
System Architecture
4/10
Overall system structure
Clear service separation (API gateway, user service, notification paths) and architectural patterns (gateway-enforced auth, outbox) demonstrate deliberate decomposition decisions.
Evidence
pravin1808/MicroServices-Application/api_gateway/src/main/java/com/civicpulse/api_gateway/filter/JwtAuthenticationFilter.java
pravin1808/MicroServices-Application/api_gateway/src/main/java/com/civicpulse/api_gateway/config/JwtUtil.java
pravin1808/MicroServices-Application/user_service/src/main/java/com/civicpulse/user_service/config/SecurityConfig.java
Security & Auth
4/10
Protecting data and access
Authentication and authorization are implemented end-to-end with JWTs, password hashing and user detail services, though some cryptographic/api uses and permissive security defaults need review.
Evidence
pravin1808/MicroServices-Application/api_gateway/src/main/java/com/civicpulse/api_gateway/config/JwtUtil.java
pravin1808/MicroServices-Application/api_gateway/src/main/java/com/civicpulse/api_gateway/filter/JwtAuthenticationFilter.java
pravin1808/MicroServices-Application/user_service/src/main/java/com/civicpulse/user_service/config/SecurityConfig.java
Reliability & Observability
3/10
Stability and monitoring
Basic observability and error handling exist (logging, reactive onErrorResume), but systematic reliability practices like retries with backoff, timeouts, structured correlation ids and metrics are not evident.
Evidence
pravin1808/MicroServices-Application/api_gateway/src/main/java/com/civicpulse/api_gateway/controller/AuthController.java
pravin1808/MicroServices-Application/user_service/src/main/java/com/civicpulse/user_service/service/UserService.java
pravin1808/MicroServices-Application/api_gateway/src/main/java/com/civicpulse/api_gateway/filter/JwtAuthenticationFilter.java
Verified artifacts
Expertise
Java• Middle
Microservices & API Architecture• Middle
Messaging & Real-time• Middle
System Architecture• Middle
Technologies
Java• Middle
MySQL
PostgreSQL
Redis
Rest API
NATS
Spring Boot
Hibernate
Git
Spring MVC
Spring Data JPA
Spring Security
Recommendations
- Develop REST/GraphQL microservices and API gateways with JWT-based authentication and header propagation.
- Implement event-driven features and reliable delivery using NATS JetStream and the transactional outbox pattern.
- Integrate Redis-backed ephemeral workflows (OTP, temporary caches) and implement end-to-end observability (traces, metrics, structured logs).
- Harden security defaults: fix cryptographic JWT usage, avoid permitAll in production configs, and add token lifecycle controls and revocation paths.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Intern Frontend Developer
Confidence: Low UI Engineer
UI engineer (junior) focused on polished static front-end pages and embedded chatbot widget experiences. The strongest proven skill is visual design and theming, evidenced by the agriculture-chatbot/agri_chatbot_ui.html file with comprehensive CSS variables, animations, and a themed df-messenger integration. There is little to no public evidence of non-trivial front-end architecture, async state management, automated tests, or accessibility engineering practices.
UI Component Architecture
2/10
How interface parts are built
Light component-like structure in a single static page but no modular component architecture, custom hooks, or composition patterns.
Evidence
agriculture-chatbot/agri_chatbot_ui.html: clearly separated .header, .chat-card and .chat-prompt-area sections showing structure but not reusable components
agriculture-chatbot/agri_chatbot_ui.html: openDFMessenger() function encapsulates interaction with the df-messenger web component rather than a component-based API
Responsive & Cross-browser
3/10
Works on all screens and browsers
Basic responsive work and fluid layout considerations are present, but no advanced cross-browser feature detection, container queries, or RTL/i18n scaffolding.
Evidence
agriculture-chatbot/agri_chatbot_ui.html: <meta name="viewport" content="width=device-width, initial-scale=1.0">
agriculture-chatbot/agri_chatbot_ui.html: @media (max-width: 900px) responsive rules and flexible .app-wrapper with max-width and rem units
Performance Optimization
1/10
Speed of the interface
No measurable performance work or code-splitting; only basic CSS animation usage without prefers-reduced-motion or lazy-loading strategies.
Evidence
agriculture-chatbot/agri_chatbot_ui.html: multiple keyframes animations (pulse, float, fadeUp) but no performance measurement artifacts
agriculture-chatbot/agri_chatbot_ui.html: no lazy-loading or resource hint usage visible for assets or widgets
Accessibility & Semantics
2/10
Usable for everyone
Minimal accessibility basics such as lang attribute and semantic button usage, but missing ARIA, explicit focus management, keyboard handling for custom widget interactions and prefers-reduced-motion.
Evidence
agriculture-chatbot/agri_chatbot_ui.html: <html lang="en"> and use of semantic <button> for primary action
agriculture-chatbot/agri_chatbot_ui.html: openDFMessenger() interacts with shadow DOM of df-messenger but there is no explicit focus management or ARIA glue
State Management & Data Flow
1/10
Managing data in the app
No client-side state management, async request handling or cancellation patterns are implemented beyond direct DOM queries and event dispatching.
Evidence
agriculture-chatbot/agri_chatbot_ui.html: openDFMessenger() uses document.querySelector and dispatchEvent only; no fetch/axios usage or state machine logic
agriculture-chatbot/agri_chatbot_ui.html: no form validation schema, optimistic updates, or request cancellation patterns
UX & Visual Polish
4/10
Look and feel quality
High visual polish for a static page with thoughtful theming, CSS variables and animations, producing a professional UI for a chatbot landing experience.
Evidence
agriculture-chatbot/agri_chatbot_ui.html: :root CSS variables and a coherent color/tone system for theming
agriculture-chatbot/agri_chatbot_ui.html: detailed styles for .chat-card, .chat-topbar, animated icons and decorative SVGs showing strong visual design focus
Expertise
HTML & CSS• Intern
Frontend AI Integration• Intern
Modern Web Frameworks• Intern
Industries
Farming & Agriculture• Intern
Technologies
React.js
Vite
Web Components
UI• mentioned only
Recommendations
- Build polished static landing pages, marketing sites and widget-embedded UIs where strong visual theming is the primary requirement.
- Implement and migrate the static UI into component-based React code to enable reuse, testing and better state handling for chatbot flows.
- Integrate accessibility improvements and simple state management patterns for interactive chatbot experiences, such as focus management and ARIA support.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: