Closed Beta: Language configuration is currently in closed beta. Contact us to request access.
Control the language used in scoring assessments. This affects the verdict, strengths, concerns, and interviewFocus fields in score results.
Configuration Levels
Language can be set at two levels:
| Level | Field | When Applied |
|---|
| Job | jobContext.language | During criteria generation |
| Request | language | During scoring |
Precedence
When both are set, request-level wins:
- If
language is set in the score request, use that
- Otherwise, use the
jobContext.language from criteria generation
- If neither is set, default to English
Setting Job-Level Language
Set language when generating criteria:
POST /v1/criteria/generate
{
"jobContext": {
"jobId": "job-123",
"jobTitle": "Senior Engineer",
"companyName": "Acme Corp",
"jobDescription": "...",
"language": "German"
}
}
All scores for this job will use German unless overridden per-request.
Overriding Per-Request
Override the job default for a specific score:
POST /v1/score
{
"jobId": "job-123",
"applicationId": "app-456",
"language": "French",
"candidate": {
"resumeUrl": "..."
}
}
This score will use French regardless of the job’s configured language.
Supported Languages
Any language name is accepted. Common values:
English (default)
German
French
Spanish
Dutch
Portuguese
Italian
Example Output
English:
{
"verdict": "Strong candidate with solid backend experience...",
"strengths": ["6 years of backend engineering experience"],
"concerns": ["No direct Kubernetes experience"]
}
German:
{
"verdict": "Starker Kandidat mit solider Backend-Erfahrung...",
"strengths": ["6 Jahre Backend-Engineering-Erfahrung"],
"concerns": ["Keine direkte Kubernetes-Erfahrung"]
}
Best Practices
- Set
jobContext.language during criteria generation for consistent output across all candidates
- Use per-request
language only when you need different output for the same job (e.g., multi-region teams)
- The resume itself can be in any language - Nova processes resumes regardless of their language