A connection works on a computer, but the customer says their phone gets poor reception in another room. What should be written in the report? "Installation completed" is too vague. "Faulty fiber" may be a conclusion without proof. For a candidate for a job in optical fiber in Morocco, this situation makes it possible to demonstrate a precise professional quality: describe what was done and observed, then pass on what remains to be verified.
A report does not replace a connection or measurement skill. It makes it understandable for the colleague who takes over the file, for the manager who monitors the intervention and for the customer who is waiting for an answer. Here is a preparation method based on an entirely fictional case. It is used to work on your presentation in an interview; the technical procedures, acceptance criteria and intervention rules remain those of your training and the company.
Understanding the profession before choosing your example
The OFPPT digital professions directory describes optical fiber installation with activities of laying, connecting and testing. These tasks require practical learning. The name of a tool on a CV is therefore not enough to establish that you can intervene autonomously. In your application, distinguish what you did in training, what you observed and what you took charge of professionally.
A job posting may concern deployment, an intervention at a customer's premises, work monitoring or another part of the network. Reread the duties before preparing your example. If the position mainly involves acceptance files, an explanation focused on the quality of the information transmitted will be more relevant than a general account of telecommunications. If the company expects field practice, this document can complement your achievements, without replacing them.
To understand the customer's situation, you must also separate the elements of their connection. The ANRT guide on high-speed internet distinguishes fiber and Wi-Fi: devices connect wirelessly to an access point, which itself is connected to the internet or to another network. A difficulty experienced on one device therefore does not, by itself, identify the part of the network responsible. This distinction helps to write a precise observation.
A fictional case with two findings that do not say the same thing
Imagine an intervention in a small office in Casablanca. The exercise file indicates that equipment was installed and that a connection was observed on a computer in a specified configuration. A person then reports an irregular connection on their phone from an adjacent room. In this case, you do not have an optical measurement result or a detailed record of the test conditions on the phone. These missing pieces of information are part of the exercise.
Your first task is to keep the two findings separate. The connection observed on the computer does not prove that all devices will work everywhere. The report concerning the phone does not prove that the optical connection is the cause. You can note the existence of the service in the observed configuration and keep the customer's request as a separate point. The report gains value when it makes it possible to find this difference without having to call you back.
To present the case in an interview, prepare a short sheet with a fictional identifier, the context, the actions described and the open questions. Do not add a speed, an optical power or a serial number to make the file more realistic. An invented piece of data remains an invented piece of data, even if it resembles what you saw in training. Here, the demonstration focuses precisely on how you handle missing information.
Writing an action, an observation and a conclusion separately
An action answers "what was done?". An observation answers "what was seen or recorded?". A conclusion answers "what does this make it possible to assert?". Mixing these levels produces sentences that are quick to write but difficult to take up again. "Everything is fine" says neither which elements were examined nor which verification made it possible to close the file. Another person cannot know whether this formula concerns the installation, the service or customer satisfaction.
In the fictional case, you could write that the connection was observed on the computer in the described configuration, then note separately the report concerning the phone. The expected follow-up must be identifiable: additional verification according to the company's procedure, with a contact person responsible for taking it over. This wording does not resolve the difficulty, but it avoids turning an assumption into a diagnosis. It is a usable basis for continuing the work.
Choose verbs that match your evidence. "Installed", "observed", "measured", "reported" and "confirmed" are not interchangeable. If the customer reports an interruption that you did not reproduce, write that it was reported. If a measurement was actually taken, indicate where its record is and under what conditions it was carried out. Do not replace these conditions with a personal assessment such as "excellent result".
In an interview, the recruiter may ask you what would make you change your conclusion. Answer based on the file: an additional verification, a missing record, an inconsistency between the equipment identifier and that of the document. You thus show that your conclusion depends on precise elements. There is no need to improvise a technical procedure to prove your seriousness; you can explain what information would be useful and who would be authorized to produce it.
Making a measurement readable without inventing a threshold
An isolated number is not yet a usable result. It must be possible to identify what was measured, the unit, the point concerned and the document from which the value comes. Depending on the tasks, an optical link measurement and a speed test do not evaluate the same thing. Your report must keep the real name of the verification, rather than grouping all results under a "speed" heading that would erase their meaning.
When you prepare an exercise, you can work on the structure of the record without placing values in it. Mention the fields that will need to be filled in from a real measurement and the reference document that would make it possible to interpret it. This does not demonstrate your ability to carry out that measurement; it shows that you know how to make it traceable. Both skills must be presented honestly, especially if you are starting out and looking for a position with support.
Avoid learning a threshold found on the internet to present it as valid everywhere. The expected criteria must be linked to the network, the equipment, the contract and the procedure applicable to the work concerned. If these elements do not appear in your case, say that compliance cannot be concluded on this basis. You do not need to lengthen the report with a list of possibilities: clearly indicate the missing reference.
The same caution applies to reusing an old record. Check that it actually concerns the intervention and equipment described. A complete document, but attached to the wrong file, can lead to more errors than a reported absence. In an application presentation, this correspondence check is a simple example to explain: you first seek to know whether the information concerns the same object before commenting on the result.
The customer must understand what is finished and what remains open
Technical language can be useful between colleagues and unnecessarily complicated for the person waiting for a connection. Adapt your explanation without changing the facts. In our example, you can say that a connection was observed on the computer and that the difficulty reported on the phone remains to be examined. The person then understands why the file includes a follow-up, even if part of the intervention is finished.
Do not promise either identical wireless coverage in all rooms or a commercial result that is not part of your role. A clear explanation makes it possible to specify what you are taking charge of and what must be passed on. If the customer requests a change, note their request and the expected decision. A recorded request is not an approved change; the report must make it possible to distinguish the two states.
The languages used depend on the situation and the position. You can prepare a short explanation in French and Arabic if the job posting requires this ability, then practice reformulating a technical term in accessible words. Do not present yourself as capable of explaining all subjects in a language on the sole basis of a memorized text. It is more credible to show a situation that you can genuinely describe and to specify your level.
A short sheet that allows a colleague to take over
Your exercise file can fit on one page, with the useful documents attached separately. A header identifies the fictional case and the version of the document. The body indicates the scope of the intervention, the actions and the observations. The last part specifies the elements still open and their expected follow-up. This organization is a Jawb proposal for your preparation; if a company uses a different form, its process must be followed.
Reread the sheet from the point of view of a colleague who was absent during the intervention. Do they understand which equipment you are talking about? Do they know whether the difficulty was observed or reported? Can they find the documents cited? If a sentence requires a long oral explanation, look for what it is missing. It is not about telling everything, but about keeping the information that changes the next decision. Movements with no consequence for the file do not necessarily need to be detailed.
Photos can help document a situation when they are planned and authorized, but they do not replace a precise caption. For your application, use a personal exercise or elements that you are authorized to share. Set aside a customer's contact details, access identifiers and internal documents from a former employer. A clearly identified fictional example can show your reasoning without obliging you to expose a real file.
Also keep corrections understandable. If you change a conclusion after new information, indicate what justifies this change in your exercise. Quietly deleting the previous version can prevent you from explaining your thought process. A dated version and a short note on the change are often enough to make the discussion readable, without turning a simple sheet into a complex administrative procedure.
Presenting this skill in an application
In your CV, link the sheet to a real experience or to a clearly named training assignment. "Preparation of a fictional report distinguishing actions, observations and open points" describes the work presented. "Complete network expertise" would give it a scope it does not have. The Jawb guide for writing a CV in Morocco can help you choose a precise wording and place this document in your background.
In an interview, first present the situation, then a sentence that you improved. Compare an overly broad wording with the one that preserves the limit of the finding. Explain why the second makes it easier to take over the file. This passage can be more instructive than a long presentation on networks: the interviewer sees how you work on a concrete task. You can then answer technical questions within the limits of your skills.
Also prepare your questions about the position. Who validates the files? What support is planned for a beginner? What part of the work concerns the field and what part concerns monitoring? These answers will help you understand the expected autonomy. The advice for preparing a job interview helps organize this exchange without turning your questions into a recited list. The report is a conversation aid, not a promise of employment.
A final check before sharing your example
Reread the identifiers, dates and names of the documents. Look for statements that go beyond the available observations. Then check that each open point has an understandable follow-up. A sheet must not give the impression that a problem is resolved when it has only been passed on. Conversely, it can acknowledge part of the work as finished without declaring the entire intervention a failure. This level of precision helps avoid misunderstandings.
If you share the document via a link, test its access without your personal session and check the version actually visible. For an application on Jawb, the application guide completes this preparation with the steps for presenting your file. Send a readable document, each element of which you can explain, rather than a set of technical files that the interviewer will not be able to link together.
In optical fiber professions, a useful report leaves a faithful trace of the work and its limits. It helps the next person take over at the right point and the customer understand the follow-up. For a candidate, knowing how to show this quality of writing complements technical practice. Your example will be ready when you can clearly distinguish what you did, what you know and what the file does not yet make it possible to conclude.
