DEV Community: Lokesh

How to make a Job Switch in IT( For Newbies)

Lokesh — Thu, 08 Jul 2021 08:49:35 +0000

Hi, I'm Lokesh, a Full Stack Developer with over two years of experience. The tech stack I specialize in are Java, Javascript, SQL, REST API and React.js. In this post, I will be detailing my personal experience with job migration. This post will help you effortlessly sail through the processes of creating effective resumes up to salary negotiation. The details or information that I've shared are purely based on my observation and will be best suited for entry-level developers looking for new opportunities.

Why Change?

As entry-level developers working in an established company, many of us don't get hands-on experience during product development. I faced this issue while working in my previous company, so I decided it was time to venture into a new environment.

My day to day work looked like this:

Perform unit testing of the newly developed features by senior developers.
Write automation test cases.
Documenting the features to be implemented.
Maintain and fix issues in already existing features.

Performing the above tasks allowed me to have a better understanding of the product. However, after a certain period, I found myself doing nothing but this, leaving me stranded with no room for growth.

If you find yourself doing dull and monotonous assigned tasks for a considerable period, it's time to rethink your employment with that company. Ultimately, it is your job to ensure that you learn about new technology and to make certain that you're on par with the market requirement.

There are two factors to consider before switching a job

Job satisfaction
Salary

Having both is Great
Having either one is Good
Not having both is when you have to make a decision.

How to prepare and apply?

The "How?" part is the most challenging task. It nearly took me a year to figure this out on my own since there is no general template for preparing for software development interviews. After a tremendous amount of time and effort, I was able to simplify and list out the various steps required to prepare for the switch:

1. Have a proper Resume and LinkedIn profile.

Before preparing for an interview, create a legitimate resume and a LinkedIn profile. Having an engaging LinkedIn profile is essential for a Software Developer regardless of your employment status. The resume you submit should be realistic and descriptive, detailing your skills and experience. Add only the skills which are your strong suits and come under your forte of specialization. For example: If you only know how to create a button in React.js don't add it to your profile. The interviewer will expect you to have a piece of working knowledge in your mentioned skills.

2. Devise a proper time plan for switching

Most of us working in IT may not have satisfying jobs. The job which was interesting last year might have gotten worse this year. Maybe you had a clash with your team. Everyone has their reasons, but once you have identified them, you will need a change. I suggest you do it straight away. Delaying it due to procrastination or any other personal reasons will affect your peace of mind and your career in the long term. Find at least 1-2 hours a day for your preparation.

A typical job switch in IT should be done within a maximum of 3 months. If you are taking more time than this, you are never gonna switch your job. I've given the sample plan which I used during my preparation.

3. Plan your syllabus and practice

The requirement for a Full Stack Developer with 2 years of experience in the market is

Basic Problem Solving
Data Structures
- String & Arrays
- Linked Lists
- Stack
- Queue
- Tree ( BT & BST )
- Graph ( DFS & BFS )
Algorithms
- Greedy algorithms
- BackTracking algorithms
Basic Knowledge on
- System Designs & Design Pattern
- Computer Networks
- Operating Systems
- DBMS & Database Modelling
- REST API

To identify the skills required according to your field of expertise and experience check the job description listed in the portals and make a consolidated list of most repetitive skills in the descriptions and frame your syllabus accordingly.

Once you have framed the syllabus it is essential to stick to the plan and spend at least 2 hours per day preparing. While preparing for a job interview your work efficiency will most probably be affected. It is better not to worry about it during this time but also don't let the preparation completely spoil your work.

Some of the best coding preparation sites I used

After learning the concepts try to attend mock interviews, where peers interview each other on various topics. Use the below-listed sites for free mock interview sessions.

3. Applying for companies

In the last image, you will notice that I've mentioned applying for companies in which you may not desire to work. Yes, you cannot always clear the first interview you are trying. Most MNC's have policies that restrict you from attending multiple interviews within 3 - 6 months. So instead of spending your attempts on dream companies, do trial runs with all the other companies.

How to identify a good company?

I generally classified the companies which I applied like this

Check the review of the companies in websites like Glassdoor, LinkedIn and if it is a startup you can find their fundings in sites like TechCrunch and AngelList

Where to apply?

LinkedIn : Getting an interview call after applying in the LinkedIn Jobs portal is nearly impossible. Since a lot of people apply on LinkedIn, It is very unlikely to get your profile shortlisted. The best way to find jobs through LinkedIn is by networking and making connections with HRs and Product Managers who post Job openings in their team. There is a better chance that you could get your profile shortlisted in this way.

Request your connections to refer you for a role in that company. While seeking help, be polite, find the job posting on the respective company's careers site and attach the Job ID and Resume with a personal note.

Create a profile on these sites with appropriate details. These are some of the best sites which helped me during the process.

How to negotiate salary?

As a fresher, we wouldn't have negotiated our salary compensation for our first job because it is fixed in most of the companies. Since it is our first negotiation it might be tricky. The main points to remember while negotiating salary are

Most skilled HR's won't mention the numbers on their minds upfront. If HR was willing to offer you 15LPA, you don't want to turn out asking for just 12LPA. So, explain your skills and experience, let HR know what kind of assets you will be bringing to the company's table, and try to get the numbers from them.
So if HR is keen on getting you to mention the number, make sure to check beforehand websites like Glassdoor and Payscale to find the packages offered to their employees, or if you have a friend in the company you are applying to, get the details from them. In my observation, the standard hike while switching a company should be a minimum of 30% and occasionally based on your performance, it can go up to 120%.

Counter Offer: If your current CTC is X LPA and you have an offer in hand from Company A for Y LPA(30% from X). Now If Company B is offering you a job you can demand 30% from Y.

Current CTC: 10LPA(X)
Offer from Company A: 13LPA(Y)
Leveraged Offer from Company B: 16.9LPA ( More than 60% hike from your Current CTC)

There are only a limited number of job switches that we make in our entire career, reaching these pay scale working in the same company takes a long time to achieve, so try to make every job switch count. I did not know such a concept existed until I attended interviews for numerous companies. So, if you are planning to make your first switch, do not lose sight of all these points.All the best!

Please feel free to contact me for any queries related to creating resume or switching jobs on LinkedIn : Lokesh Kumar

File Structure of a Node Project

Lokesh — Mon, 21 Sep 2020 14:10:34 +0000

In this article I am going to share the details about the structure of a Node project which could be maintained during the development for easier identification and better understanding.

1. package.json

{
  "name": "node",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "start": "node src/index.js",
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "dependencies": {
    "express": "^4.17.1"
  }
}

package.json is a mandatory file present in the root directory of the project
package.json holds all the metadata and dependencies required for a project. It can be created by running the following command in the root directory

 npm init -y

-y specifies do not ask me any question simply create the file.

you can specify the script which should be executed for starting the node project in scripts -> start and for stopping in scripts -> stop

"scripts": {
    "start": "node src/index.js",
    "test": "echo \"Error: no test specified\" && exit 1"
  }

and simply start and stop the node project using

npm start
npm stop

To install all the required node dependancies in package.json

sudo npm install

If Error: EACCES: permission denied error occurs

sudo npm install -g --unsafe-perm=true --allow-root

2. .env

.env file contains all the environment variables required for a project

APP_NAME = node-project
NODE_ENV = development
PORT = 3003
JWT_SECRET = '$2a$0sdfwewewerbN2Jf2UcG'
JWT_KEY = 'ewrwetiLCJjb21wYW55IjoiQWlyN3NlYXMtwetPpcuKZCtFE4k'
LOCAL_DB_URI = mongodb://localhost:27017/db_api
SERVER_DB_URI = mongodb+srv://cezDbAdmin:cezDbAsdd@development-we.gcp.mongodb.net(opens in new tab)/cdez?retryWrites=true&w=majority

CONTACT_API_HOOK = http://api.node-app.dev/contactserver/api/v1
CONTACT_API_HOOK1 = http://127.0.0.1:3003/contactserver/api/v1

ALERT_MAIL = 'noreply@gmail.com(opens in new tab)'
FIREBASE_REDIRECT_URL='http://localhost:8080/dashboard'

MAIL_API_HOOK = http://api.node-project.dev/mailserver/api/v1
ALERT_MAIL='Node project <alerts@node-project.com>'

3. server.js

server.js is the file which will be executed first in a node project. If you are using mongoDB the promise for the DB connection should be established here.

export const start = () => {
  init()
    .then(app => {
      app.listen(port, () => {
        let server =
          (env === "secure" ? "https://" : "http://") + host + ":" + port;
        console.log(
          chalk.green("Development server started on " + server)
        );
      });
    })
    .catch(err => {
      console.error(err);
    });
};

module.exports = start();

4. .gitignore

git ignore file should contain the list of files that should not be committed in a git push.

/node_modules
/public/hot
/public/storage
/storage/*.key
/.idea
/.vagrant
/.vscode
npm-debug.log
yarn-error.log
.env

5. index.js

index.js is most likely the entry point for requiring a module. In Node.js, Node itself is the web server so you don't need to name anything index.js but it's easier for people to understand which file to run first.

index.js typically handles your app startup, routing and other functions of your application and does require other modules to add functionality. If you're running a website or web app it would also handle become a basic HTTP web server.

let express = require('express')
let app = express()

let personRoute = require('./routes/person')
app.use(personRoute)
app.use(express.static('public'))

const PORT  = process.env.PORT || 3050
app.listen(PORT,()=> console.info(`Server has started on ${PORT}`))

6. app

The app folder should contain all the files of the project in an orderly format. The files should be organised into folders such as
- Routers : Which contains all the files related to routing Ex: AuthRouter.js

import Router from "koa-router";
import RoleController from "../controllers/RoleController";
import Authentication from "../Process/Authentication"

const router = new Router();

router.prefix("/iamserver/api/v1");
router
.use(Authentication.authorize)
.post("/roles", RoleController.create)
.put("/roles/:role", RoleController.update)
.delete("/roles/:role", RoleController.destroy)
export default router;

Controllers : should receive all the routing from routers Ex: RoleController.js

"use strict";
import Controller from "../../Controller";
import Company from "../models/Company"

class RoleController extends Controller {

        async getCompanies(ctx){
            try {                
                ctx.body = await Company.allCompanies()
            }
            catch (err) {
                ctx.throw(err)
            } 
        } 
    }

    export default new RoleController();

Models : Files in this folder should contain the entity related operation such as accessing DB, processing based on business logic. Ex : Company.js

import CompanySchema from "../../database/schema/CompanySchema";

class Company extends Database {
    constructor() {
        super(CompanySchema);
    }
    async allCompanies(){
        return  this.model.find().populate('users')
    }
}

export default new Company();

Configuring VSCode with GitHub

Lokesh — Wed, 09 Sep 2020 17:50:32 +0000

1. Install git scm to your machine

sudo apt install git-all

2. Create a new GitHub repository

3. Ensure git is enabled in your VSCode settings

4. Add a Remote

CTRL+SHIFT+P > Add Remote
Paste your GitHub repo url ex: https://github.com/DevLCodes/acrux-pharma-site.git
Add a remote name

5. Pull all the initial changes

First commit the changes present in your local system and run

git pull <repo-name> master --allow-unrelated-histories

6. Commit all your changes to GitHub

Stage the changes that you want to commit , commit and push to the remote to which you want to add your changes.

Clone a GitHub Repository

git clone <repo-url>

Uninstall git from Ubuntu

sudo apt-get remove git