Virtual Meeting Etiquette Best Practices: A Developer Guide

The three highest-impact virtual meeting practices are: test your audio and video before every call, mute when not speaking, and always review the agenda beforehand. These habits alone eliminate the most common meeting friction for remote developer teams. This guide goes deeper with platform-specific shortcuts, automation scripts for meeting prep, and etiquette guidelines for screen sharing, camera use, and post-meeting follow-up.

Pre-Meeting Preparation

The foundation of meeting etiquette begins before the meeting starts. Taking a few minutes to prepare significantly improves meeting quality for everyone involved.

Test Your Setup Before Joining

Technical failures during meetings waste everyone’s time. Create a quick verification script to check your audio and video before every important call:

#!/bin/bash
# Quick meeting readiness check
echo "=== Meeting Setup Check ==="

# Test microphone
echo "Testing microphone..."
arecord -d 1 -q /dev/null && echo "✓ Microphone working" || echo "✗ Microphone issues"

# Test speakers
echo "Testing speakers..."
speaker-test -t sine -f 440 -l 1 -q 2>/dev/null && echo "✓ Speakers working" || echo "✗ Speaker issues"

# Check camera
echo "Checking camera..."
v4l2-ctl --list-devices 2>/dev/null | grep -q "Video" && echo "✓ Camera detected" || echo "✗ No camera found"

# Network latency check
ping -c 3 $(echo $(ip route | grep default | awk '{print $3}') | head -c -1) 2>/dev/null
echo "Network check complete"

On macOS, use the system audio settings to verify input and output devices. On Windows, the Sound settings provide a similar verification interface. Spending 30 seconds on this check prevents the awkward “can you hear me now?” exchanges that plague many meetings.

Review the Agenda and Relevant Materials

When you’re invited to a meeting with an agenda, actually read it. If no agenda exists, that itself is a red flag. For developer-focused meetings, this means:

This preparation shows respect for everyone’s time and enables more productive discussions.

During the Meeting: Core Etiquette Rules

Camera Etiquette

Camera presence significantly impacts meeting dynamics. The general rule: keep your camera on for meetings with fewer than eight participants. For larger meetings, camera is optional but encouraged when speaking.

When your camera is on:

# Simple OBS virtual camera setup for Linux
# This creates a filtered virtual camera for consistent appearance
obs --startrecording --scene "Presentation" --filter "color correction: brightness=1.1"

Audio Best Practices

Mute when not speaking. This seems obvious, but many meetings suffer from background noise, keyboard typing, or echo from unmuted participants. Most platforms show clear mute indicators—use them:

When speaking, slightly lean toward your microphone for clarity. If using a headset with a boom microphone, position it two finger-widths from your mouth.

Screen Sharing with Purpose

When screen sharing, close unnecessary applications and disable notifications. For developer meetings, this includes:

# macOS: Disable notifications before screen share
# Run this in Terminal
osascript -e 'tell application "System Events" to set do not disturb to true'

On Linux, use notify-send --urgency=low "" "" or disable notifications via your desktop environment’s settings.

When presenting code:

Meeting Participation for Developers

Active participation improves meeting outcomes. Use these strategies:

Automation for Meeting Efficiency

Developers can automate many meeting-related tasks to improve consistency and save time.

Calendar Integration

Set up automated meeting reminders that include prep tasks:

# Example: Calendar event prep checklist generator
def generate_prep_checklist(meeting_title, has_code_review=False, has_demo=False):
    checklist = [
        f"Review agenda for: {meeting_title}",
        "Check audio/video setup",
        "Close unnecessary applications",
    ]
    
    if has_code_review:
        checklist.extend([
            "Pull latest changes",
            "Run tests locally",
            "Note specific feedback points"
        ])
    
    if has_demo:
        checklist.extend([
            "Test demo environment",
            "Prepare backup slides",
            "Verify screen share permissions"
        ])
    
    return checklist

Automated Status Updates

For recurring meetings, use status scripts that prepare your environment:

#!/bin/bash
# Meeting mode: optimize system for video call
# Add to your path and run before meetings

# Close resource-heavy applications
pkill -f "chrome" 2>/dev/null || true
pkill -f "slack" 2>/dev/null || true

# Set do not disturb
defaults write com.apple.notificationcenterui doNotDisturb -boolean true

# Optimize audio
sudo sysctl -w net.inet.tcp.delayed_ack=0 2>/dev/null || true

echo "Meeting mode activated"

Platform-Specific Tips

Zoom

Zoom remains the most feature-rich option for developer meetings. Key shortcuts to memorize:

Enable “HD” and “Touch up my appearance” in settings for better video quality.

Google Meet

Google Meet integrates tightly with Google Workspace. For developers:

Microsoft Teams

Teams excels at meetings within the Microsoft ecosystem:

Jitsi and Self-Hosted Options

For privacy-conscious teams, Jitsi provides a capable free alternative:

# docker-compose.yml for self-hosted Jitsi
services:
  jitsi:
    image: jitsi/web
    ports:
      - "80:80"
      - "443:443"
    environment:
      - ENABLE_AUTH=1
      - ENABLE_LOBBY=1

Self-hosting gives you control over recording, encryption, and data retention policies.

Post-Meeting Etiquette

Meeting etiquette extends beyond the call itself:

Conclusion

Small scripts that handle setup, reminders, and follow-ups compound over time, saving hours each week while improving meeting quality.

Built by theluckystrike — More at zovo.one