Presentation, group discussion and interview skills notes — Unit 5

While written communication provides a permanent record, oral communication is the primary method for immediate information exchange, persuasion, and relationship building in the corporate world.

For engineers, possessing brilliant technical skills is useless if you cannot verbally explain your ideas to managers, clients, or investors.

• Advantages: Immediate feedback (clarification), faster decision making, conveys emotion and tone.
• Disadvantages: No permanent record (unless recorded), prone to distortion, requires immediate thinking.

A formal presentation is structured speaking designed to inform, persuade, or build goodwill. A successful presentation relies on three pillars:

• 1. The Presenter: Your confidence, voice, and body language.
• 2. The Content: The logical structure of your arguments and the data you provide.
• 3. The Visual Aids: The slides (PowerPoint/Keynote) that support your words.

If any one of these pillars is weak, the entire presentation fails.

Before writing a single slide, you must analyze who you are speaking to. A presentation on Blockchain will sound vastly different if given to high-school students versus senior software architects.

⇒Factors to Analyze:

• Demographics: Age, gender, cultural background.
• Knowledge Level: Are they experts? If not, avoid heavy technical jargon.
• Attitude: Are they friendly, neutral, or hostile (e.g., defending a delayed project)?
• Expectations: Why are they sitting in the room? What do they want to learn?

A professional presentation follows a strict 3-part structure:

• 1. Introduction (15%): Hook the audience, state your objective, and provide a "roadmap" of what you will cover. ("Tell them what you are going to tell them.")
• 2. Main Body (75%): Deliver the core content logically. Use data, examples, and smooth transitions between points. ("Tell them.")
• 3. Conclusion (10%): Summarize the main points, state the final recommendation, and end with a strong closing statement. ("Tell them what you told them.")

Slides are there to support YOU, not replace you. The audience should be listening to you, not reading your slides.

⇒Best Practices:

• Use large, readable Sans-Serif fonts (Arial, Calibri). Minimum size 24pt.
• Maintain high contrast (Dark text on a light background, or vice versa).
• One idea per slide.
• Use high-quality images and graphs instead of blocks of text.

Studies suggest that over 50% of communication is non-verbal. Your body speaks before your mouth does.

⇒Kinesics (Body Language):

• Posture: Stand straight. Slouching shows a lack of confidence.
• Eye Contact: The most critical element. Look directly at individuals in the audience for 2-3 seconds. Do NOT read from the screen or stare at the floor.
• Gestures: Use natural hand movements to emphasize points. Avoid crossing your arms (defensive) or keeping hands in pockets (unprofessional).

Paralanguage refers to how you say the words, not the words themselves. It includes:

• Volume: Speak loud enough for the person in the very back row to hear you without straining.
• Pitch: Vary your high and low tones. A flat, monotone voice will put the audience to sleep within minutes.
• Pace: Do not rush. Speak slightly slower than your normal conversational speed.
• Pauses: Use silent pauses after an important point to let it sink in. Do NOT fill silence with "um," "uh," or "like" (filler words).

The Question & Answer session usually happens at the end and is where your true competence is tested.

• Listen to the entire question without interrupting.
• Briefly repeat the question so the whole room hears it.
• Answer concisely and directly to the person who asked.
• If you don't know the answer, do not lie or guess. Say, "That's an excellent question. I don't have the exact data right now, but I will find out and email you by this afternoon."

A Group Discussion (GD) is a formal discussion conducted by companies during the hiring process. A group of 8-12 candidates is given a topic (technical, social, or abstract) and asked to discuss it for 15-20 minutes.

⇒Why do companies use GDs?

It is an elimination round to filter out candidates who lack interpersonal skills. Evaluators look for:

• Communication skills and clarity of thought.
• Leadership and team-building abilities.
• Listening skills (crucial!).
• Ability to handle disagreements without becoming aggressive.

Candidates naturally fall into certain roles during a GD. Aim for the positive ones:

• The Initiator: Starts the GD, defines the topic, and sets the direction. Gets bonus points for leadership, but ONLY if they actually understand the topic.
• The Contributor: Provides solid facts, data, and logical arguments.
• The Moderator: Steers the group back on track when they go off-topic. Encourages quiet members to speak. (Highly rated by HR).
• The Summarizer: Concludes the GD by summarizing the main points agreed upon by the group in the last 60 seconds.

⇒DO:

• Maintain eye contact with the other group members, NOT the evaluators.
• Listen actively and nod when others speak.
• Enter the discussion by politely building on someone else's point: "I agree with John, and I'd like to add..."

⇒DON'T:

• Do not yell, point fingers, or aggressively cut people off.
• Do not dominate the entire 15 minutes. Speak 3 or 4 times, delivering high-quality points.
• Do not completely change your stance just to agree with the majority.

An interview is a formal, in-depth conversation conducted to evaluate your acceptability for employment.

It is a two-way street: The company is evaluating if you are fit for the role, and you are evaluating if the company is fit for your career.

Preparation is everything. 90% of interview success happens before you walk into the room.

• Technical Interview: Tests your hard skills. You may be asked to write code on a whiteboard, solve algorithms, or explain engineering concepts.
• HR Interview: Evaluates your cultural fit, salary expectations, and soft skills.
• Panel Interview: You face multiple interviewers at once. Rule: Address your answer primarily to the person who asked, but maintain brief eye contact with the rest.
• Stress Interview: The interviewer acts aggressive, dismissive, or asks bizarre questions to see if you break under pressure. Stay calm and polite.

• 1. Research the Company: Know what they build, their recent news, and their competitors. If you don't know what the company does, you will be rejected immediately.
• 2. Review the Job Description: Map your skills directly to the requirements listed in the JD.
• 3. Know your Resume: Be prepared to defend and explain in detail ANY project or skill listed on your resume. If you lie on your resume, the technical round will expose you.

This is almost always the first question. It sets the tone for the entire interview.

⇒The Present-Past-Future Formula:

• Present: Where you are right now (e.g., Final year CSE student at XYZ University).
• Past: Highlight 1 or 2 major technical achievements or projects that prove your skills.
• Future: Why you are excited about this specific role at this specific company.

Behavioral questions ask how you acted in specific past situations, based on the premise that past behavior predicts future behavior.

Examples:

• "Tell me about a time you failed."
• "Describe a situation where you had a conflict with a team member."
• "Tell me about a time you met a tight deadline."

You MUST answer these using the STAR Method.

The STAR method is a universally accepted framework for answering behavioral questions logically without rambling.

• S - Situation: Briefly set the scene. Give context. (e.g., "During my final year project...")
• T - Task: Explain what your specific responsibility or challenge was. (e.g., "We had to deploy the app, but the database crashed 2 days before the deadline.")
• A - Action: What specific steps did YOU take to fix it? Use "I", not "We". (e.g., "I stayed late, rewrote the queries, and migrated to AWS.")
• R - Result: What was the outcome? Use numbers if possible. (e.g., "We delivered on time and got an A grade.")

• Handshake: Firm, web-to-web, accompanied by eye contact and a smile. (Don't crush their hand, don't give a "dead fish" handshake).
• Posture: Sit up straight, lean slightly forward to show interest.
• Hands: Keep them visible on the table. Do not fidget with a pen or touch your face (indicates nervousness or lying).
• Eye Contact: Essential for building trust, but don't stare unblinkingly.

At the end, the interviewer will ask: "Do you have any questions for us?"

⇒Good questions to ask:

• "What does a typical day look like for a junior developer here?"
• "What is the biggest technical challenge your team is facing right now?"
• "What tech stack will this role primarily be working with?"

Avoid asking about salary or holidays in the first technical round; save that for HR.

⇒Unit 5 Mastery

• What is the 6x6 rule for presentation slides?
• Explain Kinesics and Paralanguage.
• What are the roles of the Initiator and Moderator in a GD?
• List three "Don'ts" for a Group Discussion.
• Explain the Present-Past-Future formula for introducing yourself.
• Break down the acronym STAR for behavioral interviews.