Ihnat Baikou
Java Developer
Node JS
Kotlin
JavaScript
SQL
Java
PHP
TypeScript
Active 9 days ago
+48 (794) 538777 Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
App-focused frontend engineer (middle level) specializing in building stateful React and Next.js business applications. The strongest proven skill is client-server state and data-flow design as demonstrated by the React Query hooks and invalidation logic in Cringenut/tapi-frontend/features/staff/hooks/useStaffAvailability.ts and the centralized reducer/context in Cringenut/ProductManagementApp/src/app/context/ProductContext.js. The public code has limited measured performance work, limited accessibility engineering and lacks automated tests or advanced cross-browser and internationalization handling.
Technical skills
Node JS• Middle
Kotlin
JavaScript
SQL• Junior • 3y+
Java• Middle • 3y+
PHP• Middle • 3y+
TypeScript• Middle
Node JS
Axios
Kotlin
Mockito
Java
Hibernate
Spring Cloud
Spring Security
Flyway• 3y+
Spring Boot• 3y+
Databases
Apache Kafka
MySQL
PostgreSQL• 3y+
Redis• 3y+
Frontend
Bootstrap
Next.js
React.js
Tailwind CSS
Three.JS
PostCSS
React Query
Formik
Yup
DevOps
AWS
CI/CD
Docker
Git
Kubernetes
Mobile
JUnit
Timeline
Software Developer (Guidewire, Java/Gosu)
•
Middle
Sollers Consulting
•
Full-Time
Delivered policy administration and underwriting features on a Guidewire PolicyCenter platform for an international P&C insurer. Built and maintained REST and SOAP integrations to connect the policy core with rating, document generation, and payment systems. Implemented data migration and mapping logic from legacy systems with validation to preserve data integrity. Wrote automated unit and integration tests to improve release stability and reduce regressions.
Java
JUnit
Polish-Japanese Academy of Information Technology
Bachelor's Degree •
Computer Science, specialization in Web Applications
Junior Java Developer
•
Junior
Matseboss Solutions
•
Full-Time
Built a secure Spring Boot backend with PostgreSQL schema setup and Flyway-based database migrations. Implemented a currency exchange service with scheduled external rate synchronization, Redis caching, and resilience for upstream provider outages. Standardized API responses and exception handling to improve HTTP status correctness. Added automated unit and integration test coverage across authentication, caching behavior, and critical endpoints.
Spring Boot
PostgreSQL
Flyway
Redis
Javasince 2023
Java Developer Intern
•
Junior
eGodziny
•
Internship
Optimized SQL queries and improved database indexing for high-traffic operational endpoints to reduce response times. Redesigned the logging approach to support centralized log aggregation and faster incident triage. Contributed to an HR automation SaaS platform for temporary employment agencies, supporting time tracking and operational coordination.
SQL
Middle Backend Developer
Confidence: Medium API Engineer
A web-focused backend-capable developer (approx junior-to-middle level) who builds API-integrated frontends and small server-side PHP features. The strongest proven skill is integrating authentication and role-based routing in a Next.js app using NextAuth/Keycloak and middleware (lib/auth.ts and middleware.ts). There is limited evidence of backend-grade data engineering, secure database access patterns, migrations, or production-grade reliability and observability instrumentation.
API Design
3/10
How well APIs are designed
API integration and client-side API patterns are present (react-query, clear endpoint usage), but there is no formal API versioning, idempotency, or documented error contract.
Evidence
Cringenut/tapi-frontend/features/staff/hooks/useStaffAvailability.ts: useQuery/useMutation with endpoint calls like GET /staff/availability/my-schedule and invalidateQueries on success
Cringenut/tapi-frontend/features/client/hooks/useCreateBooking.ts: POST /appointments/book?slotId=... and query invalidation of appointments and staff-slots
Cringenut/tapi-frontend/features/client/hooks/useClientBookings.ts: GET /appointments/my-bookings/{clientId} with enabled flag
Data Layer & Database
2/10
Working with databases
Direct DB usage exists (mysqli) but shows basic connectivity and inline SQL without migration history, transactions, or protection against SQL injection.
Scalability & Performance
3/10
Handling load and speed
Some client-side caching and performance patterns are used (react-query, useMemo, localStorage caching), but no systematic scalability design (no queues, rate limiting, or measured optimizations).
System Architecture
3/10
Overall system structure
Reasonable module boundaries and role-based routing are implemented (middleware, auth module, product context), but architecture is primarily single-service/front-end oriented without cross-service decomposition or ops concerns.
Security & Auth
3/10
Protecting data and access
Authentication and role checks are explicitly handled on the front end (NextAuth + Keycloak, middleware). However server-side security and input sanitization are weak in the PHP code, and there is no evidence of token lifecycle management or threat mitigation beyond basic checks.
Evidence
Cringenut/tapi-frontend/lib/auth.ts: NextAuth Keycloak provider, JWT and session callbacks, environment-secret usage
Cringenut/tapi-frontend/middleware.ts: middleware enforces role-based access to /staff and /client pages
Cringenut/Calculator/classes.php: raw use of $_POST and mysqli string concatenation (SQL injection risk)
Reliability & Observability
2/10
Stability and monitoring
Minimal reliability and observability patterns: some onError handling and user alerts exist, but there are no structured logs, metrics, retries with backoff, timeouts, or graceful shutdown handling.
Expertise
Node.js• Middle
PHP• Junior
Databases & Vector Storage• Junior
Technologies
Java• Middle • 3y+
PHP• Middle • 3y+
Kotlin
SQL• Junior • 3y+
MySQL
PostgreSQL• 3y+
Redis• 3y+
Spring Boot• 3y+
Hibernate
CI/CD
Mockito
Git
AWS
Docker
Kubernetes
Apache Kafka
Spring Security
Spring Cloud
Flyway• 3y+
Recommendations
- Maintain and extend API-integrated frontends and small backend endpoints where Keycloak/NextAuth-based auth and role routing are required.
- Work on PHP maintenance tasks and small feature work for legacy MySQL-backed apps while refactoring unsafe SQL to parameterized queries.
- Build single-service REST APIs or BFFs that require integration testing, request validation, and client caching strategies using react-query.
- Implement basic reliability and security upgrades: input validation, prepared statements, structured logging, and retry/backoff for network calls.
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
App-focused frontend engineer (middle level) specializing in building stateful React and Next.js business applications. The strongest proven skill is client-server state and data-flow design as demonstrated by the React Query hooks and invalidation logic in Cringenut/tapi-frontend/features/staff/hooks/useStaffAvailability.ts and the centralized reducer/context in Cringenut/ProductManagementApp/src/app/context/ProductContext.js. The public code has limited measured performance work, limited accessibility engineering and lacks automated tests or advanced cross-browser and internationalization handling.
UI Component Architecture
3/10
How interface parts are built
Component composition and a shared context are used to structure UI, but there is no custom design system or clear component library engineering; components are conventional and mostly page-specific.
Responsive & Cross-browser
2/10
Works on all screens and browsers
Basic responsive styling via Tailwind and CSS variables exists, but there is no advanced responsive strategy, container queries, RTL or explicit cross-browser feature-detection.
Performance Optimization
3/10
Speed of the interface
Some reasonable performance-minded choices such as useMemo and client-side caching with React Query and selective query enabling are present, but there is no measured before/after optimization, bundle analysis, virtualization in the shown components or advanced render-profiling.
Accessibility & Semantics
2/10
Usable for everyone
Minimal accessibility work detected - basic labels and form validation exist but there is no ARIA on custom widgets, focus-management, keyboard handling, or automated a11y checks; global CSS even removes button outlines which weakens keyboard focus visibility.
State Management & Data Flow
4/10
Managing data in the app
Clear, practical server-state discipline with React Query (queries, mutations, invalidation and enabled flags) alongside local state via useReducer/useContext and localStorage persistence; error handling is present though not exhaustive and advanced patterns like cancellation or state machines are limited.
UX & Visual Polish
3/10
Look and feel quality
UX attention includes transitions, form validation, and a notification system plus sync fallback to localStorage, but the project lacks skeletons, progressive loading patterns, undo flows and richer perceived-performance techniques.
Expertise
React• Middle
Modern Web Frameworks• Middle
HTML & CSS• Middle
Technologies
JavaScript
TypeScript• Middle
Node JS• Middle
Tailwind CSS
Next.js
Three.JS
Bootstrap
React.js
React Query
Axios
PostCSS
Formik
Yup
Recommendations
- Develop and maintain multi-page business SPAs that need role-based auth, server-state caching and CRUD flows - implement booking, scheduling or admin dashboards.
- Build admin dashboards and sync/offline flows that combine React Query with local persistence and background sync.
- Improve accessibility and QA by adding ARIA/focus management, keyboard interactions and automated a11y checks in CI.
- Own form-heavy interfaces and validation flows using Formik/Yup and central context patterns.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle Blockchain Developer
Confidence: Medium Generalist
Frontend engineer focused on React/Next.js applications at a middle level with a practical strength in building stateful UIs and integration with authentication flows. The strongest proven skill is implementing application-level auth and role-based routing as shown in lib/auth.ts (NextAuth + Keycloak callbacks) and middleware.ts (role redirects). There is little or no evidence of blockchain, smart-contract, tokenomics, or decentralized governance work in the public code.
Smart Contract Development
Writing smart contracts
Not evidenced in public code
Security & Audit
2/10
Checking contracts for flaws
Basic security and access-control patterns are present (Keycloak via next-auth, role-based middleware, some error handling) but no audit tooling, invariant/fuzz tests, or protocol-security-specific checks.
Evidence
Cringenut/tapi-frontend/lib/auth.ts: NextAuth Keycloak provider and jwt/session callbacks implementing token roles
Cringenut/tapi-frontend/middleware.ts: role-based routing enforcing STAFF vs client access
Cringenut/tapi-frontend/features/staff/hooks/useStaffAvailability.ts: onError handling with network and 403 checks
Blockchain Protocol Understanding
Knowing how blockchains work
Not evidenced in public code
DApp & Web3 Integration
2/10
Connecting apps to blockchain
Frontend integration experience is shown (next-auth, react-query, api-client usage, form validation), but there is no Web3-specific dApp work (wallets, EIP-712, subgraph mappings) to demonstrate dApp expertise.
Tokenomics & DeFi Logic
Token and finance logic
Not evidenced in public code
Decentralization & Trust Model
1/10
Designing trust without middlemen
Some centralized trust-model handling (Keycloak config and middleware redirects) is implemented, but there is no governance, upgrade lifecycle, multisig or documented trust assumptions.
Recommendations
- Build internal SaaS dashboards and appointment/product management frontends using Next.js, React Query and NextAuth (Keycloak) where their current patterns directly apply.
- Implement and own authentication and authorization integrations (Keycloak/OIDC) and role-based middleware for enterprise web apps.
- Harden frontend code by adding automated tests (unit and integration), CI linting, and replace console/alert debugging with structured error reporting.
- Move environment-specific values (Keycloak issuer, API base URLs) out of code into environment/secret stores and add runtime configuration validation.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: