SIWES Report for Computer Engineering Students: Structure, Tasks and Sample

Computer Engineering students train in very different places: IT firms, ISPs, banks, telecoms, electronics shops and software companies. Because the work is so mixed, many students end up with a report that reads like a list of random jobs.

Here's how to organise yours so your supervisor can see what you actually learned. Follow your department's format first and rename sections if your school asks for different headings.

What makes a Computer Engineering report different

• Mix hardware and software clearly. Make it obvious which part was hardware (repair, wiring, assembly), which was networking, and which was software or embedded work.
• Name specific tools and versions. "Cisco switch" is better than "network device". "Python 3 with Flask" is better than "a programming language".
• Describe the problem and the fix. Supervisors like a short story: what was wrong, how you diagnosed it, what you did.
• Do not confuse it with a Computer Science report. If you want a software-focused example, see Computer Science SIWES report samples. Yours should lean toward hardware, networks and embedded systems.

Where Computer Engineering students usually train

• IT service and repair centres
• Internet service providers and telecom companies
• Banks and ICT units of large organisations
• Software and web development firms
• Electronics and CCTV installers
• Data centres
• School or government ICT units

Tasks you can write about

Hardware

• Assembling and upgrading desktops and laptops
• Diagnosing faults (power supply, RAM, hard drive, motherboard)
• Installing operating systems and drivers
• Replacing screens, keyboards and batteries
• Printer and peripheral repair

Networking

• Laying and terminating network cables (crimping RJ45)
• Configuring routers, switches and access points
• IP addressing, subnetting and troubleshooting connectivity
• Setting up Wi-Fi and managing users
• CCTV and IP camera installation

Software and embedded

• Writing scripts or small programs
• Microcontroller work (Arduino, Raspberry Pi)
• Web or database tasks
• Backup, recovery and basic cybersecurity tasks

Support and administration

• Helpdesk tickets and user support
• Inventory and documentation
• Preventive maintenance schedules

Chapter by chapter

Chapter One: Introduction

Background, aims and objectives of SIWES, and scope. Keep it short. See how to write SIWES Chapter One.

Chapter Two: Profile of the organisation

History, services, structure, departments and an organogram. Mark your unit. See the organogram guide.

Chapter Three: Work done

Group by area. For example:

1. Orientation and safety
2. Hardware repair and maintenance
3. Networking and cabling
4. Software installation and support
5. Programming or embedded projects

Example (fictional, for style only):

In my fourth week, I assisted the network technician in setting up a new office of twelve workstations. I measured and cut the cables, crimped RJ45 connectors following the T568B wiring order, and tested each cable with a cable tester. I then connected the workstations to a switch and checked that each could obtain an IP address from the router. Two machines failed to connect, and I found that one cable had a wrong pin order and the other port was disabled on the switch. After correcting both, all machines connected. I learned that careful wiring and testing prevent many network problems.

Chapter Four: Equipment and tools used

Explain each item in three or four sentences. Examples:

• Cable tester and crimping tool
• Digital multimeter
• Screwdriver set, thermal paste and anti-static wrist strap
• Routers, switches and access points
• Operating system installers and diagnostic software
• Programming tools (VS Code, Arduino IDE, Python)
• Soldering iron and breadboard (for embedded work)

Chapter Five: Summary, problems and recommendations

Summarise the training, name real problems (limited access to servers, power failures, tight deadlines) and how you handled them, then give a conclusion and recommendations.

For the general layout, see the SIWES technical report format guide.

Common mistakes

• Listing tools without explaining them.
• Writing only about the company. Chapter Two is about the company, Chapter Three is about you.
• Using vague words like "worked on computers". Say what you did to them.
• No tests or results. Say how you checked that something worked.
• Copying a classmate's report. Supervisors compare reports from the same company.

A draft to start from

Got the tasks but not the chapters? The MonoEd SIWES Report Generator turns a short account of your training into a first draft in your school's format. The early chapters are free to read before you pay for the rest.

For the weekly entries, the SIWES Logbook can help.

If your logbook is behind, read how to fill the SIWES logbook for Computer Engineering.

Frequently Asked Questions (FAQs)

What should a Computer Engineering SIWES report contain?

A cover page, certification, acknowledgement, abstract or overview, table of contents, and chapters on introduction, company profile, work done, equipment used, and summary with recommendations. Check whether your school uses four or five chapters.

Is it different from a Computer Science report?

In focus, yes. Computer Engineering reports lean toward hardware, networking and embedded systems, while Computer Science reports lean toward software development and data.

Can I write about both hardware and programming?

Yes. Use separate headings so each part is clear.

What if I only did helpdesk work?

Write what you really did: user support, troubleshooting, installations, documentation. See what to write when there was little work.

Should I include screenshots?

Yes, if they help explain your work and don't expose confidential data. Label each one.

Where can I see a sample?

Compare Computer Science report samples and the web development report, then write your own.