The importance of the Dev Card
The Dev Card is the anonymized cover of your profile to which companies apply. Always remember that your Dev Card is what companies see.
The better the quality and simplicity, the greater the chance that someone will apply to you. When you look at your Dev Card, you have to think “I would hire myself!”.
If not: then there is probably something that needs improvement.
This step-by-step guide will give you tips on how to best fill out each section.
The Principle of Anonymity
Your Card is anonymous. This means that no details of gender, age, place of birth, completion dates, or names of training institutions are displayed.
When filling out sections of your profile, remember not to disclose sensitive information. Don’t write things like “I graduated from university X in year X”.
Tech Skills Section
Select and add all the tech skills you work with, study or have fun with.
I recommend, few but good ones are better than endless lists of technologies, favor in order those you master, those you get along with, those you would like to improve or with which you would like to work.
When you scroll down the years of experience bar, it always rounds down, it is better to look strong in a slightly lower level than poor in a high level.
Add all your tech skills, and indicate how many years of experience you have with these technologies. Experience can mean both working for a company and creating projects while studying. If you type code on the keyboard and are developing something: you are gaining experience!
The title must be the technology (e.g. C, C ++)
The description must tell your level and what you have planned to reach that level (eg. I studied for 1 year, and I created 3 projects to master memory management through pointers, semaphorization of threads, and a text chat between connected consoles. via socket. My trophy project is a replica of a shell internally in C, including management of environment variables, pipes and file management. Here is the link:)
N.B. Linking to a portfolio or a git repo dramatically increases the credibility of anything you write and allows a window into your skills. If expressing yourself in words is not your strong point, expressing yourself in projects can take you far.
In short, whether they are studies, work experience or personal projects: explain why you are good at what you are good at.
Studies and training
Year + Title.
Very simple and very fast.
But we do it simple with a series of ifs:
IF (you quit your studies) -> do not put anything;
IF (you are out of court and you do not intend to finish) -> do not put anything;
Moment of self-analysis, but remember .. few but good ones!
Our advice is to choose the ones for which you have the best examples that you could give in an interview. For example, “Stress Management”, be ready to answer “What is a stressful situation you have faced and how did you manage it?”
If you want to tell more about yourself, it is a space for your free expression. Tell us about your attitudes, your goals or your ambitions….
Find out why (Optional reading):
Anonymizing your card is very important. We want to combat recruiting biases, and we don’t want to train our AI on criteria that aren’t relevant. We believe that a person should be selected for what he can do rather than who he is! We improve diversity and inclusion by not entering sensitive data. You can feel more at ease, knowing that your information is not used, and wait for companies to apply to you: because you have the right characteristics for what the company needs! Otherwise it could be easy to make assumptions, even possibly incorrect, on regional origin or age. In any case, we want to give the same opportunities to all developers, regardless of where they were born or located, and also protect those situations in which you graduated late due to the need to work, or put aside work to help. a sick family member, or you want to jump into the sector at an advanced age, and more.
Highlighting your tech skills in this way can give you great visibility. Companies are interested in what you can do and why. Naming patterns, libraries and projects gives you a big push forward. Showing your portfolio makes it clear what your style and approach to problems are.