Robert-Petrica Gherman
Full Stack Developer
4+ years exp
2+ projects
C++
Python
SQL
C
JavaScript
Node JS
TypeScript
Active 7 days ago
+40 (775) 360569 Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
A Middle-level backend-focused Node.js engineer who builds small end-to-end JavaScript services and integrations with pragmatic, working implementations. The strongest proven skill is delivering simple REST endpoints backed by PostgreSQL with conditional upsert logic, demonstrated in werwaldo/database/databasepg.js. There is limited evidence of production practices such as migrations, connection pooling, observability, automated tests, or robust security hygiene.
Technical skills
C++
Python
SQL
C
JavaScript• Middle • 4y+
Node JS• Middle • 2 projects
TypeScript• Middle
Node JS
Express
Cheerio
Puppeteer
Strapi
Axios• 2 projects
Databases
PostgreSQL• 1 project
MySQL• 1 project
Frontend
npm
Webpack
Redux
Redux Toolkit
Tailwind CSS
Vite
i18next
Material UI
Zustand
React.js• 5y+
Angular
Next.js
DevOps
CI/CD
Git
Rest API
Docker
Design
Figma
AI/ML
AI Agents
ChatGPT
Claude
Gemini
Scikit-learn
DeepSeek
Cybersecurity
Okta
Auth0
Mobile
React Native
QA
Swagger
Timeline
Full-Stack Developer
•
Middle
Magic Romania
•
Full-Time
Re-architected and migrated the core frontend to Next.js, redesigning UI/UX for a modern responsive experience. Built and maintained an enterprise CRM/ERP dashboard using React and NestJS, including an internal scheduling panel. Consolidated appointment logic into a unified table to improve consistency and query performance, and integrated an AI chatbot (DeepSeek) to generate Jira tickets conversationally.
Next.js
React.js
Nest.JS
DeepSeek
Jira
Frontend Code Reviewer
•
Middle
ScaleAI
•
Full-Time
Created and refined frontend development prompts in JavaScript and modern web frameworks to support AI model training. Reviewed AI-generated code for correct component structure, reduced unnecessary renders, semantic HTML, and WCAG accessibility. Validated outputs by running generated code in sandbox environments and refactoring inefficient logic such as redundant state updates and unoptimized list rendering.
JavaScript
React.js
Angular
Next.jssince 2025
TypeScript
Frontend Developer – Authentication
•
Middle
ComputerGeneratedSolutions
•
Full-Time
Integrated Auth0 SDK into client applications, configuring tenant settings, callback URLs, audience parameters, and token handling. Implemented SSO using SAML identity provider connections and OpenID Connect flows, mapping user attributes to enable unified login. Added multi-factor authentication methods (TOTP, push, WebAuthn) and handled secure domain validation and related account setup workflows.
Auth0
Jirasince 2024
Web Developer
•
Middle
Atos IT Solutions and Services
•
Full-Time
Developed and maintained internal React applications for enterprise operational processes. Built reusable component libraries with consistent interfaces to improve code reuse across multiple projects. Consumed REST APIs using Axios with centralized error handling and loading-state management while participating in Agile/Scrum delivery cycles.
React.jssince 2021
Axios
Middle Backend Developer
Confidence: Medium API Engineer
A Middle-level backend-focused Node.js engineer who builds small end-to-end JavaScript services and integrations with pragmatic, working implementations. The strongest proven skill is delivering simple REST endpoints backed by PostgreSQL with conditional upsert logic, demonstrated in werwaldo/database/databasepg.js. There is limited evidence of production practices such as migrations, connection pooling, observability, automated tests, or robust security hygiene.
API Design
3/10
How well APIs are designed
Basic REST API endpoints present with some idempotent upsert logic, but no versioning, pagination, or consistent error contract; API surface is small and mostly CRUD-style.
Evidence
werwaldo/database/databasepg.js: GET /getWaldo and POST /addToLeaderboard endpoints with parameterized INSERT and ON CONFLICT upsert
webscrapper/api/server.js: GET /scraped-data endpoint and swagger UI mounting at /api-docs
Data Layer & Database
3/10
Working with databases
Shows awareness of SQL features (conditional ON CONFLICT upsert) and parameterized queries, but lacks migration history, connection pooling, and schema evolution artifacts.
Evidence
werwaldo/database/databasepg.js: parameterized INSERT ... ON CONFLICT (username) DO UPDATE SET score = EXCLUDED.score WHERE EXCLUDED.score > leaderboard.score RETURNING *
werwaldo/database/databasepg.js: use of pg Client (no Pool) and direct client.connect()
Scalability & Performance
2/10
Handling load and speed
No caching, no background/queue-based decoupling, and Playwright is launched per request which does not scale; performance considerations are minimal.
Evidence
webscrapper/api/server.js: Playwright browser/context/page created inside request handler for /scraped-data
werwaldo/database/databasepg.js: direct pg Client usage (no pooling or connection reuse)
System Architecture
2/10
Overall system structure
Project is a small multi-folder codebase with separation of concerns (frontend, backend, DB), but no deliberate service decomposition, config management, or production-ready architecture patterns.
Evidence
repository structure: werwaldo/database, werwaldo/src/hooks and webscrapper/api (separate service folders)
werwaldo/vite.config.js and webscrapper/api/server.js show clear frontend/backend separation but no inter-service contracts or deployment orchestration
Security & Auth
2/10
Protecting data and access
Some authentication work exists on the frontend (Google OAuth hook), and parameterized queries reduce SQL injection risk in one endpoint, but there are hardcoded secrets and little server-side auth or input validation.
Evidence
werwaldo/src/hooks/useGoogleAuth.js: frontend Google OAuth usage and token fetch from Google APIs
werwaldo/database/databasepg.js: hardcoded DB credentials in client configuration
Reliability & Observability
2/10
Stability and monitoring
Minimal reliability and observability: simple console logging and basic error responses are present, but no structured logging, metrics, retries, timeouts, or graceful shutdown handling.
Evidence
werwaldo/database/databasepg.js: console.error on DB errors and simple 500 responses
webscrapper/api/server.js: console.log(scrapedData) and no retry/backoff or timeout management for network/browser calls
Expertise
Node.js• Middle
Microservices & API Architecture• Middle
Databases & Vector Storage• Middle
Industries
Gaming• Middle
Technologies
PostgreSQL• 1 project
Puppeteer
Cheerio
Recommendations
- Implement environment-driven configuration and remove hardcoded secrets; migrate DB credentials to environment variables and use connection pooling (pg Pool).
- Add schema migrations and version history (e.g., migrate or a SQL migration tool) and document schema evolution for the leaderboard and waldo tables.
- Improve reliability for heavy operations by moving Playwright scraping into background workers/queues and adding retries, timeouts, and concurrency controls.
- Introduce structured logging, basic metrics, and graceful shutdown handling to make services production-ready.
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
Frontend app engineer (approx mid-level) focused on building React single page apps with practical state and integration work. The strongest proven skill is building SPA data flows and checkout/booking integrations, demonstrated by the Redux Toolkit slice (dropship-master/client/src/state/index.js) and Strapi order controller that creates Stripe sessions (dropship-master/server/src/api/order/controllers/order.js). Public code shows limited evidence of performance engineering, automated tests, and robust advanced frontend architecture patterns such as request cancellation or state machines.
UI Component Architecture
4/10
How interface parts are built
Component-level structure is practical and reusable for SPA features but relies on standard patterns and some anti-patterns rather than a deliberate component system design.
Responsive & Cross-browser
3/10
Works on all screens and browsers
Basic responsive tooling and theming are present using Tailwind and CSS variables, but there is little advanced responsive strategy or explicit RTL/i18n fallbacks beyond i18n setup.
Performance Optimization
2/10
Speed of the interface
No measurable performance work or instrumentation is present; typical client-side patterns are used without virtualization, explicit code-splitting strategy, or performance audits.
Accessibility & Semantics
3/10
Usable for everyone
Some accessibility and semantics are considered in places (forms with labels, visible role attributes, aria-hidden on icons) and an i18n setup exists, but many components lack robust focus management and ARIA on custom controls.
State Management & Data Flow
4/10
Managing data in the app
Reasonable state and server-state handling for typical e-commerce and booking flows using Redux Toolkit, async fetch patterns and Strapi controller logic, but missing advanced server-state discipline like request cancellation or optimistic updates.
UX & Visual Polish
3/10
Look and feel quality
UX work demonstrates practical features - search, filtering, date pickers and form flows - but lacks systematic edge-state UXs such as skeleton screens, consistent loading/error states, and undo patterns.
Expertise
React• Middle
Industries
Commerce• Middle
Transportation & Logistics• Middle
Technologies
TypeScript• Middle
Node JS• Middle • 2 projects
Zustand
Redux
Webpack
Tailwind CSS
Next.js
Express
Figma
Angular
React.js• 5y+
Vite
npm
Strapi
Axios• 2 projects
Material UI
i18next
Redux Toolkit
Recommendations
- Lead development of small to medium React single page applications that require routing, forms and integration with REST/third-party APIs such as Stripe or mapping services.
- Implement e-commerce checkout and booking flows that need pragmatic server-client integration and state management using Redux Toolkit or Zustand.
- Work on frontend feature development for consumer web products where quick iteration and direct API integration matter, including localization and MUI/Tailwind UI implementation.
- Improve component libraries and UX edge states by adding systematic loading/error states, accessibility checks and performance budgets.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle Game Developer
Confidence: Medium Generalist
Fullstack web developer focused on small web games and data-driven frontends at a middle-junior level with practical backend and frontend integration experience. The strongest proven skill is backend and database integration demonstrated by werwaldo/database/databasepg.js which implements leaderboard endpoints and an SQL upsert using ON CONFLICT. There is no evidence of game-engine work, custom rendering or physics simulation and no test coverage or measured performance optimization in public code.
Gameplay Systems & Mechanics
1/10
How game logic works
Very limited gameplay systems; only backend leaderboard and auth support are present rather than in-game state machines or mechanics.
Evidence
werwaldo/database/databasepg.js: POST /addToLeaderboard with SQL upsert using ON CONFLICT
werwaldo/src/hooks/useGoogleAuth.js: OAuth login hook fetching Google profile
Graphics & Rendering
1/10
Drawing game visuals
No custom rendering or shader work; styling uses Tailwind configuration and theme extensions only.
Evidence
FlightTracker/tailwind.config.js: theme extensions and animations
werwaldo/tailwind.config.js: custom color palettes and safelist
Physics & Math
1/10
Game physics and math
No physics, integrators or deterministic simulation; only geographic coordinate data is present for mapping visualizations.
Evidence
FlightTracker/src/mockData.ts: flights array with latitude/longitude coordinates and origin/destination structures
FlightTracker/src/mockData.ts: first100FLights dataset with flight schedule and location fields
Engine Proficiency
2/10
Skill with the game engine
Basic proficiency with web build tooling and framework configuration; Vite aliasing and i18n initialization indicate practical use of the web stack beyond defaults but no game engine work.
Evidence
FlightTracker/vite.config.ts: defineConfig with path aliases for project structure
FlightTracker/src/i18n/i18n.ts: i18next + react-i18next initialization and locale utils usage
Performance & Frame Budget
1/10
Keeping the game smooth
Little to no evidence of measured performance work or zero-allocation hot paths; standard server endpoints and build config are present without profiling or optimization artifacts.
Evidence
FlightTracker/src/server.js: Express endpoints with try/catch but no profiler/instrumentation
FlightTracker/vite.config.ts: custom aliasing but no build-time performance metrics or optimizations
Content Pipeline & Tooling
2/10
Tools for game content
Basic content and tooling pipeline setup for web projects is present including NPM scripts, PostCSS and Tailwind; no CI, import processors or advanced asset pipelines evident.
Evidence
FlightTracker/package.json: scripts for dev, build, lint, format and use of Prettier/ESLint
werwaldo/postcss.config.js: tailwindcss and autoprefixer plugin configuration
Industries
Gaming• Middle
Technologies
JavaScript• Middle • 4y+
Recommendations
- Use this developer to build small to medium web game prototypes that require frontend React UI, Google OAuth and a simple Postgres-backed leaderboard.
- Assign them to implement web mapping or data-visualization frontends that consume flight or geolocation data, leveraging the existing mockData and React/Vite setup.
- Have them extend backend integrations and API endpoints for data-driven apps, improving error handling, input validation and adding automated tests.
- Pair them with a senior engineer to harden performance and introduce CI, profiling, and deployment pipelines for production readiness.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: