Your personal information:
Treat this section as your “first impression” snapshot.
Use a clear, well‑lit profile picture where your face is visible and you look like someone a team could jump on a call with tomorrow. A simple phone photo against a neutral background is perfect.
Make sure your current location reflects where you actually live (city and country): this will help match you with relevant opportunities, especially for hybrid or office‑based roles, so putting “remote” instead of your city will usually hurt you.
Add a cell number and, if you use it, a WhatsApp number you really answer. Your talent advisor uses these to help you move quickly through processes; companies only get access to your contact details once they’ve requested an interview, not before.
Location and workplace policy preferences:
Your location and workplace preferences will help us match you with the right roles, so it pays to be precise. When you choose between 100% remote, hybrid or office‑based, think about how you actually want to work day‑to‑day, not what sounds nice on paper.
If you select hybrid or office‑based, only add cities you’d genuinely relocate to or commute from – companies will assume that if a city is listed, you’re ready and able to be there regularly.
For remote roles, you’ll often still be matched on time‑zone and legal work‑rights, so an accurate location remains important.
Before you make your profile visible, it’s worth asking yourself: “If I got a great offer in any of these locations, would I really move or commute?” If the honest answer is no, take that location off.
Work authorisation:
Work authorisation is one of the quickest yes/no checks companies do, so clarity here saves everyone time. Add your citizenship or residency status and spell out where you can already work without sponsorship, versus where you’d need a visa. If you’re on a visa, include the type and, if relevant, when it expires, for example: “Critical Skills Visa, valid to 2027.”
For any country you’re seriously interested in, make sure your work authorisation details are correct. This helps companies decide early whether they can hire you and whether they need to plan for sponsorship or relocation support. It’s far better to be upfront here than to get deep into a process only to find out that hiring you isn’t legally or financially viable.
This is also where you can upload supporting documentation.
Work experience:
This is the section technical managers study most closely, so write it as if you’re explaining your work to another senior developer.
For each role, describe what you actually built and owned, not just what the job spec said: the systems or features you worked on, the scale you dealt with, and the impact of your work. Naming concrete outcomes (“reduced average response times by 60%”, “helped migrate from monolith to microservices”) is far more compelling than generic responsibilities (“responsible for APIs”).
Make sure your technical skills per role reflect what you used regularly, because they actively help with matching you to what hiring manager are looking for and appear as tags and many managers filter or skim by those. Don’t worry if parts of your career weren’t in development. It’s better to have a complete story with a non‑dev role or a study break than unexplained gaps that hiring managers have to interrogate later, you can also add reasons for leaving previous roles to accurately represent your career journey thus far.
Ideal next job:
Hiring managers often read this section right after your headline, and they use it to decide whether to start a conversation with you. Use it to teach them what a great role looks like for you and to be explicit about your target role title(s) and your years of experience in those areas.
Instead of saying you’re “looking for a challenge,” describe what that challenge actually is:
The specific roles you’re aiming for (e.g., “Senior Backend Engineer (6+ years)” or “Product Designer (4 years)”)
The kind of team you want to be part of (size, culture, management style)
The type of work you’d like to focus on next (e.g., greenfield product development, platform work, B2B SaaS, ML infra)
The level of ownership you’re aiming for (individual contributor vs. tech lead, people management, roadmap influence)
Any conditions that help you do your best work (hours, flexibility, remote/hybrid preference, office setup, tech stack norms)
Call out the tools and languages you want to be hands‑on with (and your experience with them), the industries you’re excited about, and anything you’d prefer to avoid (e.g., pure maintenance work, heavy legacy support, constant fire‑fighting or 24/7 on‑call).
The more specific you are about role, seniority, and fit, the more likely it is that the interview messages you receive will feel “spot on” instead of random.
AI Fluency [Beta]
AI Fluency is where you show how comfortable you are using, building or supporting AI in your work. Companies are increasingly filtering for this, so don’t leave it blank if you’re doing anything beyond the occasional copy‑paste.
Be honest about which level you’re operating at: are you just starting out, mainly using AI tools in your day‑to‑day workflow (for coding, reviews, documentation or data exploration), have you shipped features that are actually powered by models or APIs, or are you the person setting up the data pipelines, vector stores and infrastructure those features run on?
In the summary, name the specific tools and workflows you rely on, for example: GitHub Copilot, ChatGPT, Claude, or in‑house models, and link to work experience or projects where this shows up in practice.
A short note about where you’re cautious with AI (for example around PII, IP or bias) also signals to hiring managers that you’re ready to use these tools responsibly in production, not just experimenting on the side.
Education:
Education isn’t usually what gets you shortlisted, but it does help frame your background and can clear certain company requirements. List your formal education (high school and tertiary where relevant) and add any bootcamps, online courses or certifications that matter for the roles you want. A cloud certification, data course, or solid bootcamp can be just as interesting as a degree, especially for practical dev roles. The key is to show a consistent pattern of levelling up: if you’ve taken meaningful courses or masterclasses, include them so companies can see that you invest in your own growth rather than stopping at whatever you did at school or university.
