Objectives are optional. The platform works without them, using only your achievement history. When objectives are declared, personalization tends to become more precise.
How it works
You declare an objective
Choose a category and describe, in free text or with tags, what you want to achieve. It can be something broad like “become a better programmer” or something specific like “complete the Rio Marathon”.The flow accepts anything from a simple definition with just the category to a more detailed configuration with tags, level, and a specific destination.
The platform interprets your intent
When you write in free text, the platform identifies semantic signals from your objective and connects them to the vocabulary used to organize events and recommendations.This reduces the friction between the way you write and the way the system organizes related opportunities.
What you can define
The objectives form is designed to work with minimal friction. Only the category is required. The other fields help refine the direction when needed.Main fields
| Field | Description | Required |
|---|---|---|
| Category | Sports, Education, Corporate, or Sociocultural | Yes |
| Objective | Free text describing what you want to achieve | No |
| Tags of interest | Terms that help refine recommendation relevance | No |
Advanced fields
| Field | Description |
|---|---|
| Priority | Low, Medium, or High |
| Level | Beginner, Intermediate, Advanced, or Expert |
| Strengths | Skills you already have |
| Preferred format | Online, in-person, city, or state |
| Specific destination | A concrete goal, such as an event, exam, or certification |
Tags of interest
Tags help bridge the gap between your declared intent and the universe of events available on the platform. When an objective includes terms related to a topic, skill, or expected outcome, the platform can improve the match between that objective and the suggested opportunities.How tags can emerge
There are three main paths:- Manual selection — you select tags directly in the form
- Text interpretation — the platform identifies signals from the objective written in natural language
- History reading — automatic suggestions may use patterns observed in your past achievements
Matching events
When creating or editing an objective, the platform may display a preview of events matching the direction you’ve provided. This helps quickly validate whether the objective is well-defined and whether the system understood your intent correctly. This preview also makes it easier to adjust the objective before saving.Auto-generated objectives
The platform can also suggest objectives automatically based on your achievement history. When it identifies consistent patterns of interest, category, or progression, the system may propose a suggested objective for you to review. These objectives appear with a visual highlight and can be:| Action | What happens |
|---|---|
| Confirm | The objective is incorporated into your profile |
| Edit | The form opens for adjustments before saving |
| Discard | The suggestion is removed |
Auto-generated objectives do not influence recommendations until confirmed or edited by the user.
Auto-evolution
Objectives can evolve along with your journey. As new achievements are recorded, the platform may update its understanding of the level, direction, or relevance of that objective, respecting the accumulated history and any manual adjustments made by the user.When an objective is manually edited, that definition takes priority over the platform’s automatic inferences.
Specific destinations
Beyond broad objectives like “I want to get better at programming”, you can also set concrete goals. Examples:- Rio Marathon 42 km
- TOEFL iBT
- AWS Solutions Architect Certification
How objectives impact recommendations
Objectives are one of the most relevant signals in the recommendation engine. In practice, they help the platform better answer questions like:- which category makes the most sense right now
- which events have the greatest relevance to the declared intent
- which opportunities best match the current level
- which paths should be prioritized over others