feat: match agentic, llm, fde and palantir foundry roles
This commit is contained in:
+9
-1
@@ -35,7 +35,15 @@ const SIGNALS: [RegExp, number, string][] = [
|
||||
[/\bcloud\b|\baws\b|solutions?\s+architect/i, 3, "cloud/AWS"],
|
||||
[/\bsecurity\b/i, 2, "security"],
|
||||
[/\bbackend\b|\bfull.?stack\b|\bapi\b|\bintegration\b/i, 2, "backend/API"],
|
||||
[/forward\s+deployed|\bfield\s+engineer|solutions?\s+engineer|customer\s+engineer/i, 4, "forward-deployed"],
|
||||
// Agentic/LLM-agent work is the AI/LLM-integration edge from cv/polo.md —
|
||||
// weighted on its own so "Agentic AI Engineer" clears minScore without a
|
||||
// seniority word.
|
||||
[/\bagentic\b/i, 4, "agentic"],
|
||||
[/forward\s+deployed|\bfde\b|\bfield\s+engineer|solutions?\s+engineer|customer\s+engineer/i, 4, "forward-deployed"],
|
||||
// Palantir Foundry is the platform FDE roles at pharma (Novartis Data42) are
|
||||
// built on. "Foundry" alone is ambiguous (metal casting), so it only counts
|
||||
// next to Palantir or an engineer/developer title.
|
||||
[/\bpalantir\b|\bfoundry\s+(?:engineer|developer|architect)/i, 4, "Palantir Foundry"],
|
||||
[/\bsoftware\s+engineer\b|\bdeveloper\b/i, 2, "software"],
|
||||
// Tech Lead is an explicit target role (see CLAUDE.md), but a bare title like
|
||||
// "Technical Lead" or "Tech Lead" alone only ever hit the generic seniority
|
||||
|
||||
Reference in New Issue
Block a user