connect.aleksei@gmail.com
Best for technical questions, project deep-dives, and longer conversations. I read every message.
I read every message. If you have a question about a system I worked on, want to talk about distributed backends, or just want to say hi — feel free to reach out.
Email is the primary channel. LinkedIn and GitHub work for shorter conversations and code questions.
Best for technical questions, project deep-dives, and longer conversations. I read every message.
Best for quick intros, recruiter outreach, and first contact.
For code questions, issue threads, and OSS work. Slower turnaround.
I keep a small inbox zero practice. I read every message that lands in my primary inbox — usually within a day, sometimes a week if I'm heads-down on something.
If you write something specific, you'll get a specific reply. If you send a template, you'll probably get a template back.I'm most useful on questions about distributed backends, event-driven systems, Kafka and MongoDB, the boring parts of reliability engineering, and the team practices that make all of that work. I can't help with frontend, ML, or anything outside what I've actually shipped.
Specific question, a system you saw, an honest disagreement, a refer.
Generic pitches, recruiter templates, anything starting with "Hope this finds you well".