Nilay Parmar
Software Engineer
5+ years exp
Java
JavaScript
TypeScript
Node JS
Go
API Design: 6/10
System Architecture: 6/10
Security & Auth: 6/10
Active 2 days ago
+91 (9428) 371852
Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
Backend engineer (mid-senior level) specializing in Go-based REST APIs and Kubernetes integrations with a clear focus on developer UX for cluster resources. The strongest proven skill is building Kubernetes resource transformation and auth flows, evidenced by podforge/backend/internal/builders/common.go and podforge/backend/internal/auth/oidc.go. Public code does not show a production-grade DB migration history, extensive distributed-systems operational patterns (circuit breakers, multi-region consistency), or a full observability/alerting pipeline.
Technical skills
Java
JavaScript
TypeScript• Middle • 4y+
Node JS• Senior • 3y+
Go• Senior • 3y+
Java
Spring Boot
Node JS
Axios
Nest.JS• 5y+
Go
Gin
Zap
GORM
Databases
PostgreSQL
SQLite
RabbitMQ• 5y+
Redis• 5y+
Frontend
React.js
React Query
Chakra UI
Tailwind CSS
Vite
Element Plus
DevOps
AWS
CI/CD
Amazon EKS• 3y+
ArgoCD• 3y+
GitLab CI• 3y+
Kubernetes• 3y+
Timeline
Senior Software Engineer
•
Senior
Elevation Services
•
Full-Time
Worked on routing shipment and order events with schema validation and reliable processing. Built and maintained Node.js ETL pipelines and owned API contracts, including ORM transaction boundaries. Optimized queries for high-volume reads and focused on keeping delivery unblocked while staying hands-on across the stack.
Node JS
Amazon EKS
Kubernetes
ArgoCD
GitLab CI
Software Developer
•
Middle
Kevit.io
•
Full-Time
Developed session management, identity flows, and token lifecycle functionality. Implemented and maintained API endpoints for multiple integrations while ensuring consistent behavior and data integrity across flows.
Software Developer
•
Middle
Inexture
•
Full-Time
Contributed to NestJS microservices for scalable messaging and backend workflows. Implemented features using RabbitMQ for messaging and Redis for caching, and supported AWS S3 and AWS SES based email workflows. Participated in build and deployment work and collaborated with core maintainers on code reviews and merges.
Nest.JS
RabbitMQ
Redis
Dharmsinh Desai University
Bachelor's Degree •
Computer Science
Senior Backend Developer
Confidence: High API Engineer
Backend engineer (mid-senior level) specializing in Go-based REST APIs and Kubernetes integrations with a clear focus on developer UX for cluster resources. The strongest proven skill is building Kubernetes resource transformation and auth flows, evidenced by podforge/backend/internal/builders/common.go and podforge/backend/internal/auth/oidc.go. Public code does not show a production-grade DB migration history, extensive distributed-systems operational patterns (circuit breakers, multi-region consistency), or a full observability/alerting pipeline.
API Design
6/10
How well APIs are designed
API design shows deliberate versioning, grouped route structure, consistent handler wiring and error shaping, but lacks explicit idempotency key handling and advanced pagination patterns.
Evidence
podforge/backend/internal/routes/routes.go
podforge/backend/internal/handlers/crud.go
podforge/backend/internal/util/error_util.go
Data Layer & Database
4/10
Working with databases
Data layer includes a testable user store and support for Postgres and SQLite with seeding logic, but there is little visible schema migration history or explicit transaction/isolation handling in the surfaced files.
Evidence
podforge/backend/internal/store/store.go
podforge/backend/internal/store/user_store_test.go
podforge/backend/internal/routes/routes.go (syncConfigUsers -> store.UpsertUser / SeedUsers)
Scalability & Performance
4/10
Handling load and speed
There are clear scalability-oriented pieces (SSE watch endpoints, bulk apply/delete routines and an apply service), but no visible, reasoned caching/invalidation strategy or measured load-optimizations and only limited evidence of configured backoff/retry policies.
Evidence
podforge/backend/internal/services/bulk_service.go (deleteRoutine / applyRoutine)
podforge/backend/internal/handlers/watch_handler.go (SSE handling)
podforge/backend/internal/services/apply_service.go
System Architecture
6/10
Overall system structure
A modular architecture separates handlers, services, store and middleware with a centralized route/handler wiring function and environment-aware auth setup, indicating deliberate decomposition for maintainability and testability.
Evidence
podforge/backend/internal/routes/routes.go (handlerSet and buildHandlers)
podforge/backend/internal/handlers/* (multiple handler constructors)
podforge/backend/internal/services/* (service constructors)
Security & Auth
6/10
Protecting data and access
Concrete authentication and authorization work is present: local JWT-based auth, OIDC verifier with domain allowlist and role mapping, middleware enforcement and password-hash validation; secrets and dev-mode warnings are handled, but there is no visible token revocation or refresh lifecycle implementation in the exposed code.
Evidence
podforge/backend/internal/auth/oidc.go
podforge/backend/internal/auth/local.go
podforge/backend/internal/middleware/authn/authn.go
Reliability & Observability
5/10
Stability and monitoring
Observability and reliability are addressed with structured logging middleware, gin.Recovery usage, test coverage for error envelopes, and some timeouts, but advanced resiliency patterns (circuit breakers, reasoned retry with jitter, graceful shutdown sequences) are not visible in the human-authored code surfaces shown.
Evidence
podforge/backend/internal/middleware/logger/logger.go
podforge/backend/internal/util/error_util.go
podforge/backend/internal/routes/routes.go (use of gin.Recovery and a context timeout in setupAuth)
Verified artifacts
Expertise
Go Development• Middle
Microservices & API Architecture• Middle
Java• Middle
Industries
Software• Middle
Technologies
Java
PostgreSQL
Redis• 5y+
Nest.JS• 5y+
Spring Boot
RabbitMQ• 5y+
GitLab CI• 3y+
Zap
CI/CD
ArgoCD• 3y+
SQLite
AWS
Kubernetes• 3y+
Amazon EKS• 3y+
Recommendations
- Develop and maintain a migration history and schema evolution plan for the user store and any future persistent schemas (apply migrations, versioning and tests).
- Extend resilience: add configurable retries with jitter/backoff and circuit-breaker-like guards around expensive k8s API calls and the apply/bulk paths, and add graceful shutdown handling for background workers.
- Build end-to-end observability: instrument key services with metrics and traces and add health/ready probes that reflect dependency readiness (DB, k8s API).
- Own APIs and RBAC-sensitive features: design idempotency for bulk apply/delete operations and document error contracts and pagination for list endpoints.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle Frontend Developer
Confidence: Medium App Engineer
Middle-level frontend application engineer specializing in typed React SPAs and integrations with backend systems. The strongest proven skill is server-state and integration discipline, demonstrated by podforge/ui/src/hooks/createResourceHooks.ts (TanStack Query patterns and cache invalidation) and podforge/ui/src/auth/oidc.ts (correct PKCE OIDC flow with state and error checks). There is little public evidence of systematic accessibility testing, measured performance optimization artifacts, or broad end-to-end test coverage in the human-authored files.
UI Component Architecture
4/10
How interface parts are built
Modular component logic and reusable hooks are present, with typed manifest conversion and a hook factory that avoids prop-drilling, but there is limited evidence of a deliberate component system or composition patterns across many UI components.
Evidence
podforge/ui/src/hooks/createResourceHooks.ts: createResourceHooks factory with query keys, useList/useDetail/useCreate/useRemove
podforge/ui/src/components/manifest/kindStrategies.ts: KIND_STRATEGIES and per-kind toManifest/fromManifest conversion functions
Responsive & Cross-browser
3/10
Works on all screens and browsers
Basic responsive and cross-browser concerns are handled at the app shell level (viewport, dark-first flash avoidance, CSS tokens), but there is no evidence of advanced layout strategies or RTL/i18n readiness.
Evidence
portfolio/index.html: viewport meta and pre-paint theme script to avoid flash
portfolio/src/index.css: Tailwind-based theme tokens, dark-mode color-scheme and scrollbar styles
Performance Optimization
2/10
Speed of the interface
Some pragmatic performance considerations exist (server-state caching, refetch intervals, reduce flash on first paint) but no measured optimizations, bundle analysis, code-splitting strategy, or virtualization artifacts are present.
Evidence
podforge/ui/src/hooks/createResourceHooks.ts: useQuery with refetchInterval and cache invalidation on mutations
portfolio/index.html: critical inline script to avoid theme flash (perceived performance)
Accessibility & Semantics
2/10
Usable for everyone
Minimal accessibility signals such as lang attribute and accessible HTML structure are present, but no ARIA on custom widgets, focus management, or a11y tooling in CI is evidenced in human-authored files.
Evidence
portfolio/index.html: <html lang="en"> and semantic head/meta tags
portfolio/src/index.css: dark-mode and selection styles but no ARIA/focus management code
State Management & Data Flow
5/10
Managing data in the app
Clear server-state and async discipline is implemented using TanStack Query with consistent query keys, invalidation on mutations, and enabled flags; OIDC PKCE flow includes session handling and state verification, showing good integration and security awareness.
Evidence
podforge/ui/src/hooks/createResourceHooks.ts: consistent queryKey strategy, enable flags, queryClient.invalidateQueries on mutation success
podforge/ui/src/auth/oidc.ts: PKCE implementation with verifier/state storage, discovery, token exchange and explicit error checks
portfolio/src/hooks/useLeetCodeData.ts: fetch with loading/error states and JSON parsing
UX & Visual Polish
4/10
Look and feel quality
Visual polish and UX attention are evident in theme-first CSS, transition utilities and a pre-paint theme script, though there is limited evidence of comprehensive loading/error/skeleton patterns across components.
Evidence
portfolio/src/index.css: theme tokens, transition utilities and component classes (retro-card, retro-btn)
portfolio/index.html: inline script to set theme before paint to avoid flash
Expertise
React• Middle
Frontend Architecture & Build Tools• Middle
Industries
Information Technology• Middle
Technologies
JavaScript
TypeScript• Middle • 4y+
Node JS• Senior • 3y+
Tailwind CSS
React.js
Vite
React Query
Axios
Chakra UI
Element Plus
Recommendations
- Build admin UIs and dashboards that integrate with REST/SSE backends, especially cloud or Kubernetes management consoles.
- Implement complex SPA workflows with typed domain logic and server-state (resource CRUD, optimistic updates, background refreshes).
- Implement OAuth/OIDC integrations and secure auth flows for single-page apps and developer tooling frontends.
- Polish accessibility, testing and performance instrumentation (axe/lighthouse traces, CI a11y checks, bundle analysis) for production-readiness.
Middle Security Engineer
Confidence: Medium Cloud Security Engineer
Backend and cloud-focused developer (Middle) with practical experience building Go web services and deploying them to container/cloud platforms. The strongest proven skill is implementing application authentication and transactional service logic as shown in gin-fusion/backend/services/userService.go (bcrypt and JWT usage) and gin-fusion/backend/services/voteService.go (transaction handling and rollback). There is limited evidence of formal vulnerability analysis, detection engineering, comprehensive secrets management or automated security tests in public code.
Vulnerability Analysis
2/10
Finding security weaknesses
Minimal evidence of vulnerability analysis; infra-level controls like image scanning and deployment circuit breaker show operational security awareness but there is no formal root-cause analysis or PoC work.
Evidence
ecs-circuit-breaker/serverless.yaml: ecr.scanOnPush and DeploymentCircuitBreaker configuration
ecs-circuit-breaker/.gitlab-ci.yml: CI deploy pipeline invoking setAWSEnvironment.sh
Cryptography & Secure Protocols
4/10
Using encryption correctly
Uses standard primitives for password hashing and token signing (bcrypt and JWT) which is correct in principle, but key lifecycle and validation controls are minimal.
Evidence
gin-fusion/backend/services/userService.go: bcrypt.GenerateFromPassword and bcrypt.CompareHashAndPassword
gin-fusion/backend/services/userService.go: jwt.NewWithClaims and token.SignedString(os.Getenv("SECRET"))
gin-fusion/backend/go.mod: github.com/golang-jwt/jwt/v5 present in module dependencies
Offensive Security / Pentesting
Testing by attacking
Not evidenced in public code
Defensive Hardening
4/10
Making systems harder to break
Good practical hardening in places: deployment-time protections, CI/CD, middleware-based request authentication and transactional safeguards are present, but end-to-end security testing, secrets management and least-privilege enforcement need improvement.
Evidence
ecs-circuit-breaker/serverless.yaml: DeploymentCircuitBreaker and IAM role statements
gin-fusion/backend/router/router.go: middleware.AuthenticateRequest and SetTrustedProxies usage
gin-fusion/backend/services/voteService.go: explicit transaction handling with rollback on errors
Detection & Incident Response
Spotting and handling attacks
Not evidenced in public code
Compliance & Threat Modeling
1/10
Planning against threats
Very limited compliance or threat-modeling artifacts; some infra configuration reflects operational controls but no formal threat models, STRIDE/attack trees or audit-oriented documentation exist.
Evidence
ecs-circuit-breaker/serverless.yaml: DeploymentCircuitBreaker setting as an operational control
Expertise
Cloud & Container Security• Middle
DevSecOps & Cloud Security• Middle
Industries
Software• Middle
Technologies
Go• Senior • 3y+
Gin
GORM
Recommendations
- Harden secrets and deployment credentials: stop writing raw AWS credentials in scripts and rely on CI/CD secret stores or IAM role assumption; remove or redact committed ARNs, subnet and security group identifiers from public locations.
- Improve key management and token hygiene: validate presence and strength of the JWT secret at startup, consider rotating keys and evaluate asymmetric signing (RS256) or a managed secrets solution such as AWS Secrets Manager or HashiCorp Vault.
- Add security-focused tests and CI gates: unit and integration tests for auth flows, security regression tests for fixes, and automated SAST/secret-detection (gosec, trivy/grafeas) in the pipeline.
- Expand defensive telemetry and incident readiness: add structured logging for auth failures, instrument metrics/alerts in CI/CD and define simple runbooks for rollback and investigation scenarios.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: