Position: Backend JavaScript Developer
Category: Node.js
English level: upper
Years of experience: 5

- Built a service that connects to a database (MS SQL), fetches information about tables, types, indexes, etc and build JSON Schema of it to make possible visualize the schema. Also, it could reverse the JSON schema into DDL.
- Implemented unified services that could interact with different cloud storages - AWS S3, Azure Blob Storage, Google Cloud. It could create a file structure tree, upload and download files. I learned a lot about cloud storages.
Overall 2 years of commercial experience. Several interesting projects I worked with:
- Learning management system. A platform for passing online tests, retrieving lectures, feedback, etc. A lot of interactions with users by web sockets. Interesting resource share between back-end and front-end. We used Node.js, React, Typescript, TypeORM, Socket.io.
- Social network. It hasn't gone far, but I had an excellent opportunity to develop architecture on my own from scratch both for front-end (React) and back-end (Node.js), database architecture. I worked with cutting-edge technologies - GraphQL, Apollo, PostgreSQL.
- Desktop application for visualization of database schemas. The main application interacts with the services of different databases (MongoDB, Cassandra, MS-SQL, etc) and creates schema of tables, rows, their types, etc. I learned a lot about the variety of databases, their features. I built a couple of database services on my own. Also, I used to work with node.js inter-process communication, resolved some React performance issues. I became a master of debugging. We used Electron with Node.js and React behind it.
I'm passionate about creating a good quality product that will live for a long time. I'm expecting to think about architecture, scalability, best practices. Of course within reasonable limits with no harm to the business.
Given the above, I want a
- medium/big project, maybe a high load
- preferably a product company
- product and engineer oriented approaches
- medium/big team (5+)
- TypeScript
- no remote
- not front-end only, preferably back-end