---
title: "Create and Manage Job Positions in SkillPanel"
canonical: "https://help.skillpanel.com/space/TBG/2893742090/Create%20and%20Manage%20Job%20Positions%20in%20SkillPanel"
format: markdown
---
**Why:** job positions define what good looks like for every role: skills, mastery levels, and growth paths. Setting them up keeps your organization’s skills data consistent and actionable.

---

## When to use this

- building or updating your company’s skills framework
- defining roles before assigning employees
- linking skillsets to career paths or promotion rules
- creating consistent skill coverage across teams

---

## Prerequisites

- access to **Talent framework → Job positions**
- predefined **skillsets** (see *Skillsets setup guide*)
- permissions to create or edit positions

---

## Quick start

1. Go to **Talent framework → Job positions**.
2. Click **Create** → enter position name.
3. Set a **default mastery level** → click **Create**.
4. (Optional) Mark as **Abstract** for feeder-only roles.
5. Add **skillsets** or **position feeders** as needed.

---

## Detailed steps

### 1. Create a job position

- Click **Create** at the top right.
- Enter a name, description, and default mastery level.
- Select **Abstract** only if the position will serve as a feeder (not assigned to employees).
- Click **Create** to confirm.  
**Why this matters:** defining clear role templates keeps skills consistent across departments.

![a02377bc-a666-48bc-8e13-a7eae32c88ab.png](media://1a6b1dca-caf0-4a9b-977a-7547a5b0a8c0)

### 2. Add skillsets

- Click a position name → right panel opens.
- In **Skillsets**, click **+** → pick from list → **Submit**.
- Repeat for each required skillset.  
**Tip:** combine technical and soft skillsets for a balanced profile.

![9f33a7ea-6f99-4c72-a5ff-d4d6a136927a.png](media://3ac7cd6e-5228-411c-acdd-c30a582678ed)

### 3. Create progressive roles using feeders

- Build from the bottom up: e.g., *Junior → Regular → Senior*.
- For the higher-level role, open **Position feeders** → **+** → choose lower-level position → **Submit**.
- The new role inherits all skillsets from the feeder, labeled **INHERITED**.  
**Why this matters:** avoids duplicate work and ensures promotion paths stay aligned.

![5649ab15-390f-428f-8905-e439a9e2c6c9.png](media://38a32156-b74e-4e16-a83c-b3061c8e5acf)

### 4. Use abstract positions

- Abstract positions represent shared competencies (e.g., *Manager Competencies*).
- They can’t be assigned to employees, only used as feeders.
- Add skillsets to define universal manager skills, then link this abstract role to all management positions.  
**Result:** consistent leadership standards without manual duplication.

![image-20251008-093836.png](media://156029ff-cc67-4882-92c0-ff9c6e624743)

### 5. Edit existing job positions

- Click a position name → **Edit** icon (top right).
- Adjust name, mastery level, or tags → **Save**.
- To add/remove feeders or skillsets, use the **+** or bin icons.  
**Note:** only **DIRECT** skillsets can be deleted; inherited ones require removing their feeder.

![image-20251008-094020.png](media://6e8acf56-617d-418f-ae8d-3729db41e0d5)

### 6. Tag job positions

Tags group and filter roles for easier navigation and permissions.

- Go to **Careers → Job Positions**.
- Edit or create a job position.
- In **Property**, enter one or more tags → **Save**.
- Tags are unique within each tag family and managed by authorized users.  
**Why this matters:** tagging supports granular role-based access and cleaner analytics filters.  
**Important:** tagging is optional and requires enablement via `support@skillpanel.com`.

![image-20250930-144402.png](media://b3f2b99f-9ac2-40f8-938e-004af9937b87)

![image-20250930-144424.png](media://5ce2251d-0526-4b3b-8ac4-782ab95e8107)

## Use SkillPanel to go faster / clearer

| Step | Feature | Benefit | How? |
| --- | --- | --- | --- |
| Feeders | Inheritance logic | Build clear career ladders in minutes | avoids duplicate data entry |
| Abstract roles | Shared role logic | Reuse skill bundles (e.g., leadership core) | fewer inconsistencies |

---

## Examples

**Example 1**  
Input: *Junior → Regular → Senior Backend Developer*  
Action: Link feeders progressively.  
Output: Each higher role auto-inherits skillsets; promotions reflect true mastery growth.

**Example 2**  
Input: *Manager Competencies* (abstract) → linked to *Project Manager* and *Product Manager*.  
Output: Both roles include shared leadership skillsets automatically.

---

## FAQ

**Q:** Why can’t I delete an inherited skillset?  
**A:** Remove the feeder that provides it. If you would like to change the mastery level of the skillset, add the skillset again to overwrite.

**Q:** Can I assign employees to abstract positions?  
**A:** No, they’re structural only.

**Q:** What’s a “default mastery level”?  
**A:** The baseline proficiency required for all skillsets in that role. When adding a skillset without assigning mastery level, it uses the default.

**Q:** Who can create tags?  
**A:** Only users with tag management rights.

**Q:** Can I change a feeder after assignment?  
**A:** Yes, but review inherited skills afterward—changes cascade.

---

## Pitfalls & tradeoffs

- **Don’t** reuse abstract roles as active positions, as employees can’t be linked.
- Inherited skillsets can’t be removed individually, only overwritten to change mastery levels.
- Too many feeders complicate maintenance; keep the hierarchy shallow.
- Over-tagging reduces filter clarity.