Project Challenge: Technical Job Interview Simulation (SMX)

Course: Systems and Networks Administration (SMX)
Estimated Video/Audio Duration: 3 minutes (~1 minute per interview)
Objective: To demonstrate communication fluency, accurate technical ICT vocabulary (hardware, software, network, troubleshooting), and spontaneous problem-solving skills following the PRO+ rubric guidelines.


1. Interview Scripts

🎙️ INTERVIEW 1: Helpdesk & User Support

Focus: Software, Operating Systems, and Helpdesk troubleshooting.

Interviewer (Student A): Good morning! Welcome to our IT department. To start, why do you want to work as a Helpdesk Technician with us?

Candidate 1 (Student B): Good morning. I want to start my career here because I love solving technical problems and helping users. During my SMX diploma, I discovered that I enjoy managing operating systems and finding out why a computer is failing.

Interviewer (Student A): Great. Imagine a user calls because their computer is extremely slow and won’t connect to the internet. What is your troubleshooting process?

Candidate 1 (Student B): First, I would check the basics. I’d open the command prompt and run ipconfig and ping to see if it’s a network issue. To fix the speed, I would check the Task Manager to see the RAM and CPU usage. It could be a virus or too many startup programs.

Interviewer (Student A): Good. Have you ever solved a similar software issue in your class projects?

Candidate 1 (Student B): Yes! In our last challenge, we deployed an operating system image using Clonezilla. Some computers had driver conflicts and ran very slow, but I fixed it by updating the drivers in safe mode.


🎙️ INTERVIEW 2: Network & Security Junior Technician

Focus: Local Area Networks (LAN), active equipment, and infrastructure.

Interviewer (Student B): Hello, thanks for coming. What motivated you to specialize in networks during your SMX studies?

Candidate 2 (Student C): Hi. I find networking fascinating because it connects everything. I really like assembling rack cabinets, creating network cables, and configuring security settings to keep data safe.

Interviewer (Student B): Perfect. If an entire office local network (LAN) goes down and nobody can access the server, what components do you check first?

Candidate 2 (Student C): I would check the main router and the central switch to see if the activity LEDs are blinking. If they are off, it might be a hardware failure or a power supply issue. If they are on, I would check the DHCP server configuration.

Interviewer (Student B): Interesting. Did you configure a real network like this in your course?

Candidate 2 (Student C): Yes, exactly. For our networking module, my team designed a local network with a star topology. We configured a Cisco router with specific IP addresses and added WPA3 security to the wireless access point.


🎙️ INTERVIEW 3: Hardware & System Maintenance

Focus: Hardware components, diagnostics, and data backup.

Interviewer (Student C): Good morning. Please, tell me about your experience assembling and maintaining computer hardware.

Candidate 3 (Student A): Good morning. I have a lot of hands-on experience. In the SMX workshop, we assembled many computers from scratch, installing the motherboard, CPU, RAM, and storage drives.

Interviewer (Student C): Excellent. A client brings a PC that turns on—the fans are spinning—but the screen is black and it emits repeating beeps. What is the problem?

Candidate 3 (Student A): The beeps are a BIOS/UEFI error code. Continuous beeps usually mean a RAM problem or a graphics card issue. I would open the case, clean the dust, and reseat the RAM modules in their slots.

Interviewer (Student C): We also use Linux servers. Do you have experience with that?

Candidate 3 (Student A): Yes, we worked with Ubuntu Server. I know how to use the Linux terminal to manage users and permissions, and I also configured automated backups using shell scripts to prevent data loss.


2. Core Technical Vocabulary (SMX Glossary)

To meet the highest rubric evaluation criteria, the following key terms have been actively integrated into the dialogue:

  • Hardware: Motherboard, CPU, RAM modules, Storage drives, Fans, Power supply, Switch, Router, Rack cabinets.
  • Software & OS: Windows, Ubuntu Server, Linux terminal, Driver conflicts, Clonezilla, Command prompt, BIOS/UEFI.
  • Networks: LAN, Star topology, IP addresses, DHCP server, Ping, Ipconfig, WPA3 security.
  • Troubleshooting: Error codes, Safe mode, Task Manager, Backup, Data loss, Virus.

3. Project Evidence & Deliverables

[Team Instructions: Insert a WordPress “Image Gallery” or “Video” block here displaying your preparation phase, photos of the team during recording, and the final link to your YouTube or Google Drive video file to complete the Evidències rubric requirement.]