Anonymous
Python Developer
4+ years exp
4+ years ML exp
JavaScript
Python
Scalability & Performance: 7/10
API Design: 6/10
System Architecture: 6/10
Online
Invite to interview
Message
Download CVCV
Overview
Technical skills
Career analytics
Roles
Overview
Senior Python backend engineer specializing in performant, concurrent desktop service layers and resilient API integrations. The strongest proven skill is building high-performance, resource-conscious components such as the RecyclerScrollArea virtualized viewport (moduls/ads/_card_viewport.py) and robust network fetch logic in GasFetchService (Ethereum_Gas_Tracker/services.py). There is limited public evidence of schema-based data storage, formal migration history, cloud-native distributed system design or CI/CD/infra automation in the analyzed code.
Technical skills
JavaScript
Python• Senior • 4y+
Python
aiogram
Aiohttp
Asyncio• 4y+
PySide6• 4y+
Databases
Databases
AI/ML
AI Agents
Claude Code
LiteLLM
LLM
Model Context Protocol
Prompt Engineering
Windsurf
AI/ML
LLM Apps
Semantic Search
ChatGPT• 4y+
Claude• 3y+
Cursor• 3y+
DeepSeek• 3y+
RAG
DevOps
Git
Rest API
Observability
Docker• 4y+
Docker Compose• 4y+
Web3
Ethereum
QA
Playwright
Selenium• 4y+
Career analytics
Verified work history and code activity in one view - open-source impact, work rhythm, trust signals and a forecast of when this candidate is likely to move.
3
Years active
146
Commits analyzed
Work rhythm
UTC+0
12 AM6 AM12 PM6 PM12 AM
Code activity
Low
Peak
Last activity
Jul 2026 · 0 Days
Active days (90d)
1
Typical work hours
7 AM - 3 PM
Open source & impact
1
Stars earned
Collaboration Quality
Senior Backend Developer
Confidence: High API Engineer
Senior Python backend engineer specializing in performant, concurrent desktop service layers and resilient API integrations. The strongest proven skill is building high-performance, resource-conscious components such as the RecyclerScrollArea virtualized viewport (moduls/ads/_card_viewport.py) and robust network fetch logic in GasFetchService (Ethereum_Gas_Tracker/services.py). There is limited public evidence of schema-based data storage, formal migration history, cloud-native distributed system design or CI/CD/infra automation in the analyzed code.
API Design
6/10
How well APIs are designed
API design shows deliberate fallback and failure strategies (waterfall RPC, Etherscan -> modern RPC -> legacy RPC), batched RPC requests and explicit network validation, but lacks formal versioning/idempotency contracts or documented stable error contract across services.
Evidence
Ethereum_Gas_Tracker/services.py:GasFetchService (waterfall strategy, _do_etherscan/_do_rpc/_try_modern_rpc/_try_legacy_rpc)
Makis12rus/ADS-Power-Manager/moduls/ads/_api_client.py:AdsAsyncClient and _request_ads_api (ads API client abstraction and request helpers)
Data Layer & Database
2/10
Working with databases
No traditional database layer or migration history; persistence is local (registry, QSettings, filesystem) with some transactional save patterns, secret storage and DPAPI integration but no schema evolution artifacts or tuned SQL.
Evidence
ADS-Power-Manager/moduls/ads/settings_panel.py:_execute_save (transactional save to registry and UI geometry)
Ethereum_Gas_Tracker/win_logic.py:SecretStorage and SecurityManager (DPAPI + keyring fallback for key storage)
Scalability & Performance
7/10
Handling load and speed
Clear focus on performance and scalability in UI virtualization, caching and network concurrency: virtualized recycler for very large lists, renderer and texture caches, adaptive RPC timeouts and parallel validators; shows concrete optimizations rather than copy-paste cache patterns.
Evidence
ADS-Power-Manager/moduls/ads/_card_viewport.py:RecyclerScrollArea (virtualized pool, identity map, auto-scroll and DND with in-flight reindexing)
ADS-Power-Manager/core/_style_graphics.py:Graphics (renderer and icon caches with thread-safe locks)
Ethereum_Gas_Tracker/services.py:RpcBatchValidator (adaptive timeout, parallel validation, latency sorting)
System Architecture
6/10
Overall system structure
Modular separation between core, moduls and UI layers, explicit presenter patterns and plugin manager indicate reasoned module boundaries; architecture is focused on a desktop monolith with careful component separation rather than distributed microservices.
Evidence
ADS-Power-Manager/moduls/ads/profile_presenter.py:ProfilePresenter (presenter pattern integration between UI and core)
ADS-Power-Manager/core/_plugin_manager.py:PluginManager (plugin scanning and manifest handling)
ADS-Power-Manager/core/core.py (explicit facade imports and orchestration of subsystems)
Security & Auth
5/10
Protecting data and access
Security awareness is visible (DPAPI, SecurePasswordLineEdit, encrypted key storage and cautious secret handling), but there are risky choices (explicit SSL verification disabling in some fetchers) and no centralized dependency audit or hardened network policy documented.
Evidence
Ethereum_Gas_Tracker/win_logic.py:SecurityManager.encrypt_string / decrypt_string and SecretStorage (DPAPI, keyring fallback)
ADS-Power-Manager/core/_style_widgets.py:SecurePasswordLineEdit (input method hints to avoid OS caching)
Ethereum_Gas_Tracker/services.py:ChainlistFetcher (sets QSslConfiguration.VerifyNone and reply.ignoreSslErrors)
Reliability & Observability
6/10
Stability and monitoring
Reliability patterns present: timeouts, abort/cleanup for network replies, timers for adaptive behaviour, resource guards and explicit cleanup of C++ Qt objects; observability is ad-hoc (custom logger) rather than integrated with centralized metrics/alerting.
Evidence
Ethereum_Gas_Tracker/services.py:GasFetchService (QTimer aborts, _cleanup_reply, _timer interaction and fallback flows)
ADS-Power-Manager/system/logger.py:Logger (structured logger, anti-spam and log_block context manager)
ADS-Power-Manager/moduls/ads/_card_viewport.py:RecyclerScrollArea (Resource Guard patterns, pool reset and reset_visuals)
Expertise
Python• Senior
Microservices & API Architecture• Middle
System Architecture• Middle
Industries
Blockchain & Crypto• Senior
Recommendations
- Develop high-performance desktop tooling and native OS integration features where low-latency UI, rendering caches and DPAPI/key management are required.
- Implement resilient API clients and service layers that need adaptive timeouts, parallel validation and waterfall/fallback strategies (RPC, third-party APIs).
- Build advanced UI components and developer tooling that benefit from virtualization, identity-map recycling and GPU-accelerated rendering caches.
- Help harden network security posture by removing SSL bypasses, centralizing TLS handling and adding explicit retry/backoff policies and dependency audits.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Senior DevOps Engineer
Confidence: Medium Generalist
Senior desktop application engineer specializing in high-performance PySide6 GUI systems with careful resource guards and custom rendering. The strongest proven skill is large-scale, performant UI engineering exemplified by the virtualized RecyclerScrollArea and DND/selection engine in moduls/ads/_card_viewport.py. There is little to no public evidence of CI/CD, infrastructure-as-code, cloud deployment or formal incident playbooks.
CI/CD Pipelines
Automated build and deploy
Not evidenced in public code
Infrastructure as Code
Managing servers with code
Not evidenced in public code
Containerization & Orchestration
Working with containers
Not evidenced in public code
Observability & Monitoring
2/10
Watching system health
Basic observability: structured logging and an async telemetry worker are present, but there are no SLOs, burn-rate alerts, alert routing or dashboards-as-code.
Evidence
system/logger.py: Logger class with log/info/warning/error methods and log_action decorator
moduls/ads/_telemetry.py: TelemetryWorker / TelemetryThread using aiohttp for async polling
Reliability & Incident Response
3/10
Keeping systems up
Clear attention to runtime reliability and graceful state handling (watchdog, transactional locks, autosave/force-save), but no incident runbooks, chaos exercises or deployment rollback strategies are present.
Evidence
core/_watchdog.py: AppWatchdog class with heartbeat, run loop and start/stop helpers
moduls/ads/_card_viewport.py: Transactional lock, Identity Map and DND landing pipeline with landing animation and rowDropped signal
moduls/ads/settings_panel.py: force_save and debounced _save_timer for zero-loss flush before automation
Cloud & Cost Optimization
Smart use of the cloud
Not evidenced in public code
Expertise
Site Reliability Engineering• Middle
Observability & Monitoring• Middle
Industries
Blockchain & Crypto• Middle
Technologies
Observability
Python• Senior • 4y+
Asyncio• 4y+
Aiohttp
PySide6• mentioned only
Recommendations
- Develop high-performance desktop tooling and complex client-side applications that require custom rendering, virtualization and low-latency UI interactions.
- Build secure local automation and integration utilities where careful credential handling and autosave semantics are required.
- Engineer advanced UI components and internal IDP libraries (virtual lists, drag-and-drop, custom widgets) for reuse by product teams.
- Integrate structured observability and formal incident/runbook artifacts to mature operational readiness (alerts, SLOs, dashboards as code).
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle AI/ML Engineer
Confidence: High LLM Engineer
Mid-level LLM engineer specializing in building async RAG microservices and vector-retrieval backends. The strongest proven skill is implementing an async FastAPI RAG pipeline with pgvector-focused schema and retrieval logic as shown in main.py lifecycle management and services.py retrieval/indexing methods. There is little to no evidence of model training, experiment tracking, tests, CI/CD, or robust production hardening of LLM integration in public code.
Model Architecture & Training
1/10
How well models are designed and trained
Minimal model work - a toy embedding stub is present but no training, loss, or optimizer logic.
Data Pipeline & Feature Engineering
2/10
How data is prepared for models
Basic data persistence and schema for vector chunks with metadata; simple indexing and insertion flows exist but no complex ETL or augmentation.
Experimentation & Evaluation
How results are measured and tested
Not evidenced in public code
MLOps & Deployment
3/10
How models are shipped to production
Practical deployment and ops primitives - application lifespan management, async DB pool, and API endpoints are implemented but full MLOps (tracking, CI/CD, monitoring) is absent.
Computational Efficiency
3/10
How efficiently computing resources are used
Some performance considerations - asyncpg pooling, HNSW pgvector index creation and LIMITed nearest neighbor SQL are used, but no profiling or advanced optimizations.
Research Depth & Innovation
1/10
Depth of research and new ideas
No research depth or novel algorithmic contributions; RAG pipeline is an assembly of components with simulated LLM call.
Expertise
Conversational AI & Chatbots• Middle
Industries
Artificial Intelligence• Middle
Software• Middle
Technologies
Databases
AI/ML
LLM Apps
Rest API
Semantic Search
Embeddings• mentioned only
FastAPI• mentioned only
LiteLLM• mentioned only
pgvector• mentioned only
PostgreSQL• mentioned only
Pydantic• mentioned only
RAG• mentioned only
Recommendations
- Develop production RAG microservices that integrate vector stores and LLMs with clear retrieval and provenance flows.
- Build fast async backends and prototypes that require pgvector/DB-index integration and low-latency similarity search.
- Harden LLM orchestration by adding real model integration, streaming responses, retries/backoff, metrics and observability.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: