Summary of "Из джуна на удаленку $10k+ в месяц за три года - через Zuzex, аутстафф, бигтехи и кибербез"

Overview

Interview with Sasha (Alexander), a self-taught developer who progressed from a junior role in Russia to remote foreign-currency roles and $10k+ offers within roughly three years. He describes stacks and technical responsibilities, common hiring/tests, and practical tips for getting remote jobs and negotiating offers.

Technical stacks & platforms

Languages
- Go (primary), Python, some Node
- Earlier exposure to Ruby/Perl frameworks and Django/Flask
Infrastructure / Cloud
- AWS (S3, ECS, SQS), Yandex Cloud, private clouds
- Built services on ECS in some projects instead of Kubernetes
Databases
- Frequent use of DynamoDB
- Postgres and Mongo-like stores mentioned
- References to embedded DBs (Badger/RocksDB-like) in blockchain/storage interviews
Messaging & streaming
- Kafka, RabbitMQ, other MQs
- Telemetry collectors and high-throughput log/incident pipelines
Observability & operations
- Prometheus + Grafana dashboards
- Load testing, metrics instrumentation
- TCP/connection pooling tuning
Networking & low-level
- HTTP/HTTPS proxying, TLS, socket-level tuning
- Telephony protocols, firewalls, DNS/recursive behavior
- Emphasis on low-latency systems
Security / cybersecurity
- Firewall product work (Positive Technologies): C++ device firmware and Go/Python backend services
- Telemetry collection, config management, admin panels
Performance & concurrency
- Mutex/deadlock issues, connection ping frequency affecting throughput
- Optimizing RPS per core (examples: 125 RPS observed; issues approaching 1,000 RPS/core)
- Cache strategies, sharded caches, memory-efficient streaming JSON decoding
Blockchain-related concepts
- Merkle trees, Bloom filters, consensus/tolerant systems
- Transaction parsing and validator algorithms (common in interviews)

Representative products, features & engineering tasks

Full HTTP(S) proxy / load-balancer across geographies
- Connection reuse, TLS overhead reduction
- Prometheus metrics, Grafana dashboards, load testing
Memory-efficient streaming JSON parsers
- Decode and persist large JSON without OOM
- Channel-based processing and streaming decoding
Telemetry collectors and admin/config services for firewall hardware
- Integration between C++ firmware on devices and cloud/backends
Microservice and distributed-monolith rewrites
- Code generation scripts (repositories, handlers) and migration challenges

Interview, hiring & test patterns

Typical stages
1. Screening
2. Engineering manager interview
3. Coding interview / homework (live or take-home)
4. Team interview
5. Final / offer
Test formats
- Single-day algorithmic tasks to multi-day/week system tasks
- Examples: proxy implementation, load test & instrumentation, streaming parser
Heavy take-home example
- Proxy + hubs + dashboards + load tests targeting 1,000 RPS/core
- Intended as a 4-hour task but realistically could take a week with real instrumentation and optimization
Question types
- Practical architecture and end-to-end tasks
- Low-level theoretical questions (processor caches, atomic primitives)
- Varies by company and market (Eastern-market vs Western startups)
Market differences
- Russian/Eastern interviews sometimes harder for lower salaries
- Western/foreign startups often expect ownership and cross-stack capabilities

Use of AI / code assistants

Active use of Claude / GPT for:
- Interview prep and rehearsals
- Writing and iterating code, generating tests, and pushing commits
- Translating interview tasks and rehearsing English
Team attitudes
- Many teams use AI for routine tasks; some senior engineers resist
- Candidates advised to document AI-generated code in take-homes, since reviewers may ask

Remote work, HR, legal & operational issues

Background checks and nationality restrictions
- Example: an Israeli company rescinded an offer days before start because the candidate had a Russian passport
Corporate laptop logistics (three common patterns)
1. Buy-your-own with reimbursement
2. Company ships laptop to an EU hub and forwards
3. Direct corporate image with heavy restrictions (VPNs, debugging limits) - Restrictions can hinder local debugging and development
Payment options and legalities
- Options discussed: receiving money in Russia, using agents, crypto payments
- Advice: consult community guides for specific workarounds
LinkedIn / geo-strategy
- Setting EU/European location can improve inbound recruiter responses
- Remote workers sometimes use temporary residence in Georgia, Armenia, Serbia to ease legal/logistical hurdles

Career arc, compensation & negotiation

Typical progression in Sasha’s story
- Internship → small outsourcing → product teams → attempts at bigtech (scooter, Yandex/Ozon/Avito) → Positive Technologies → remote foreign roles
Compensation growth
- Reported ~30x salary growth over a few years
- Examples include offers in USD and GBP (mentions of $10k+ and £4.5k–7k offers)
Negotiation tips
- Better English (C1) improves negotiation power
- Counter-offers can raise pay (examples of ~20%+ increases)
- If you don’t care about an employer, they may offer more to attract you
Interview outcomes
- Many rejections are common; persistence and resume optimization are required
- Unpaid take-homes are common but can be valuable for learning and visibility

Practical advice & community resources

For juniors
- The market is tougher; you need exceptional projects, patience, or internships to progress
- Consider foreign remote positions after 1–2 years of solid experience
Improve English and optimize LinkedIn/resume
- Listing a European location can sometimes help inbound foreign recruiters
Use AI tools wisely
- Accelerate coding, but document AI-generated code in take-home submissions
Join communities (“the club”)
- For mock interviews, shared hiring intelligence, workarounds (laptop, payments), and moral support
- Example: community members shared Linux/socket tuning tips and hiring playbooks

Reviews, guides & tutorials referenced

Interview/test prep
- Using ChatGPT/Claude to rehearse interview answers and convert Russian tasks to English
Club guides
- Hiring/remote-pay guides (how to receive money in Russia)
- Job-search playbooks, shared question banks, practical fixes for corporate laptop or environment limitations
Practical tutorials implied
- Building a high-performance proxy (code + instrumentation)
- Streaming JSON parsing and memory-efficient decoders
- Prometheus/Grafana instrumentation
- TCP pooling and socket-level tuning

Notable anecdotes & takeaways

DynamoDB often appears as a default managed datastore across projects
Positive Technologies work highlighted contrasts between firmware/C++ device code and backend services
Foreign tests can be extremely practical and difficult; some provide detailed feedback (one candidate received a 4-page critique for a proxy test)
Work-life balance matters: candidate left high-pay offers for better fit and quality of life; travel and remote work helped recovery from hiring stress

Main speakers / sources

Sasha (Alexander) — self-taught developer, multiple Russian bigtechs and Positive Technologies, now in a remote foreign role
Interviewer / channel host — unnamed, runs the referenced “club” community
Community members mentioned
- Nikita — provided Linux/socket tuning help
- Other unnamed colleagues, managers, and public figures (e.g., Vladimir Balun)