Max Penkin
Node JS
Python
TypeScript
Data Pipeline & Feature Engineering: 4/10
Active 16 days ago
Invite to interview
Message
Download CVCV
Overview
Technical skills
Roles
Overview
A backend-focused engineer with senior-level evidence in fault-tolerant payment integrations and API design. The strongest proven skill is payment and fulfillment engineering with transactional claim patterns and idempotent webhook handling as implemented in apps/web/lib/jobs/issue-card.ts and the payments clients. Public code lacks large-scale performance measurement artifacts and explicit multi-service contracts for a distributed microservices mesh.
Technical skills
Node JS• Junior
Python• Junior
TypeScript
Node JS
BullMQ
Express
Nest.JS
Prisma
Axios
Python
aiogram
Asyncio
FastAPI
Aiohttp
Databases
PostgreSQL
Redis
SQLite
AI/ML
AI/ML
OpenAI SDK
Anthropic SDK
Frontend
Next.js
React.js
Tailwind CSS
Vite
pnpm
Zod
Turborepo
DevOps
Docker Compose
Junior AI/ML Engineer
Confidence: Low LLM Engineer
An experienced LLM-focused engineer with strong production experience building Telegram-based conversational systems and agent-driven automation; level is senior by demonstrated system design and operational fixes. The clearest proven skill is engineering reliable agent-to-backend workflows and payment/DB transactional correctness, evidenced by db/queries.py, numerous integration tests under bot/tests, and handlers that implement subscription, payment and webhook logic. There is little or no evidence of custom model training, GPU/quantization work, or formal ML experiment infrastructure in public code.
Model Architecture & Training
1/10
How well models are designed and trained
No evidence of custom model architectures or training pipelines; work is primarily prompt/agent engineering and hosted LLM integration rather than model development.
Evidence
bot-smm/src/agent/prompts.py
bot-smm/src/agent/news_agent.py
Data Pipeline & Feature Engineering
4/10
How data is prepared for models
Solid operational data work - explicit DB schema usage, upserts, transactional payment flows, chat history JSONB, and scheduling logic; production-grade assumptions about idempotency and race conditions are present.
Evidence
vanyabotcrm/bot/src/db/queries.py
vanyabotcrm/bot/tests/test_db_integration.py
vanyabotcrm/bot/src/funnel/sender.py
Experimentation & Evaluation
3/10
How results are measured and tested
Good automated testing and CI-aware practices visible; test suites and typechecks are comprehensive, but there is no evidence of formal experiment tracking, A/B frameworks, or structured ML evaluation pipelines.
Evidence
vanyabotcrm/bot/tests/test_calculator.py
vanyabotcrm/bot/tests/test_ai_agent.py
bot-smm/README.md
MLOps & Deployment
3/10
How models are shipped to production
Practical deployment and ops experience is evident - cron scripts, Docker/standalone packaging references, webhook handling and alerting to Telegram - but no specialized LLM serving infra or drift monitoring code.
Evidence
vanyabotcrm/scripts/* (cron/arm scripts)
bot-smm/src/main.py
vanyabotcrm/bot/src/handlers/payment.py
Computational Efficiency
2/10
How efficiently computing resources are used
Uses async IO and non-blocking patterns for API calls and agent calls; however there is no evidence of GPU optimization, batching for model inference, quantization, or profiling/benchmarking for efficiency.
Evidence
vanyabotcrm/bot/src/services/ai_agent.py
vanyabotcrm/bot/src/services/ai_client.py
Research Depth & Innovation
1/10
Depth of research and new ideas
No evidence of original research, reproducing papers, custom layers or SOTA model implementations; innovation is at the product and systems level around agents and workflows, not at research-model level.
Evidence
bot-smm/src/agent/news_agent.py
Expertise
Conversational AI & Chatbots• Junior
AI Agents & Agentic Workflows• Junior
Industries
Health Care• Junior
Technologies
AI/ML
Python• Junior
FastAPI
Anthropic SDK
OpenAI SDK
SQLite
Asyncio
Aiohttp
aiogram
Recommendations
- Develop production conversational agents and LLM-backed features - build chatbots, mini-app integrations, and agent workflows that include payments and webhooks.
- Integrate LLMs into backend services with robust error handling and observability - tasks like building fallback, retries, and operational alerting for agent-driven flows.
- Implement MLOps-style monitoring for LLM usage - cost/latency dashboards, simple drift and hallucination checks and automated alerting channels.
- Hardening and automation around CI/CD and deploy scripts for AI apps - Docker, deploy scripts, and self-hosted runner work where webhooks and build isolation matter.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Junior Backend Developer
Confidence: Low API Engineer
A backend-focused engineer with senior-level evidence in fault-tolerant payment integrations and API design. The strongest proven skill is payment and fulfillment engineering with transactional claim patterns and idempotent webhook handling as implemented in apps/web/lib/jobs/issue-card.ts and the payments clients. Public code lacks large-scale performance measurement artifacts and explicit multi-service contracts for a distributed microservices mesh.
API Design
6/10
How well APIs are designed
API design shows explicit contracts, idempotency and webhook handling for payment flows; clear error handling and non-trivial decisions about retries vs no-retries for non-idempotent endpoints.
Data Layer & Database
6/10
Working with databases
Data layer demonstrates transactional boundaries, atomic claim patterns and migration tooling; tests and scripts show attention to schema evolution and DB-side invariants.
Evidence
elfuerte72/oplati_podpisku/packages/db/package.json (drizzle / db:migrate / db:init-roles)
elfuerte72/oplati_podpisku/apps/web/lib/jobs/issue-card.ts (uses transitionOrderDetailed + setOrderCardId in transactional flow)
elfuerte72/oplati_podpisku/apps/web/lib/loveandpay/handlers.test.ts (transactional claim tests / idempotency simulations)
Scalability & Performance
5/10
Handling load and speed
Scalability and performance measures include rate-limiting, background cron/worker decoupling and retry/backoff strategies; some caching/queue patterns are present but no large-scale load-testing artifacts.
System Architecture
5/10
Overall system structure
System architecture shows deliberate module boundaries (monorepo workspaces, separate packages for agent/db/types), job/worker separation and a deploy/infra orientation; decomposition is pragmatic rather than microservices-for-show.
Security & Auth
6/10
Protecting data and access
Security awareness is strong - HMAC signing, timing-safe compares, PII scrubbing, explicit non-logging of PAN/CVC and audit-driven fixes are present.
Reliability & Observability
6/10
Stability and monitoring
Reliability and observability features (structured logging, Sentry integration, alert bot, retries with backoff, graceful failure modes and tests for failure scenarios) are implemented and used in payment-critical paths.
Expertise
Backend AI & LLM• Junior
Messaging & Real-time• Junior
Node.js• Junior
Python• Junior
Industries
Financial Services• Junior
Technologies
PostgreSQL
Redis
Express
Recommendations
- Lead development of payment integrations and fulfillment flows (charge/top-up/release), ownership of transactional invariants and idempotency logic.
- Design and implement Telegram-based real-time features and bot-backend handoffs, including alerting and operator flows.
- Own backend API design and reliability improvements for money-paths, including further hardening of retries, observability and DB migration practices.
- Implement or review migration chains and schema evolution for Postgres-based systems and design recovery playbooks for payment incidents.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Intern Frontend Developer
Confidence: Low Generalist
A practical junior-level engineer with experience in modern web stacks and related tooling. The strongest proven area is handling web-facing integrations and payments, evidenced by numerous payment-related files and payment-provider client code (payment flow, provider clients and handlers). There is little or no human-authored frontend component architecture, accessibility or dedicated frontend performance work available for review and complex system-design or cross-cutting frontend evidence is not present in the human-authored set.
UI Component Architecture
How interface parts are built
Not evidenced in public code
Responsive & Cross-browser
Works on all screens and browsers
Not evidenced in public code
Performance Optimization
Speed of the interface
Not evidenced in public code
Accessibility & Semantics
Usable for everyone
Not evidenced in public code
State Management & Data Flow
Managing data in the app
Not evidenced in public code
UX & Visual Polish
Look and feel quality
Not evidenced in public code
Expertise
React• Intern
Frontend Architecture & Build Tools• Intern
Frontend AI Integration• Intern
Industries
Financial Services• Junior
Technologies
TypeScript
Node JS• Junior
Nest.JS
Docker Compose
Tailwind CSS
Next.js
Prisma
React.js
Vite
Axios
BullMQ
Zod
pnpm
Turborepo
Cloud• mentioned only
Recommendations
- Assign this developer to implement and maintain feature-level frontend work using Next.js and React, focusing on payments UI and Telegram mini-app integration.
- Use them to extend and harden payment-provider integrations and server-side webhook handling where existing patterns are clear.
- Pair them with a senior frontend engineer for component architecture, accessibility, and large-scale state management work.
- Have them own build tooling and CI tweaks (Turborepo, Vite, Next.js) and smaller infra tasks under supervision.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: