Interview Q&A

Short answer: ccess them in workflows: env: WS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: <<<<<<< HEAD your code ======= incoming code >>>>>>> branch

Real-world example (ShopNest)

Feature work for “UPI payment” lives on feature/upi-payment. Open a PR to main; resolve conflicts before merge.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: My preferred strategy depends on the project type and team size: For large enterprise projects with planned releases → I prefer Git Flow.

Explain a bit more

Branches: main, develop, feature/*, release/*, hotfix/* Benefits: Organized release management, clear isolation of features and fixes. For agile teams or startups deploying multiple times a day → I prefer Trunk-Based Development. Developers work on short-lived feature branches and merge into main frequently (often daily). CI/CD pipelines ensure code is always deployable. Real-world example: At my last company, we used Trunk-Based Development for a SaaS platform — it reduced merge conflicts and allowed fast continuous deployment.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: source code during software development.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Store tokens (like AWS_ACCESS_KEY, DOCKER_TOKEN) in → Settings > Secrets and variables > Actions Access them in workflows: env: AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: git config --global user.signingkey <key-id> git config --global commit.gpgsign true

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Integration means connecting your Git repository to your CI/CD system so every push, pull request, or tag triggers an automated build, test, and deploy pipeline.

Explain a bit more

✅ Jenkins Integration Install the Git plugin in Jenkins. Create a new pipeline job and link it to your Git repository: pipeline { agent any stages { stage('Checkout') { steps { git branch: 'main', url: } } stage('Build') { steps { sh 'npm install' sh 'npm test' }

Example code

}
}
} ● Jenkins polls Git or listens for webhooks to trigger builds automatically. ✅ GitLab CI/CD GitLab CI is built-in — simply create .gitlab-ci.yml: stages: test deploy test: script: npm install npm test deploy: script: ./deploy.sh only: main Every push triggers this pipeline automatically. ✅ GitHub Actions GitHub has its own YAML-based workflows: name: Node CI on: [push, pull_request] jobs: build: runs-on: ubuntu-latest steps: uses: actions/checkout@v4 run: npm ci run: npm test It runs directly in GitHub without needing extra setup. Real-world example: Your team pushes code to GitHub → GitHub Actions automatically runs tests → Jenkins (or GitLab CI) deploys to a staging environment → Approval required for production deploy.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: git cherry-pick <commit-hash>

Real-world example (ShopNest)

Prefer clear commits: fix(cart): prevent negative quantities instead of update.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: git switch -c hotfix/save-work

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: git checkout -b feature/login abc1234

Real-world example (ShopNest)

Feature work for “UPI payment” lives on feature/upi-payment. Open a PR to main; resolve conflicts before merge.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: dashboard). → This prevents misuse. Remove the secret from code: git rm --cached path/to/file git commit -m "Remove sensitive file"

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Accidentally pushing secrets (API keys, passwords, tokens) is serious — even if you delete them, they may still exist in commit history. Steps to fix it:

Real-world example (ShopNest)

Prefer clear commits: fix(cart): prevent negative quantities instead of update.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: git merge origin/main

Real-world example (ShopNest)

Feature work for “UPI payment” lives on feature/upi-payment. Open a PR to main; resolve conflicts before merge.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: After initializing a Git repo locally (git init), you can connect it to a remote repository (like one on GitHub) using: git remote add origin Then push your code: git push -u origin main Explanation: origin is just a nickname for the remote URL.

Explain a bit more

The -u flag links your local branch with the remote one so future pushes are easier (git push alone works after that). Real-world example: You create a local portfolio website and later decide to host it on GitHub. You connect your local repo to the remote one using git remote add origin so both stay in sync.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Mark the conflicting sections in your file: <<<<<<< HEAD your current branch code ======= incoming branch code >>>>>>> feature/new-ui

Real-world example (ShopNest)

Feature work for “UPI payment” lives on feature/upi-payment. Open a PR to main; resolve conflicts before merge.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: A Git tag marks specific points in a repository’s history — usually to label release versions (like v1.0, v2.1, etc.).

Explain a bit more

It’s like a snapshot that says, “this commit is stable and ready to release.” Types of tags: Lightweight tag: just a name for a commit. Annotated tag: includes metadata like the tagger’s name, date, and message. Commands: git tag -a v1.0 -m "Version 1.0 release" git push origin v1.0 Real-world example: After testing your project, you tag the commit representing your first release with v1.0. This helps other developers or CI/CD pipelines identify which version is live.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: <<<<<<< HEAD current branch code ======= incoming branch code >>>>>>> feature/contact-form

Real-world example (ShopNest)

Feature work for “UPI payment” lives on feature/upi-payment. Open a PR to main; resolve conflicts before merge.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: A branch in Git is like a separate line of development — a parallel universe for your code. It allows you to work on new features, bug fixes, or experiments without affecting the main codebase (usually called the main or master branch). Why branches are useful: They make collaboration easier by keeping each developer’s work isolated until it’s ready to be merged back. Real-world

Example code

Imagine your company website is live, but you need to add a “dark mode” feature. Instead of editing the main code directly (which might break the live site), you create a new branch called feature/dark-mode to work independently. Once it’s done and tested, you merge it back into main.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Git is a distributed version control system (VCS) that allows multiple developers to work on a project without overwriting each other's work.

Explain a bit more

It's designed to be fast, flexible, and scalable, allowing developers to track changes in code and collaborate with ease. In contrast, SVN (Subversion) is a centralized version control system. This means that SVN has one central repository, and developers check out code to work locally. Git, on the other hand, allows every developer to have their own full local repository, including the project’s history. This makes Git faster and more reliable, especially in distributed teams. Real-World Example: If you were working on a website project with a team, using Git allows each developer to clone the repository, make changes locally, and push their changes without disrupting others. In SVN, the code is pulled from the central server, and only one developer can commit changes at a time.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: A distributed version control system (DVCS) for tracking changes in source code during software development.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: git checkout wrong-branch git reset --hard HEAD~2

Real-world example (ShopNest)

Feature work for “UPI payment” lives on feature/upi-payment. Open a PR to main; resolve conflicts before merge.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: origin – The main remote repository you cloned or own. upstream – Usually refers to the original repository that your fork came from.

Example code

If you fork a popular open-source project: Your fork on GitHub = origin The original repo (the one you forked from) = upstream Commands to set both: git remote add origin git remote add upstream Why it matters: This setup lets you pull new changes from the main project (upstream) while pushing your changes to your fork (origin).

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Git is the tool used to track changes in your code locally (on your computer), whereas GitHub is a platform that hosts Git repositories online, enabling collaboration and sharing.

Explain a bit more

GitHub allows teams to work on Git-based projects in a central location, review code, and manage issues and pull requests. Real-World Example: You use Git to make changes to your website’s code locally. Once you're happy with your changes, you push them to GitHub so your team can see and review the updates. GitHub is essentially a cloud service that works on top of Git.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: pplication app = new Application(factory); pp.Render(); } } pplication app = new Application(factory); pp.Render(); } } pplication app = new Application(factory); pp.Render(); } } pplication app = new Application(factory); pp.Render(); } }

Real-world example (ShopNest)

ShopNest’s NotificationFactory creates Email or SMS senders based on user preference.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Product 1 Product 2 Product 3 How It Works:

Real-world example (ShopNest)

Use a GoF pattern in ShopNest only when it removes duplication or makes a change safer—explain the problem it solves in the interview.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.