Interview Q&A

Short answer: lso increases the risk of downtime during upgrades.

Real-world example (ShopNest)

ShopNest’s SQL Server database stores customers, products, and orders. Good indexes and clear foreign keys keep checkout queries fast and safe.

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: Use case: When you only want matching records.

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: Understand the source and target databases, and map the data models. Identify data transformations, such as type conversions or renaming columns.

Real-world example (ShopNest)

ShopNest’s SQL Server database stores customers, products, and orders. Good indexes and clear foreign keys keep checkout queries fast and safe.

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: Use tools like Liquibase, Flyway, or Alembic to manage and version schema changes. These tools allow you to write migrations in SQL or as scripts that can be version-controlled. These tools can apply, track, and rollback schema changes.

Real-world example (ShopNest)

ShopNest’s SQL Server database stores customers, products, and orders. Good indexes and clear foreign keys keep checkout queries fast and safe.

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: All tenants share the same database and tables. A tenant identifier (e.g., tenant_id) is used to segregate data. Pros: Easier to maintain and scale. Cons: Can lead to security and data isolation issues.

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 common pattern where one record in a table can be associated with multiple records in another table. Example: A Customer can have many Orders, but each Order can belong to only one Customer.

Real-world example (ShopNest)

ShopNest’s SQL Server database stores customers, products, and orders. Good indexes and clear foreign keys keep checkout queries fast and safe.

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: Create indexes on columns that are used in WHERE clauses, JOIN conditions, and ORDER BY clauses. Use covering indexes to avoid full table scans and improve performance.

Real-world example (ShopNest)

ShopNest adds an index on Orders(CustomerId, CreatedAt) because “my recent orders” is queried constantly.

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: Use EXPLAIN or QUERY PLAN to analyze query execution times and identify slow queries. Track metrics like response time, execution time, and query throughput.

Real-world example (ShopNest)

ShopNest adds an index on Orders(CustomerId, CreatedAt) because “my recent orders” is queried constantly.

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: Sharding involves splitting data into smaller, more manageable pieces called shards.

Explain a bit more

Each shard is stored on a different server (or cluster) to distribute the load. Typically, horizontal partitioning is used in sharding, where rows (rather than columns) of a database table are distributed across multiple databases. Example: A user table could be sharded by user ID, where all users with IDs 1-1000 are stored in one database, 1001-2000 in another, and so on.

Real-world example (ShopNest)

ShopNest’s SQL Server database stores customers, products, and orders. Good indexes and clear foreign keys keep checkout queries fast and safe.

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: Vertical scaling means upgrading the resources (CPU, RAM, disk space) of a single database server. Advantages: Simple to implement since you only need to upgrade the existing server. Disadvantages: There is a physical limit to how much you can scale up. It also increases the risk of downtime during upgrades.

Real-world example (ShopNest)

ShopNest’s SQL Server database stores customers, products, and orders. Good indexes and clear foreign keys keep checkout queries fast and safe.

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: One database (master) handles all writes, while one or more secondary databases (slaves) replicate the data for read queries and redundancy. Advantages: Load balancing for read-heavy applications, fault tolerance. Disadvantages: Writes are still a single point of failure.

Real-world example (ShopNest)

ShopNest’s SQL Server database stores customers, products, and orders. Good indexes and clear foreign keys keep checkout queries fast and safe.

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: SQL Server Agent: Use SQL Server Agent to schedule backup jobs.

Example code

Create a backup job in SQL Server Management Studio (SSMS) to run daily, weekly, or at specific intervals. Script for automated backups: BACKUP DATABASE MyDatabase TO DISK = 'C:\Backups\MyDatabase.bak';

Real-world example (ShopNest)

ShopNest’s SQL Server database stores customers, products, and orders. Good indexes and clear foreign keys keep checkout queries fast and safe.

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 full backup includes all the data in the database at the time the backup is taken. It is a complete snapshot of the database. Advantages: Easy to restore; ensures a full copy of the database. Disadvantages: Larger in size and takes more time compared to other backup types. Example: This backup is typically taken on a regular schedule, like daily or weekly.

Real-world example (ShopNest)

ShopNest’s SQL Server database stores customers, products, and orders. Good indexes and clear foreign keys keep checkout queries fast and safe.

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: data. Use tools like gpg, or built-in encryption features (e.g., SQL Server Backup Encryption, PostgreSQL using pg_dump with -Fc and encrypting the output file).

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: Entities: Products, Customers, Orders, Payments, ShoppingCart, Categories,? is a common interview topic in SQL & Databases. Give a clear definition, then one concrete example.

Real-world example (ShopNest)

ShopNest’s SQL Server database stores customers, products, and orders. Good indexes and clear foreign keys keep checkout queries fast and safe.

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: redundancy by eliminating unnecessary duplication.

Real-world example (ShopNest)

Product and Category are separate tables (normalized). The order line stores product id + price snapshot—not a giant duplicated product blob.

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: Handling errors in React is done using Error Boundaries.

Explain a bit more

They are React components that catch JavaScript errors anywhere in their child component tree and log those errors or display a fallback UI. Example of Error Boundary: class ErrorBoundary extends React.Component { constructor(props) { super(props); this.state = { hasError: false }; } static getDerivedStateFromError(error) { return { hasError: true }; // Update state to trigger fallback UI } componentDidCatch(error, info) { console.error(error, info); } render() { if (this.state.hasError) {

Example code

return <h1>Something went wrong!</h1>;
}
return this.props.children;
}
} You wrap your components inside ErrorBoundary to catch and handle errors gracefully.

Real-world example (ShopNest)

ShopNest’s storefront is React: components for ProductCard, CartDrawer, and CheckoutForm, with hooks for local UI state.

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: To optimize React apps for SEO (Search Engine Optimization):

Real-world example (ShopNest)

ShopNest’s storefront is React: components for ProductCard, CartDrawer, and CheckoutForm, with hooks for local UI state.

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: React uses the Virtual DOM to handle updates. When state or props change, React creates a new virtual DOM, compares it to the previous version, and calculates the most efficient way to update the actual DOM. Steps:

Real-world example (ShopNest)

ShopNest’s storefront is React: components for ProductCard, CartDrawer, and CheckoutForm, with hooks for local UI state.

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: new virtual DOM, compares it to the previous version, and calculates the most efficient way to update the actual DOM. Steps: new virtual DOM, compares it to the previous version, and calculates the most efficient way to update the actual DOM. Steps:

Real-world example (ShopNest)

ShopNest’s storefront is React: components for ProductCard, CartDrawer, and CheckoutForm, with hooks for local UI state.

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: You can use libraries like react-dnd or react-beautiful-dnd for drag-and-drop functionality. Example with react-beautiful-dnd: npm install react-beautiful-dnd import { DragDropContext, Droppable, Draggable } from 'react-beautiful-dnd'; function App() { const items = ['item1', 'item2', 'item3'];

Example code

return ( <DragDropContext onDragEnd={() => {}}> <Droppable droppableId="droppable"> {(provided) => ( <ul ref={provided.innerRef} {...provided.droppableProps}> {items.map((item, index) => ( <Draggable key={item} draggableId={item} index={index}> {(provided) => ( <li ref={provided.innerRef} {...provided.draggableProps} {...provided.dragHandleProps} {item} </li> )} </Draggable> ))} {provided.placeholder} </ul> )} </Droppable> </DragDropContext> ); }

Real-world example (ShopNest)

ShopNest’s storefront is React: components for ProductCard, CartDrawer, and CheckoutForm, with hooks for local UI state.

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: React.lazy enables you to dynamically import components only when they are needed, enabling code splitting and lazy loading.

Explain a bit more

const LazyComponent = React.lazy(() => import('./LazyComponent')); function App() { return ( <React.Suspense fallback={<div>Loading...</div>}> <LazyComponent /> </React.Suspense> ); } Suspense is a wrapper around lazy-loaded components that shows a loading fallback while the component is being loaded.

Real-world example (ShopNest)

ShopNest’s storefront is React: components for ProductCard, CartDrawer, and CheckoutForm, with hooks for local UI state.

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: For most tech roles, one page is ideal up to around 5 to 7 years of experience, while two pages may be justified for senior profiles with strong breadth. The goal is not page count; it is relevance density. Keep only what supports the target role.

Step-by-step approach

1. Start with one page and expand only if removing content hurts role-fit clarity.
2. Prioritize last 5 to 8 years and compress older experience into short summaries.
3. Limit each role to high-impact bullets instead of full task history.
4. Move less relevant certifications and coursework to concise sections.
5. Check that first half page already shows role match and impact.
6. Ask a peer to do a 20-second scan test for relevance.

Real-world example

Ananya had a 3-page resume for a 4-year profile at Infosys. Vikram from Freshworks asked her to trim repetitive points and keep only role-matching achievements. She reduced it to 1.2 pages with stronger metrics and cleaner sectioning. Recruiters started responding faster because the core story became obvious.

Mistakes to avoid

• Assuming longer resume automatically looks more experienced.
• Removing key achievements just to force one page.
• Keeping outdated internships for senior roles.
• Duplicating same project details across sections.

Length should follow relevance, not ego.

Short answer: Project descriptions must show problem, your contribution, tech choices, and measurable outcomes. Most resumes fail because they list features, not impact. Write each project bullet so an interviewer can ask deeper follow-up immediately.

Step-by-step approach

1. Begin with the project objective and user/business context in one line.
2. Mention your exact ownership, not generic team-level contribution.
3. Include key tools and architecture choices only when relevant.
4. Add quantifiable outcome like latency, reliability, revenue, or adoption change.
5. Use strong action verbs and remove filler words.
6. Prepare a deeper verbal walkthrough for interview follow-ups.

Real-world example

Meera listed projects as "worked on dashboard module" with no details. Rohit from CRED asked her to rewrite each project around problem-solution-impact format. She added metrics like 27% faster report generation and 19% drop in support escalations. Interviewers began asking architecture questions instead of basic clarifications.

Mistakes to avoid

• Describing project as a feature list without context.
• Not clarifying individual contribution in group projects.
• Skipping outcomes and business effect.
• Using too much low-signal technical jargon.

Problem-action-impact beats feature-technology list.

Short answer: For developers, reverse-chronological format works best because it highlights recent technical depth and growth trajectory. Keep sections predictable so both ATS and engineering managers can scan quickly. Strong developer resumes prioritize impact, stack relevance, and project ownership.

Step-by-step approach

1. Use this section order: Summary, Skills, Experience, Projects, Education, Certifications.
2. Keep experience entries reverse-chronological with clear dates and roles.
3. Write concise bullets with action verbs, tools used, and measurable impact.
4. Show architecture or scale details for senior roles where relevant.
5. Add GitHub and portfolio links near header for quick validation.
6. Ensure consistent formatting across all headings and bullet styles.

Real-world example

Neha used a design-heavy functional resume while applying from CRED to product companies. Arjun at Flipkart suggested switching to a reverse-chronological engineering-friendly format with cleaner project metrics. She also moved technical skills above education for faster relevance scanning. Recruiters responded more quickly after the format change.

Mistakes to avoid

• Choosing visual templates over parse-safe technical clarity.
• Hiding recent relevant roles below less important sections.
• Combining unrelated stacks in a single undifferentiated skills block.
• Using inconsistent tense and formatting.

Engineer resume format should optimize scan speed.