Examples for Technical Roles are: Software Engineer, Embedded Engineer, Electrical Engineer, Cybersecurity Engineer, CTO, VP of Engineering etc
Here are some common issues users often encounter. For more details on configuring projects, please refer to our article here: Project Configuration Deep Dive
1. Undefined Seniority: Skipping experience levels can allow junior candidates to score highly.
Tip: Set minimum years of experience or weight advanced skills to reflect seniority.
2. Hands-on vs. Leadership Focus: Technical vs. leadership roles may score similarly without clear distinctions.
Tip: Separate scoring for technical and leadership competencies to match the role’s focus.
3. Overly Narrow Tech Requirements: Specific tools (e.g., “Azure”) can limit the candidate pool.
Tip: Broaden to “Cloud Environments, preferably Azure” to include relevant experience.
4. Overuse of “Must-Have” Criteria: Excessive “Must-Haves” can exclude good candidates.
Tip: Use “Should-Have” for desirable but non-critical skills.
5. Unweighted Skills: Equal weighting skews scores for low-priority skills.
Tip: Assign High, Medium, or Low weights based on skill importance.
6. Limited Keywords: Narrow keywords may miss relevant candidates.
Tip: Include synonyms (e.g., “JavaScript” and “JS”) to broaden search results.
Examples of Well-Configured and Poorly Configured Projects:
