Remote Full Stack Engineer | Scalable Systems - Mumbai, India

I have been programming since I was 14, and have worked across various stacks and projects.

Have worked at only small/early stage startups where in a very short amount of time, I got experience worth years like System Architecture, Infra Scaling and so on along with best practices while building systems. To mention a few:

1) Node Best Practices: ( private link

2) Conventional commits ( private link

3) OWASP Top-10 (to ensure all the basics of security are taken care of)

What makes me different than 99% Engineers out there (in 3 points) ?

1) I start from business problem first. Software is a tool to solve business problem, and I understand it and start from your business problem first, asking you questions and go to the depths of "why" to ensure that I can build the perfect tailored solution.

2) I have a product mindset (working at early stage startups, where I have been able to develop this mindset) and build software from product perspective first thinking about scope, different cases and so on.

3) Apart from working on the functional side of software, I also focus on the non-functional part of the software like security (OWASP), privacy (GDPR), edge cases, system limitations while architecting it and so on

Recent Project:

Built an event tracking system from scratch for a startup since they were facing limitations in their current stack. Below are some of the key architectural decisions and practices that have been implemented:

1) API-Based Cron for Scalability - To avoid the pitfalls of traditional cron jobs in a horizontally scaled environment, this project utilises an API-based cron system. This approach ensures that scheduled tasks are executed once, regardless of the number of server instances running, thereby preventing duplication and ensuring efficiency.

2) Dual Primary Keys in Database Design - The database schema employs two types of primary keys: an integer-based private key and a UID based public key.

This design choice offers the following benefits:

2a)Space Efficiency: The integer-based private key consumes less space when used as a foreign key in related tables.

2b) Security and Privacy: The UID-based public key prevents the exposure of the total number of rows in a table, enhancing privacy and security.

3) Soft Deletes for Data Retention - The project adopts a soft-delete strategy for data management. Instead of permanently removing records from the database, items are marked as deleted. This approach allows for data recovery if needed and ensures compliance with legal and regulatory requirements.

4) Database Cleanup and Maintenance - The project includes automated routines for database cleanup and maintenance, ensuring optimal performance and data integrity and also GDPR compliance.

5) Decoupled services - The project architecture promotes decoupling of services, enhancing modularity and ease of maintenance. - This is implemented both inside the backend server as modules and in the entire microservice.