Full Stack Developer

* Technical lead - Node.js, React.js, Architecture, Code Design ◀
Improved the company's technology stack. Brought in React.js and Redux and helped set the pace for replacing old jQuery applications with new ones, based on modern technologies. Contributed to defining the high level architecture of the whole product ecosystem, from the servers and services necessary for the applications to run, all the way to frameworks and libraries, coding standards, style guides and testing practices.
Helped drastically improve the code quality, helped standardise the software development practices and the team culture around testing - TDD, E2E.

* DevOps - Communication, AWS, CI◀
From this position, I mostly acted as a bridge between the development team
I was working with, and the Operations department. I improved the operations team understand the project needs and suggest suitable services to make development easier and improve the stability of the application in production.
Contributed to the migration from Node 0.10 to the LTS version and to the rewrite of a big part of the application.

* Mentor - JavaScript (ES6), Software Development Basics ◀
Helped a QA team member migrate to Full Stack JavaScript within 6 months.
Created an ES6 training, used to get a better understanding of the latest standards in JavaScript development. Available for questions from team members, I tried to provide clarification on any issue that might have appeared due to lack of experience or novelty of the technology.
Improved QA department understanding of Docker, Git and JavaScript.
Enabled the QA team to write end-to-end tests with Protractor. Improved the whole team's understanding of Continuous Integration.

* Technical Recruiter ◀
Contributed to the company's JavaScript recruitment and interviewing process.
Changed the JavaScript technical interview which translated into higher quality candidates and employees. Helped build the team currently working on the project.

Lead Front-End Developer (SR)
Oct 2013 – Jul 2014

Task analysis, estimates, organisation, team management, implementation of complex functionalities at the presentation layer.
As a lead front-end developer I am responsible of keeping the front-end team together, scheduling and attending meetings to clarify requirements and offer feedback in regards to the implementation at the presentation layer, offer guidance to team members.
Aside from the usual activities I hold internal trainings focused on JavaScript development, design patterns and object-oriented programming techniques. I also take part in the recruiting process by holding interviews for both front-end and backend candidates.
The main technologies that I use in this position are JavaScript, XML, JSON, DS Script(Demandware specific backend language — based on ECMA-262), HTML5, CSS3, BackboneJS, jQuery, LoDash.

Demandware Developer
Jan 2013 – Jul 2014

Demandware is an eCommerce platform built to fit the needs of every company, no matter how big or small it is. In this position I'm responsible for doing front-end related work, mostly done in JavaScript, but I do backend coding as well. The platform uses a language based on the ECMA 262 specification, very similar to JavaScript. On the front-end side I'm responsible for implementing custom functionality, and applications that require hardcore coding. I'm also involved in a training program as well, in which I train/supervise people that are new to the Demandware platform, on the front-end side. This position involves dealing with different personalities, different types of learners, and it requires effort to adapt your explanations and feedback, and self-control.
Javascript Developer
Dec 2012 – Jul 2014

I was responsible for developing JavaScript based web applications and custom functionality that needed to be implemented on the client side. This position also involved working with HTML and CSS, employing the best practices in the field. I had a TDD-based workflow, and tried to stick to it most of the times. To keep myself organized I kept TODOs in Evernote, and centralized everything there. I tried as much as I could to stay away from libraries and in my opinion there's no need to resort to libraries if the language has native functionality built in to fit your needs. As a second responsibility besides working on JavaScript web-apps, I also did internal trainings with developers who needed to expand their knowledge of OOP.