Graduate Engineer Trainee

Tip 1: Explain with a simple example like a student table where student info and course info are in one table. Then show how normalization splits it into smaller, meaningful tables (e.g., Students and Courses).
Tip 2: Start with "why" normalization is needed—to avoid redundancy, maintain data integrity, and improve performance. Interviewers like candidates who understand why, not just what.
Tip 3: Clearly differentiate each normal form in a step-by-step manner, and don’t try to overcomplicate it with unnecessary technical jargon. Clean, simple definitions show clarity of concept.

Step 1: I first thought about using a dictionary to store character counts.
But then I realized this wouldn't maintain the order or handle consecutive repetition properly.
Step 2: I changed my approach and started iterating through the string from left to right. I used a loop to count how many times the current character is repeating consecutively.
Step 3: For each character, I added it to the result string. If its count was more than 1, I added the count next to it.
Step 4: I implemented this logic using a simple while loop and string concatenation. The interviewer liked how I optimized the approach to run in O(n) time with O(1) extra space (ignoring output).

Tip 1: Read regularly about system designs.
Tip 2: Think About Database Design.
Tip 3: Define High-Level System Architecture.

Tip 1: Practice DBMS regularly.
Tip 2: Solve questions online.

Tip 1: Study OS concepts daily.
Tip 2: Add a small real-life example to explain clearly.

Step 1: Create a hashmap to store number → index.
Step 2: For each element x, check if target - x exists in the map.
Step 3: If found, return their indices.

Step 1: Create a dummy node, use a current pointer.
Step 2: Compare heads of both lists, append smaller to current, move pointer.
Step 3: Append remaining elements.

Step 1: Initialize max_sum = current_sum = arr[0].
Step 2: For each element, update current_sum = max(x, current_sum + x).
Step 3: Update max_sum if current_sum is greater.

Tip 1: Start with your education and technical background (make it relevant to the role).
Tip 2: Mention key skills, certifications, or projects you've worked on (briefly).
Tip 3: End with your career goal or why you are excited about the opportunity.

Tip 1: Choose real strengths that are relevant (like teamwork, communication, quick learning).
Tip 2: Pick a weakness that is minor and show how you're working to improve it.
Tip 3:Be honest but positive — never sound careless.

Tip 1: Show career growth, not job-hopping.
Tip 2: Align your goals with the company's goals (example: growing technically, leadership roles).
Tip 3: Be realistic and show ambition.

Tip 1: Mention values, culture, or recent achievements.
Tip 2: Show alignment with your career path.
Tip 3: Avoid generic answers like "good reputation."

Tip 1: Highlight key skills/achievements. Match them to job requirements.
Tip 2: Emphasize how you’ll contribute to the team.
Tip 3: Be concise and confident: No need to oversell.

Tip 1: Always say yes. It shows engagement.
Tip 2: Ask thoughtful questions about growth, team culture, or projects.
Tip 3: Avoid salary/leave topics early.