# How to prepare for job interviews #1 : Digital Presence

## Digital Presence

### LinkedIn

* Have a professional avatar: if you can afford professional photographer it would be perfect **but** you don't need it, just let someone takes a picture of you with clear lighting and don't be too casual
* Your LinkedIn description should explain what you do, I prefer to keep it short and concise as bullet points
* Underrated feature: use *`featured`* section on LinkedIn to show your projects, certifications, and anything worth sharing in your profile. People will scan your profile (specially HR) so it would be nice to presents to readers a quick overview of your profile

![](/files/Q6cGFAG4cPoYxir0Id7n)

* Add relevant media for each experience you have
* Use *`projects`* section to add your projects (deployed links would be a huge plus)

### Resume / CV

* General resume structure
  * Work Experience
  * Education
  * Certifications
  * Skills
  * Side projects 
  * References (people to call)
* LinkedIn is important but your CV can play a major role on your hiring, how? 
  * Job referrals : Either a software engineer looking to hire inside his organization, or he knows someone in another organization who wants to hire an engineer, at the end of the day he will asks for your resume to send it to someone, your resume will be the first impression of you
  * HR may contact you over LinkedIn and asks for your resume, most likely he will send it to a hiring manager or a technical interviewer (tech lead or senior engineer) to review it
  * Your CV will be discussed in the upcoming interviews specially with the hiring manager, and you will be asked about information mentioned in it, so make sure to keep it updated and accurate
* How to create a good resume ?
  * People will scan your resume, this study shows that on average recruiters will spend almost 7 seconds to read your resume, so I prefer to keep it short and presents all information as bullet points. <https://www.hrdive.com/news/eye-tracking-study-shows-recruiters-look-at-resumes-for-7-seconds/541582/>
  * 1-2 pages at max
  * Correct spelling
  * Mention numbers (metrics) or impact as much as possible. Explain the outcome of what you did:
    * I developed a restful API which now <mark style="background-color:yellow;">serves 1000+ end-users</mark>&#x20;
    * &#x20;Developed CI/CD pipelines which <mark style="background-color:yellow;">improved developer productivity</mark>&#x20;
  * Keep your CV simple , <mark style="color:red;">**no charts or progress bars**</mark>, either yow know the skill or not &#x20;
  * **❌**

<div align="center"><img src="/files/YFXfnPNDjcLnbPU6JQwX" alt="Don&#x27;t do this"></div>

* Always provide a PDF version
* the resume file should be with your name <mark style="color:red;">**not**</mark> resume(1).pdf

{% hint style="info" %}
Abdulrahman\_*Alotaibi\_Software\_Engineer.pdf*
{% endhint %}

* List only relevant certifications, and avoid adding trivial-to-get certifications (LinkedIn certifications or certificate of completion)
* Don't include trivial skills&#x20;

### Resource to build resumes

{% embed url="<https://www.canva.com/>" %}

{% embed url="<https://enhancv.com/?gclid=CjwKCAjwh-CVBhB8EiwAjFEPGQv3MEYkmp5TFq6uIfuyAehW9yIOuyujURa2Hg6KXjb8hnNYDEZJlxoCpXUQAvD_BwE&utm_campaign=search_brand_terms_new_users&utm_medium=cpc&utm_source=google&utm_term=enhancecv>" %}

## Build your own website

I use a headless-CMS to return all of my blog posts (you can also use it to store all of your website copywriting)

{% embed url="<https://prismic.io/>" %}

I use `Nextjs`  to build the UI&#x20;

{% embed url="<https://nextjs.org/>" %}

I use `Namecheap` to buy my domain

{% embed url="<https://www.namecheap.com/>" %}

Also, you can use `Webflow` or Notion resume templates to build your resume&#x20;

{% embed url="<https://www.notion.so/Resume-ee188cbab4ae47ddb3fc79c1a3d3b906>" %}

{% embed url="<https://webflow.com/resume-websites>" %}

### Ref

![](/files/Bz66k1KZu3yCXsgE2xjN)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://abdulrahman-1.gitbook.io/my-digital-garden/level-0-non-technical-considerations/how-to-prepare-for-job-interviews-1-digital-presence.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.