Nemanja Nikolic
Fullstack
5+ years exp
Management: Under a year (6-15 people)
3+ projects
JavaScript
Node JS
SQL
Active 3 days ago
Invite to interview
Download CVCV
Overview
Technical skills
Projects
Timeline
Roles
Overview
Frontend app engineer (middle level) with practical experience building small interactive web apps and a browser-based game; the strongest proven skill is modular client-side state and async flow management demonstrated by the game modules with unit tests and a React useFetch hook that implements AbortController-based cancellation; what is not evidenced is large-scale architecture, measured performance tuning, robust accessibility on custom widgets, or production-grade backend integration patterns.
Phone
Technical skills
JavaScript
Node JS
SQL
Node JS
Axios
Dotenv
QA
Cypress
Jest
Frontend
React.js
React Router
Vite
Webpack
ESLint
Babel
DevOps
Rest API
GitHub
Databases
MySQL
Projects
IFTA mileage state calculator
Calculates miles per state based on the data that the ELD sent. It uses node's turf library to work with coordinates and calculate distance between each of them. GraphHopper is used to calculate big "jumps" between points.
Node JS
SQL
ELD odometer drop detector
It uses ELD providers platform to collect ELD data. It looks for OBD odometer drops, based on the odometer behavior, it finds problematic vehicles and bad packets.
Node JS
Timeline
Developer Assistant
•
Middle
Cortech
•
Full-Time
Worked as a developer assistant in Kragujevac, supporting the development team with implementation and debugging assistance. Contributed to resolving technical issues encountered during ongoing development work. Provided support related to production database usage when required.
Visoka škola strukovnih studija za informacione tehnologije ITS
Bachelor's Degree •
Informatics
Information and Communication Technology Intern
•
Junior
Fiat
•
Internship
Supported IT operations during an internship, including troubleshooting and maintaining systems. Assisted with installing and configuring hardware and software, and provided technical support to employees. Helped resolve IT-related issues and customer inquiries, including work with a production database and automating repetitive tasks.
Middle Backend Developer
Confidence: Medium Data Platform
Generalist developer at a Middle level focused on small-scale data processing and Node.js scripting with practical hands-on tooling experience. The strongest proven skill is geospatial ETL and telemetry processing as demonstrated by calculateIFTASkyonics.js and helpers/getCoordinatesSkyonics.js which stream CSV data, compute distances with turf, map points to states, and generate SQL output. Public code does not show production-grade API design, database migrations, formal testing, or hardened security and auth systems.
API Design
2/10
How well APIs are designed
Minimal API design evidenced by client-side direct fetches and simple request helpers; no versioning, idempotency, or formal error contracts are present.
Data Layer & Database
3/10
Working with databases
Clear ETL-style data processing and SQL generation for telemetry data including CSV streaming and geospatial lookups, but no migration history, transactional semantics, or DB schema evolution artifacts.
Evidence
TerminatorrT800/skyonics-ifta-calculator/calculateIFTASkyonics.js: writeSQLquery builds bulk INSERT strings and distance/state aggregation
TerminatorrT800/skyonics-ifta-calculator/helpers/getCoordinatesSkyonics.js: CSV streaming via fs.createReadStream and csv-parser to produce per-day coordinate arrays
Scalability & Performance
2/10
Handling load and speed
Some performance awareness (streaming CSV parsing), but no caching/invalidations, no queuing, no connection pooling or load-handling patterns.
System Architecture
2/10
Overall system structure
Small, well separated projects (front-end app, CLI data tool, weather UI) but no evidence of deliberate service decomposition, config/secret management, or graceful degradation design.
Security & Auth
2/10
Protecting data and access
Minimal security practices: some input trimming and abort handling exist, but authentication logic is insecure (plaintext user list/password check) and no token lifecycle, SQL escaping or input-sanitization for generated SQL.
Reliability & Observability
2/10
Stability and monitoring
Basic reliability patterns present (try/catch, AbortController), and console logging is used for observability; no structured logging, metrics, retries with backoff or graceful shutdown patterns are evident.
Expertise
Node.js• Middle
Industries
Transportation & Logistics• Middle
Technologies
Node JS• Middle
Rest API
Axios
Dotenv
Recommendations
- Develop ETL and CLI data processing pipelines for telematics or logistics workloads, improving robustness (validation, batching, idempotency).
- Build small REST services around the existing Node.js data logic, adding proper API contracts, input validation and token-based authentication.
- Improve reliability and observability by adding structured logging, retries with exponential backoff where appropriate, and basic metrics/alerts.
- Add unit/integration tests and a simple migration history for any database schema generated by the SQL output to support safe evolution.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle Frontend Developer
Confidence: High App Engineer
Frontend app engineer (middle level) with practical experience building small interactive web apps and a browser-based game; the strongest proven skill is modular client-side state and async flow management demonstrated by the game modules with unit tests and a React useFetch hook that implements AbortController-based cancellation; what is not evidenced is large-scale architecture, measured performance tuning, robust accessibility on custom widgets, or production-grade backend integration patterns.
UI Component Architecture
3/10
How interface parts are built
Component boundaries are modular and files are small and focused, but there is no evidence of a custom component library, design tokens, or advanced composition patterns; most UI is either plain DOM construction or simple React actions/hooks.
Evidence
Jest/src/index.js:createGrid
Blogs-Web-App/FrontEnd/react-app/src/useFetch.js:useFetch (custom hook)
Restaurant-page/src/menuPage.js:Menu (DOM-construction component)
Responsive & Cross-browser
2/10
Works on all screens and browsers
Styling is handcrafted and comprehensive for layouts, but there is little evidence of responsive strategies, feature detection, RTL/i18n readiness, or progressive enhancement.
Evidence
Blogs-Web-App/FrontEnd/react-app/src/index.css:global layout and component styles
Restaurant-page/src/style.css:full-page styling and layout
Performance Optimization
2/10
Speed of the interface
Small performance-aware choices exist (request cancellation), and modern tooling (Vite, webpack) is present, but there is no measured optimization, bundle analysis, virtualization, or non-trivial code-splitting shown.
Evidence
Blogs-Web-App/FrontEnd/react-app/src/useFetch.js:AbortController-based request cancellation
Blogs-Web-App/FrontEnd/react-app/vite.config.js:Vite plugin setup
Accessibility & Semantics
2/10
Usable for everyone
Some semantic HTML is used, but there is little visible a11y work on custom widgets (no ARIA, focus-management, keyboard support on custom controls) and no CI a11y tooling evident.
Evidence
Restaurant-page/src/template copy.html:semantic nav and buttons
Jest/src/index.js:modal overlay pattern (.modal-overlay and .hidden) but no focus management
State Management & Data Flow
4/10
Managing data in the app
Clear separation of server/state logic and UI exists with custom hooks and modular game state; request cancellation and route actions show thought for async flows, but there are no state machines, optimistic update rollbacks, or sophisticated cache invalidation.
Evidence
Blogs-Web-App/FrontEnd/react-app/src/useFetch.js:request cancellation and error/isPending state
Blogs-Web-App/FrontEnd/react-app/src/layouts/login/action.js:uses request.signal and server request flow
Jest/src/gameBoard.js + Jest/src/player.js + Jest/tests/ship.test.js:modular game state with unit tests
UX & Visual Polish
4/10
Look and feel quality
Good basic UX touches are present - modal configuration, toast feedback, loading/pending state tracking - but loading/error/empty states and accessibility/undo patterns are spotty and not consistently implemented across projects.
Evidence
Jest/src/index.js:configuration modal and game start/reset flow
Blogs-Web-App/FrontEnd/react-app/src/layouts/login/action.js:toast feedback on login success/error
Blogs-Web-App/FrontEnd/react-app/src/useFetch.js:isPending state exposed for loading UI
Expertise
React• Middle
Frontend Architecture & Build Tools• Middle
HTML & CSS• Middle
Technologies
Webpack
Babel
React.js
Vite
ESLint
React Router
Recommendations
- Develop interactive single-page applications or medium-sized React features that need clean client-side state and request cancellation handling.
- Build and harden small browser games or simulation UIs where game logic is isolated from rendering and covered by unit tests.
- Migrate projects to production readiness by adding CI, measured performance (bundle analysis), and end-to-end/a11y tests.
- Work on component-driven UI libraries and accessibility improvements to elevate visual components into reusable, tested primitives.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle QA Engineer
Confidence: Medium Generalist
Frontend JavaScript developer (middle) focused on small, unit-tested interactive browser features and game logic. The strongest proven skill is implementing unit tests for core logic using Jest as shown in tests/ship.test.js. The public code shows limited test infrastructure, no CI pipelines, and no API or performance testing artifacts.
Test Automation Frameworks
3/10
Building automated tests
Basic unit test automation is present using Jest with a project-level config and test script, but there is no custom fixture infrastructure, no test factories, no mock servers, and no parallelization or selector discipline beyond simple unit tests.
Test Coverage & Strategy
2/10
What and how to test
There are meaningful unit tests covering game logic and some negative/happy paths, but there is no risk-based test structuring, no tagging (smoke/critical/regression), no property-based or boundary-invariant tests, and assertions are focused on basic outcomes.
API & Integration Testing
Testing how parts work together
Not evidenced in public code
Performance & Load Testing
Testing speed under load
Not evidenced in public code
Bug Reporting & Analysis
Finding and describing bugs
Not evidenced in public code
CI Test Integration
2/10
Running tests automatically
Basic test execution integration exists via npm scripts and a Jest config, but there is no CI workflow, no test matrix, no per-test retry policy, and no artifact capture or quarantine mechanics.
Expertise
Unit & Component Testing• Middle
Technologies
JavaScript• since 2021 • Middle
Jest• since 2025 • 1 project
Recommendations
- Develop unit-tested front-end game logic and interactive components with Jest and increase test invariants and boundary cases.
- Implement small-scale test infrastructure improvements such as fixtures/factories, clearer negative-path tests, and structured test tags (smoke/critical/regression).
- Add CI integration (GitHub Actions or similar) to run tests and capture artifacts, and introduce simple linting and automated checks to catch typos and alert text issues.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: