06/19/2023 updated
100 % available
Lead Fullstack Engineer, Javascript Engineer, Front-End Web Developer
Limassol, Greece
Only remote
MSc EngineerInnovationJavaScriptAgile MethodologyData ModelingWeb DevelopmentElasticsearchEngineeringNode.jsSvelteNext.jsSystems DesignTypeScriptWebRTCTailwindReact.js
With more than 7 years of experience as a freelance developer and software engineer, I got involved in a variety of projects, facing different requirements and challenges. Writing full stack applications in combination with creating systems with different ecosystems, facing a variety of real-life problems and following the vast diversity of community-driven web technologies and innovation, helps me to shape a versatile technical expertise with a higher view on connecting the pieces that form a solid web software solution.
Skills
Javascript | Typescript | Node.js | SASS | WebRTC
Full-Stack, FE, BE Development | Engineering | Data Modeling | System Design | Agile Development | p2p
Libraries / Tools
React.js | Vue.js | Angular | Redux | Vuex | GraphQL | Express | Elastic Search | Mongoose | Webpack | Docker | Styled-components | Tailwind | Echarts
Frameworks
Next.js | Svelte | Gatsby | Nuxt.js | Nest.js | Feathers.js | Meteor.js | Symfony
Skills
Javascript | Typescript | Node.js | SASS | WebRTC
Full-Stack, FE, BE Development | Engineering | Data Modeling | System Design | Agile Development | p2p
Libraries / Tools
React.js | Vue.js | Angular | Redux | Vuex | GraphQL | Express | Elastic Search | Mongoose | Webpack | Docker | Styled-components | Tailwind | Echarts
Frameworks
Next.js | Svelte | Gatsby | Nuxt.js | Nest.js | Feathers.js | Meteor.js | Symfony
Experience
Professional experience5 - 10 years
Freelancer since2019
Languages
EnglishGoodGreekNative speakerSpanishGood
Project history
Creating an Amazon seller app
Stack: FeathersJS, MongoDB, Mongoose, Nuxt.js, Vue.js, Echarts, AWS
3 repos architecture: Back End, Front End, Flow manager
Back end:
A Feathers.js app connected to a Mongo database. Code splitted in microservices, utilizing complex mongoose aggregation pipelines and
operating with websockets to all feathers-clients subscribed to them, providing further flexibility with real-time transport (like Socket.io)
configured, event channels for all niched use cases.
Front end:
A Nuxt.js app communicating with feathers BE through the feathers-client sdk to present a ui(Apache Echarts, Vue.js) to amazon sellers that
need to keep track and monitor a plethora of KPIs related to their shop/account.
Flow manager:
A vanilla node set of services instantiating a feathers-client. Responsible for continuously collecting, updating, transforming and emitting data
from various Amazon apis and other sources to our back end.
Stack: FeathersJS, MongoDB, Mongoose, Nuxt.js, Vue.js, Echarts, AWS
3 repos architecture: Back End, Front End, Flow manager
Back end:
A Feathers.js app connected to a Mongo database. Code splitted in microservices, utilizing complex mongoose aggregation pipelines and
operating with websockets to all feathers-clients subscribed to them, providing further flexibility with real-time transport (like Socket.io)
configured, event channels for all niched use cases.
Front end:
A Nuxt.js app communicating with feathers BE through the feathers-client sdk to present a ui(Apache Echarts, Vue.js) to amazon sellers that
need to keep track and monitor a plethora of KPIs related to their shop/account.
Flow manager:
A vanilla node set of services instantiating a feathers-client. Responsible for continuously collecting, updating, transforming and emitting data
from various Amazon apis and other sources to our back end.
Amdocs R&D department (DigitalOne)
Software Engineer of the core team developing CatalogOne
Stack: React.js, Redux, Reselect and Mocha
CatalogueOne is the largest (scope-wise) project I had the opportunity to participate in. Needed to create a complex architecture with
modular top quality code that was able to cover the needs of the Telco Industry. Also, the solution needed to be extendable for customized
usage for other (Amdocs or not) products. The UI was handling REST calls to various microservices that composed the backbone of
CatalogOne.
Main responsibilities:
Prototyping on new features for catalogOne
Create a user-friendly performant tool with complex operations Built large-scale, extendable UI architecture
Challenges:
Amdocs products have the concept of layers. The core team is building the main framework and other products hook to this layer. Being part
of the core and layer1 team we needed to provide proper architecture to support flexible extendibility.
The code base was organized in a 5 repositories system, bundled with webpack. We were focusing on continuous optimisations regarding
performance, cashing mechanisms and managing dependencies across the repos.
As part of the framework team, I was working on creating a framework that utilizes the core code, but keeping it agnostic on the layers code.
We created and optimized our pipelines for all UI repos builds and also established the release process for all repos following CI-CD
standards and best practices.
CatalogOne is the heart of many Amdocs products, since it's the new catalog. Building a tool with all the capabilities to support all telco
companies' needs by Agile principles, means that as a web developer I was in constant collaboration with Product Owners, Architects, Tech
leads, Designers, Testers and other Development teams.
Software Engineer of the core team developing CatalogOne
Stack: React.js, Redux, Reselect and Mocha
CatalogueOne is the largest (scope-wise) project I had the opportunity to participate in. Needed to create a complex architecture with
modular top quality code that was able to cover the needs of the Telco Industry. Also, the solution needed to be extendable for customized
usage for other (Amdocs or not) products. The UI was handling REST calls to various microservices that composed the backbone of
CatalogOne.
Main responsibilities:
Prototyping on new features for catalogOne
Create a user-friendly performant tool with complex operations Built large-scale, extendable UI architecture
Challenges:
Amdocs products have the concept of layers. The core team is building the main framework and other products hook to this layer. Being part
of the core and layer1 team we needed to provide proper architecture to support flexible extendibility.
The code base was organized in a 5 repositories system, bundled with webpack. We were focusing on continuous optimisations regarding
performance, cashing mechanisms and managing dependencies across the repos.
As part of the framework team, I was working on creating a framework that utilizes the core code, but keeping it agnostic on the layers code.
We created and optimized our pipelines for all UI repos builds and also established the release process for all repos following CI-CD
standards and best practices.
CatalogOne is the heart of many Amdocs products, since it's the new catalog. Building a tool with all the capabilities to support all telco
companies' needs by Agile principles, means that as a web developer I was in constant collaboration with Product Owners, Architects, Tech
leads, Designers, Testers and other Development teams.