Senior Backend engineer with devops knowledge. I have experience in building scalable distributed projects (see cv) and joining experienced team with mature project. I am passionate about highly concurrent services, challenging CS and math problems. In my free time I enjoy solve programming challenges and learn new technologies on Coursera (available certs on request).
That was a fun little interlude - I wonder how effective strategies like this are? Is it to check for genuine technical ability, engage candidates or just a little barrier to ensure a candidate is really interested in the role?
Location: Moscow, UTC+3
Remote: yep
Willing to relocate: not right now, mb in the future
Technologies: Ruby, MongoDB, AMQP, Go, Clojure, AWS, Chef, Git.
Résumé/CV: on request
Email: my nickname till "_" at realisticgroup dot com
Important:
I spent all my career (from 2006) building projects in ruby, and I'm about to move on. I'm interested in joining some project on early stage to get real world experience with clojure/go (or even with erlang/ocaml) and to improve my english communication skills. I would like to spend with your project no more than 20h/week with low rate for the first couple of months.
I totally don't like: php, python, perl, windows, rails, socials networks, outsourcing and boring client-side (making forms with bootstrap isn't for me).
And I'm not a freelancer and want to be attended to one project for a long time.