Pipeline run
793d7086-e1f6-4935-bca9-82a6742d040e
Pipeline LLM cost (USD)
API 1: $0.0031
API 2: $0.0000
API 3: $0.0000
Total: $0.0031
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA description
role baseline loaded
sources · ai_index: jd · nature_of_work: jd · tech_stack_maturity: jd
Nature of work
· Data platform optimization and governance
Designs and documents database schemas and standards, evaluates DBMS tools, and defines table/field structures, storage, capacity, loading, maintenance, and security plans. Also codes client-server app screens/reports and supports QA and test code.
"Establishes database management systems, standards, guidelines, and quality assurance for database deliverables"
Tech stack maturity
Mainstream Modern
Capacity planning is a standard data engineering capability commonly implemented with established modern data platforms and tooling rather than requiring bleeding-edge or legacy-only stacks.
AI index (0 = no AI use, 5 = totally AI-dependent · v2.1)
0.00 / 5
· Title match
· Has AI skill
· AI skill (primary)
· AI skill (secondary)
· On AI team
· Builds AI products
vocab breakdown (legacy)
Assistants (×1):
—
Frameworks (×2):
—
Models / concepts (×3):
—
Evidence — skills matched in JD (11)
Database Management Systems
Quality Assurance
Database Design
Capacity Planning
Data Loading
Data Maintenance
Security Policy
Technical Platforms
User Interface
Client-Server
Relational Model
Skill cluster (1 dimension groups, role-scoped)
Cross-cutting / unaligned
Database Management Systems
Quality Assurance
Database Design
Capacity Planning
Data Loading
Data Maintenance
Security Policy
Technical Platforms
User Interface
Client-Server
Relational Model
Show KRA description ↓
• Establishes database management systems, standards, guidelines, and quality assurance for database deliverables, such as conceptual design, logical database, capacity planning, external data interface specification, data loading plan, data maintenance plan and security policy. Documents and communicates database design.
• Evaluates and installs database management systems.
• Codes complex programs and derives logical processes on technical platforms. Builds windows, screens, and reports. Assists in the design of user interface and business application prototypes.
• Participates in quality assurance and develops test application code in client server environment.
• Provides expertise in devising, negotiating, and defending the tables and fields provided in the database. Adapts business requirements, developed by modeling/development staff and systems engineers, and develops the data, database specifications, and table and element attributes for an application.
• At more experienced levels, helps to develop an understanding of client's original data and storage mechanisms.
• Determines appropriateness of data for storage and optimum storage organization.
• Determines how tables relate to each other and how fields interact within the tables for a relational model.
Signals
Skill
—
—
Alias
data-engineer
1.00
KRA
data-engineer
0.42
Post-classification
Centroidupdated · n=7
Alias collision log—
New-role queue—
New skills captured11
New KRA captured—
Captured for admin review
Database Management Systems
primary
↔
Data Engineer
pending
Quality Assurance
primary
↔
Data Engineer
pending
Database Design
primary
↔
Data Engineer
pending
Capacity Planning
primary
↔
Data Engineer
pending
Data Loading
primary
↔
Data Engineer
pending
Data Maintenance
primary
↔
Data Engineer
pending
Security Policy
primary
↔
Data Engineer
pending
Technical Platforms
primary
↔
Data Engineer
pending
User Interface
primary
↔
Data Engineer
pending
Client-Server
primary
↔
Data Engineer
pending
Relational Model
primary
↔
Data Engineer
pending
Status:
extract_from_jd_done
Created: 2026-05-19T00:04:55.846047Z
Updated: 2026-05-19T00:04:56.847987Z
Flow
Current 3-step pipeline
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Role
Chosen role & resolution
No chosen role stored for this run.
Job description
Data Engineer Job Description: • Establishes database management systems, standards, guidelines, and quality assurance for database deliverables, such as conceptual design, logical database, capacity planning, external data interface specification, data loading plan, data maintenance plan and security policy. Documents and communicates database design. • Evaluates and installs database management systems. • Codes complex programs and derives logical processes on technical platforms. Builds windows, screens, and reports. Assists in the design of user interface and business application prototypes. • Participates in quality assurance and develops test application code in client server environment. • Provides expertise in devising, negotiating, and defending the tables and fields provided in the database. Adapts business requirements, developed by modeling/development staff and systems engineers, and develops the data, database specifications, and table and element attributes for an application. • At more experienced levels, helps to develop an understanding of client's original data and storage mechanisms. • Determines appropriateness of data for storage and optimum storage organization. • Determines how tables relate to each other and how fields interact within the tables for a relational model.
Skills from this JD
Each row merges API 1 extraction, API 2 library match / v3 orchestration (dimensions + locked dims), and API 3 persistence tags.
Database Management Systems
Primary
No API 2 row (run stopped after API 1 or history missing)
Quality Assurance
Primary
No API 2 row (run stopped after API 1 or history missing)
Database Design
Primary
No API 2 row (run stopped after API 1 or history missing)
Capacity Planning
Primary
No API 2 row (run stopped after API 1 or history missing)
Data Loading
Primary
No API 2 row (run stopped after API 1 or history missing)
Data Maintenance
Primary
No API 2 row (run stopped after API 1 or history missing)
Security Policy
Primary
No API 2 row (run stopped after API 1 or history missing)
Technical Platforms
Primary
No API 2 row (run stopped after API 1 or history missing)
User Interface
Primary
No API 2 row (run stopped after API 1 or history missing)
Client-Server
Primary
No API 2 row (run stopped after API 1 or history missing)
Relational Model
Primary
No API 2 row (run stopped after API 1 or history missing)
Library artifacts (this run)
No artifact rows for this run.
nano JD Parser — gpt-4.1-nano click to toggle
RoleData Engineer
DomainOther
JD type
pass
Show raw JSON
{
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": null,
"ctc": null,
"domain": {
"primary": {
"aliases": [],
"domain": "Other"
},
"secondary": null
},
"education": [],
"experience": {
"max": null,
"min": null,
"raw": null
},
"job_locations": [],
"role": "Data Engineer",
"role_archetype": "Data",
"roles_and_responsibilities": [
{
"bullet_count": 8,
"heading": "Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Establishes database management systems,",
"last_5_words": "fields interact within the tables for"
},
"text": "\u2022 Establishes database management systems, standards, guidelines, and quality assurance for database deliverables, such as conceptual design, logical database, capacity planning, external data interface specification, data loading plan, data maintenance plan and security policy. Documents and communicates database design.\n\u2022 Evaluates and installs database management systems.\n\u2022 Codes complex programs and derives logical processes on technical platforms. Builds windows, screens, and reports. Assists in the design of user interface and business application prototypes.\n\u2022 Participates in quality assurance and develops test application code in client server environment.\n\u2022 Provides expertise in devising, negotiating, and defending the tables and fields provided in the database. Adapts business requirements, developed by modeling/development staff and systems engineers, and develops the data, database specifications, and table and element attributes for an application.\n\u2022 At more experienced levels, helps to develop an understanding of client\u0027s original data and storage mechanisms.\n\u2022 Determines appropriateness of data for storage and optimum storage organization.\n\u2022 Determines how tables relate to each other and how fields interact within the tables for a relational model.",
"word_count": 202
}
],
"urls": []
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "Database Management Systems"
},
{
"is_primary": true,
"skill_name": "Quality Assurance"
},
{
"is_primary": true,
"skill_name": "Database Design"
},
{
"is_primary": true,
"skill_name": "Capacity Planning"
},
{
"is_primary": true,
"skill_name": "Data Loading"
},
{
"is_primary": true,
"skill_name": "Data Maintenance"
},
{
"is_primary": true,
"skill_name": "Security Policy"
},
{
"is_primary": true,
"skill_name": "Technical Platforms"
},
{
"is_primary": true,
"skill_name": "User Interface"
},
{
"is_primary": true,
"skill_name": "Client-Server"
},
{
"is_primary": true,
"skill_name": "Relational Model"
}
],
"jd_role": {
"display_name": "Data Engineer",
"rationale": null,
"role_archetype": "Data",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": null,
"ctc": null,
"domain": {
"primary": {
"aliases": [],
"domain": "Other"
},
"secondary": null
},
"education": [],
"experience": {
"max": null,
"min": null,
"raw": null
},
"job_locations": [],
"role": "Data Engineer",
"role_archetype": "Data",
"roles_and_responsibilities": [
{
"bullet_count": 8,
"heading": "Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "\u2022 Establishes database management systems,",
"last_5_words": "fields interact within the tables for"
},
"text": "\u2022 Establishes database management systems, standards, guidelines, and quality assurance for database deliverables, such as conceptual design, logical database, capacity planning, external data interface specification, data loading plan, data maintenance plan and security policy. Documents and communicates database design.\n\u2022 Evaluates and installs database management systems.\n\u2022 Codes complex programs and derives logical processes on technical platforms. Builds windows, screens, and reports. Assists in the design of user interface and business application prototypes.\n\u2022 Participates in quality assurance and develops test application code in client server environment.\n\u2022 Provides expertise in devising, negotiating, and defending the tables and fields provided in the database. Adapts business requirements, developed by modeling/development staff and systems engineers, and develops the data, database specifications, and table and element attributes for an application.\n\u2022 At more experienced levels, helps to develop an understanding of client\u0027s original data and storage mechanisms.\n\u2022 Determines appropriateness of data for storage and optimum storage organization.\n\u2022 Determines how tables relate to each other and how fields interact within the tables for a relational model.",
"word_count": 202
}
],
"urls": []
},
"rejected": false,
"rejection_reason": null,
"run_id": "793d7086-e1f6-4935-bca9-82a6742d040e",
"stage3_signals": {
"alias_match_roles": [
{
"display_name": "Data Engineer",
"matched_count": null,
"role_id": 2,
"score": 1.0,
"slug": "data-engineer",
"total_count": null
}
],
"kra_match_roles": [
{
"display_name": "Data Engineer",
"matched_count": null,
"role_id": 2,
"score": 0.424,
"slug": "data-engineer",
"total_count": null
},
{
"display_name": "Cybersecurity Engineer",
"matched_count": null,
"role_id": 5,
"score": 0.4078,
"slug": "cybersecurity-engineer",
"total_count": null
},
{
"display_name": "Android Engineer",
"matched_count": null,
"role_id": 4,
"score": 0.3977,
"slug": "android-engineer",
"total_count": null
},
{
"display_name": "Frontend Engineer",
"matched_count": null,
"role_id": 7,
"score": 0.3911,
"slug": "frontend-engineer",
"total_count": null
},
{
"display_name": "Backend Engineer",
"matched_count": null,
"role_id": 1,
"score": 0.3851,
"slug": "backend-engineer",
"total_count": null
}
],
"skill_match_roles": [],
"stage35_ran": false
},
"stage4_decision": {
"alias_collision_detected": false,
"case": "A",
"chosen_role": {
"display_name": "Data Engineer",
"matched_count": null,
"role_id": 2,
"score": 1.0,
"slug": "data-engineer",
"total_count": null
},
"confidence": 0.424,
"llm2_fired": false,
"llm2_reasoning": null,
"queued": false,
"reasoning": "Stage 1 title \u0027Data Engineer\u0027 (name match); KRA agrees (0.42)"
},
"stage5_updates": {
"centroid_n_after": 7,
"centroid_updated": true,
"collision_log_id": null,
"new_kra_attached": null,
"new_skills_attached": [
{
"is_primary": true,
"queue_id": 278,
"role_display_name": "Data Engineer",
"role_slug": "data-engineer",
"skill_name": "Database Management Systems",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 279,
"role_display_name": "Data Engineer",
"role_slug": "data-engineer",
"skill_name": "Quality Assurance",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 280,
"role_display_name": "Data Engineer",
"role_slug": "data-engineer",
"skill_name": "Database Design",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 281,
"role_display_name": "Data Engineer",
"role_slug": "data-engineer",
"skill_name": "Capacity Planning",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 282,
"role_display_name": "Data Engineer",
"role_slug": "data-engineer",
"skill_name": "Data Loading",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 283,
"role_display_name": "Data Engineer",
"role_slug": "data-engineer",
"skill_name": "Data Maintenance",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 284,
"role_display_name": "Data Engineer",
"role_slug": "data-engineer",
"skill_name": "Security Policy",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 285,
"role_display_name": "Data Engineer",
"role_slug": "data-engineer",
"skill_name": "Technical Platforms",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 286,
"role_display_name": "Data Engineer",
"role_slug": "data-engineer",
"skill_name": "User Interface",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 287,
"role_display_name": "Data Engineer",
"role_slug": "data-engineer",
"skill_name": "Client-Server",
"status": "pending"
},
{
"is_primary": true,
"queue_id": 288,
"role_display_name": "Data Engineer",
"role_slug": "data-engineer",
"skill_name": "Relational Model",
"status": "pending"
}
],
"queue_entry_id": null,
"v3_pipeline_triggered": false,
"v3_role_slug": null,
"v3_run_id": null
}
}
API 2 — extract-details
{}
API 3 — final-role-output
{}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.
Loading…