Position: Fullstack Developer, Lead, Architect
Category: Lead
English level: upper
Years of experience: 9

- Wrote an adapter from Dojo Toolkit to React, that enabled gradual migration of the project to React, without rewriting it from scratch, thus saving the startup at least 66K$ (the company was going to hire two extra Dojo Toolkit developers for 3000$/mo each, but after the migration we were able to continue without extra hiring for all 11 months which I've been working there);

- In collaboration with an amazing Ops-guy developed an internal Jira plugin allowed management and QA to deploy an isolated environment for any given ticket with a click of a button in Jira, with no involvement from developers;

- Helped a team at an enterprise-sized company (Mulesoft) to reduce their delivery cycle from a few months to a week and stop working overtime;

- For the last two years my team has been functioning without a manager;

- Along the way taught several developers how to *save* their time using tests automation, and how to leverage it to maintain sanity in codebases;

- Taught programming 2 friends from scratch until they got real paid jobs;

- Inspired few developers (according to the developers themselves) to push their boundaries and learn new languages or frameworks.

- Built a network of like-minded fullstack developers (and I can bring them with myself).
Available immediately! 

- - -

If any of the points below gives you a PTSD attack, I can help you:
- Every new feature breaks two old features;
- Everything was fine until you released to production and the whole world felt apart;
- There is just no room to add more meetings, but nothing can get done;
- You spend great amount of time on sprint estimation but deadlines are still being missed;
- Developers beg you for time for some "technical work" but no one is able to explain you what has to be done and how long it will take;
- Two developers developed two features in parallel, and now they can't integrate them;
- It feels like business and development speak on two different languages;
- etc.

Those are some of the real phrases I heard from the clients:
- "Now we deliver once a week instead of once a quarter"
- "Wtf, developers are happy to automate their tests?"
- "QA persons finally have time to breath!" (that's a direct quote)
- "We don't have to work on weekends anymore"

If you want someone to completely take the burden of technical decisions off your shoulders, so you can focus on the business part, while the app is just magically delivered to production - here I am!

I started to learn programming when I was 13, and 16 years later (9 of which is commercial experience) I can say I know a few things about how to deliver value to users in a *regular and reliable manner*. 

Along this way I've discovered and mastered several practices you have probably heard about, but never seen working well in a "real world setup", like tests automation which allows the team to deliver new features without breaking old ones, continuous delivery which makes deployments a routine, agile practices which give you the mythical flexibility, and so on.

Contact me even if you're interested but still not sure - I'll try to answer any of your questions.
It's critically important for me to have the ability of making decisions on development processes and technologies. Otherwise I will not be able to fully leverage my potential, and you will get just an extra pair of hands, while the main benefit from hiring me is to get an extra head. 

- - -

Acceptable backend technology is some "regular scripting duo", e.g. PHP/Laravel, Python/Django or Ruby/RoR. It's unlikely that I'll be able to handle something on Java, Go, Scala, etc. Also Elixir is acceptable if you're planning some highload.

It is also totally fine if you have a legacy project that should be resurrected - as far as it's written on one of the scripting languages described above. It's also fine if it has some custom "homemade" framework, but I'll ask to take a look on it first. Whatever it is at the end, under no circumstances I'll propose to "rewrite it from scratch", but instead will propose a strategy for gradual migration along with developing new features.

Frontend is default for the current year: it's either React, or Vue, or Angular. Something exotic like Svelte is negotiable too, but then you probably don't need to read this text - just go ahead and contact me. And again, any legacy project can be resurrected.

If you need mobile, it's either React Native or something even more lightweight, like Turbolinks. I unlikely will be able to handle an app that needs an extensive work with native mobile APIs or which has some extreme design tricks or animations. But I' fine with that if you have time to let me figure it out.

The infrastructure is built on top of GitLab CI, Docker and Dokku. If we're talking about a legacy project, the existing infrastructure will be used on start and then upgraded gradually.