Samuel Orogun
Backend Developer
4+ projects
PHP
JavaScript
Node JS
TypeScript
Responsive & Cross-browser: 4/10
State Management & Data Flow: 4/10
UX & Visual Polish: 4/10
Active 1 day ago
Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
A frontend app engineer at a Middle level specializing in building interactive React and Next.js applications with practical client-side state management. The strongest proven skill is client-state architecture and persistence shown by audiophile/src/app/store/cartStore.ts implementing a persisted Zustand cart with snapshot and derived helpers. There is little public evidence of automated tests, advanced performance measurement or comprehensive accessibility work and no signs of large-scale system architecture design.
Technical skills
PHP
JavaScript• Junior
Node JS
TypeScript• Junior
Node JS
Express
Frontend
Vue.js
PostCSS
Zustand
Vite
Material UI
ESLint
Framer Motion
Next.js
React.js
Tailwind CSS
DevOps
Rest API
Git
CI/CD
Design
Figma
QA
Postman
Databases
MongoDB• 4 projects
Timeline
Web Development Intern & Team Lead
•
Lead
Tech Studio Academy
•
Internship
Led a cross-functional effort to partially redesign the Nigeria Immigration Service website, coordinating sprint cycles and daily stand-ups to hit milestones. Implemented a secure authentication system with login, registration, and password reset, including role-based access control. Translated high-fidelity Figma designs into responsive, accessible UI using React and Tailwind, and validated backend endpoints with Postman while maintaining code quality via Git workflows.
React.js
Node JS
Express
Tailwind CSS
Postman
Git
Figma
University of Ilorin
Bachelor's Degree •
Chemical Engineering
Frontend Developer Intern
•
Junior
HNG 13
•
Internship
Built a full-featured event ticketing application with interactive UI patterns and state management. Developed an Audiophile e-commerce platform in Next.js with TypeScript, adding dynamic product filtering, cart persistence, and checkout flow optimizations. Implemented responsive, accessible UI components using semantic HTML practices.
Next.js
TypeScript
Middle Frontend Developer
Confidence: Medium App Engineer
A frontend app engineer at a Middle level specializing in building interactive React and Next.js applications with practical client-side state management. The strongest proven skill is client-state architecture and persistence shown by audiophile/src/app/store/cartStore.ts implementing a persisted Zustand cart with snapshot and derived helpers. There is little public evidence of automated tests, advanced performance measurement or comprehensive accessibility work and no signs of large-scale system architecture design.
UI Component Architecture
2/10
How interface parts are built
Limited direct evidence of component architecture or custom component libraries; code shows modular state but not component composition patterns or a design system authored by the developer.
Evidence
audiophile/src/app/store/cartStore.ts: centralised Zustand store encapsulating actions and state
my-portfolio/eslint.config.js: project-level linting config indicating some engineering discipline
Responsive & Cross-browser
4/10
Works on all screens and browsers
Responsive assets and theming are considered with multi-breakpoint ImageSet types and dark-mode support, but no advanced layout techniques or RTL/i18n patterns are present.
Evidence
audiophile/src/app/types.ts: ImageSet type with mobile/tablet/desktop fields
audiophile/src/app/globals.css: prefers-color-scheme media query and CSS variables for theming
Performance Optimization
2/10
Speed of the interface
Minor performance-aware choices (persist partialization, mobile asset selection) are present; no measured optimizations, bundle analysis, code-splitting strategy or virtualization evidence.
Evidence
audiophile/src/app/store/cartStore.ts: persist middleware with partialize to only persist needed state
my-portfolio/vite.config.js: Vite plugin usage (basic build tooling present)
Accessibility & Semantics
2/10
Usable for everyone
Basic semantic and browser-friendly elements are present (lang attribute, viewport, color-scheme respect) but there is little explicit accessibility work on custom widgets or ARIA/keyboard management.
Evidence
my-portfolio/index.html: html lang="en" and viewport meta tag
audiophile/src/app/globals.css: prefers-color-scheme handling for dark/light modes
State Management & Data Flow
4/10
Managing data in the app
Clear, practical client-side state management with persisted store, derived helpers and edge handling (remove on zero quantity); shows end-to-end flow design for cart interactions but lacks advanced server-state discipline or request-cancellation patterns.
Evidence
audiophile/src/app/store/cartStore.ts: Zustand store with actions (addItem, updateQuantity, snapshotCart, persist middleware)
audiophile/src/app/types.ts: typed Product and CartItem models supporting the state logic
UX & Visual Polish
4/10
Look and feel quality
Visual polish and deliberate styling choices are evident (glassmorphism utilities, subtle noise overlay, theme variables), indicating attention to perceived quality though not paired with advanced UX patterns like undo, skeleton-state or motion-driven performance tuning in the shown files.
Evidence
my-portfolio/src/index.css: .bg-noise texture and .glass-panel utilities
audiophile/src/app/globals.css: CSS variables and theme-aware defaults
Expertise
React• Middle
Modern Web Frameworks• Middle
Industries
Commerce• Middle
Technologies
TypeScript• Junior
Node JS
Rest API
Vue.js
Zustand
Tailwind CSS
Next.js
Express
Figma
Git
React.js
Vite
Material UI
PostCSS
ESLint
Framer Motion
Recommendations
- Develop consumer e-commerce frontends and checkout flows where the existing cart/state expertise is directly useful.
- Ship small-to-medium Next.js apps that need pragmatic client-state persistence, inventory of UI states and typed data models.
- Extend the codebase with automated tests and CI checks to demonstrate robustness and raise the engineering tier.
- Invest in measured performance work (LCP/INP audits, bundle analysis) and explicit a11y fixes for custom widgets to strengthen production-readiness.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Junior QA Engineer
Confidence: Medium Generalist
Front-end developer at Junior level specializing in React/Vite project setup and configuration. The strongest proven skill is setting up front-end build and lint infrastructure as shown by vite.config.js and eslint.config.js. There is no public evidence of test automation, API or contract tests, CI workflows, or performance testing in the provided code.
Test Automation Frameworks
1/10
Building automated tests
Almost no test automation framework present; only project config files for linting and build are available without fixtures, test runners or page objects.
Test Coverage & Strategy
1/10
What and how to test
No visible test coverage or risk-based test strategy; there are no test scripts, classification tags, property-based tests or mutation testing artifacts.
API & Integration Testing
1/10
Testing how parts work together
No API or contract testing evidence; the codebase is front-end configuration only and lacks schema validation, contract tests or integration testcontainers.
Performance & Load Testing
1/10
Testing speed under load
No performance or load testing artifacts such as k6, Locust, Gatling scenarios or SLO/threshold checks were found.
Bug Reporting & Analysis
1/10
Finding and describing bugs
No reproducible bug reports, changelogs, or root cause analysis artifacts are present in the inspected code; only configuration and build files are available.
CI Test Integration
1/10
Running tests automatically
No CI workflow or test integration artifacts were found; repository shows local scripts (dev/build/lint/preview) but no CI matrices, failure artifact collection or quarantine policies.
Technologies
JavaScript• Junior
Postman
Recommendations
- Develop small-to-medium React websites and component-based landing pages using Vite and Tailwind where build and lint configuration matter.
- Improve value by adding a test scaffold: unit tests, simple E2E flows and a CI workflow that runs lint and tests on push.
- Migrate a project to TypeScript and add basic API contract checks or schema validations to broaden integration testing experience.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Junior Game Developer
Confidence: Medium Generalist
Front-end web developer (Junior) specializing in React and modern JavaScript build tooling. The strongest proven skill is configuring JavaScript toolchains and linting, backed by concrete artifacts such as vite.config.js and eslint.config.js in the projects. There is no evidence of game-development systems, rendering/shader work, physics, netcode, or performance profiling in the public human-authored files.
Gameplay Systems & Mechanics
How game logic works
Not evidenced in public code
Graphics & Rendering
Drawing game visuals
Not evidenced in public code
Physics & Math
Game physics and math
Not evidenced in public code
Engine Proficiency
2/10
Skill with the game engine
Basic toolchain and build configuration proficiency shown through Vite plugin usage and ESLint configs, indicating familiarity with modern JS build tooling but not deep engine work.
Evidence
samadeola1/my-portfolio/vite.config.js: defineConfig with @vitejs/plugin-react and @tailwindcss/vite plugin usage
samadeola1/my-portfolio/eslint.config.js: exported ESLint defineConfig using @eslint/js, globals and react plugins
samadeola1/my-portfolio/package.json: dependencies and devDependencies declaring Vite, React and ESLint toolchain
Performance & Frame Budget
Keeping the game smooth
Not evidenced in public code
Content Pipeline & Tooling
2/10
Tools for game content
Basic content pipeline and developer tooling artifacts exist such as package.json manifests, ESLint configuration and Vite config files showing automation for front-end projects.
Evidence
samadeola1/Personal-portfolio/package.json: project dependency list and devDependencies for build and lint tooling
samadeola1/Blog-landing-page/package.json: similar build and dependency manifest
samadeola1/my-portfolio/eslint.config.js: lint rules and plugin configuration for automated code quality
Recommendations
- Develop marketing sites, portfolios, and small React-based single page applications using Vite and Tailwind.
- Implement and maintain front-end build tooling, linting rules and CI checks for web projects.
- Harden skills in front-end performance and profiling by adding measured optimizations and documenting before/after profiler captures.
- If moving toward game tools or game UI, build small interactive prototypes that add deterministic update loops, input handling, and documented performance budgets
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: