## Conversation ### Turn 1 **User** > Here's the JD for an engineer we need to fill. Can you recommend an assessment battery? > > "Senior Full-Stack Engineer — 5+ years across Core Java, Spring, REST API design, Angular, SQL/relational databases, AWS deployment, and Docker. Will own end-to-end microservice delivery, contribute to architectural decisions, and mentor mid-level engineers. Strong CI/CD and cloud-native experience required." **Agent** That JD spans seven distinct areas — Core Java, Spring, REST APIs, Angular, SQL, AWS, and Docker. The catalog has dedicated knowledge tests for each. A focused recommendation needs to know what the candidate will actually own. To narrow this down: Is this a backend-leaning role (Java / Spring / SQL heavy) or a frontend-heavy role or a true balanced full-stack role with significant Angular work? _No recommendations this turn (`recommendations: null`)._ _`end_of_conversation`: **false**_ ### Turn 2 **User** > Backend-leaning. Day-one priorities are Core Java and Spring; SQL is constant. Angular is occasional — they'd review frontend PRs but not own features. **Agent** Understood — Java, Spring, and SQL as primary; Angular as secondary review-only. One more question before I shape the battery: is the seniority closer to a senior IC (deep backend ownership, leads design on their service) or a tech lead (sets architecture across services, reviews other engineers' work)? That changes whether we lean on a knowledge-heavy battery or add a leadership/scenarios layer. _No recommendations this turn (`recommendations: null`)._ _`end_of_conversation`: **false**_ ### Turn 3 **User** > Senior IC. They lead design on their own services but don't manage other engineers directly. **Agent** For a senior IC backend engineer with Java / Spring / SQL primary and Angular secondary, here's a first shortlist focused on what they'll actually own: | # | Name | Test Type | Keys | Duration | Languages | URL | |---|------|-----------|------|----------|-----------|-----| | 1 | Core Java (Advanced Level) (New) | K | Knowledge & Skills | 13 minutes | English (USA) | | | 2 | Spring (New) | K | Knowledge & Skills | 9 minutes | English (USA) | | | 3 | RESTful Web Services (New) | K | Knowledge & Skills | 12 minutes | English (USA) | | | 4 | SQL (New) | K | Knowledge & Skills | 9 minutes | English (USA) | | | 5 | SHL Verify Interactive G+ | A | Ability & Aptitude | 36 minutes | English (USA), Chinese Traditional, Korean, Serbian _(+29 more)_ | | | 6 | Occupational Personality Questionnaire OPQ32r | P | Personality & Behavior | 25 minutes | English International, French (Canada), Portuguese, Chinese Simplified _(+35 more)_ | | _`end_of_conversation`: **false**_ ### Turn 4 **User** > Add AWS and Docker. Drop REST — the API design signal will already come through in Spring and the live interview. **Agent** Updated — REST out, AWS and Docker in: | # | Name | Test Type | Keys | Duration | Languages | URL | |---|------|-----------|------|----------|-----------|-----| | 1 | Core Java (Advanced Level) (New) | K | Knowledge & Skills | 13 minutes | English (USA) | | | 2 | Spring (New) | K | Knowledge & Skills | 9 minutes | English (USA) | | | 3 | SQL (New) | K | Knowledge & Skills | 9 minutes | English (USA) | | | 4 | Amazon Web Services (AWS) Development (New) | K | Knowledge & Skills | 6 minutes | English (USA) | | | 5 | Docker (New) | K | Knowledge & Skills | 10 minutes | English (USA) | | | 6 | SHL Verify Interactive G+ | A | Ability & Aptitude | 36 minutes | English (USA), Chinese Traditional, Korean, Serbian _(+29 more)_ | | | 7 | Occupational Personality Questionnaire OPQ32r | P | Personality & Behavior | 25 minutes | English International, French (Canada), Portuguese, Chinese Simplified _(+35 more)_ | | _`end_of_conversation`: **false**_ ### Turn 5 **User** > On Java — they'd be working on existing services, not greenfield. Is the Advanced level the right pick? **Agent** Yes. Advanced covers concurrency, JVM internals, performance tuning, and the kind of design-level Java that comes up when extending production microservices — which matches "owns end-to-end microservice delivery". The Entry-Level test is calibrated for graduate hires reading and modifying existing code, which undershoots a senior IC. Keeping Advanced. | # | Name | Test Type | Keys | Duration | Languages | URL | |---|------|-----------|------|----------|-----------|-----| | 1 | Core Java (Advanced Level) (New) | K | Knowledge & Skills | 13 minutes | English (USA) | | | 2 | Spring (New) | K | Knowledge & Skills | 9 minutes | English (USA) | | | 3 | SQL (New) | K | Knowledge & Skills | 9 minutes | English (USA) | | | 4 | Amazon Web Services (AWS) Development (New) | K | Knowledge & Skills | 6 minutes | English (USA) | | | 5 | Docker (New) | K | Knowledge & Skills | 10 minutes | English (USA) | | | 6 | SHL Verify Interactive G+ | A | Ability & Aptitude | 36 minutes | English (USA), Chinese Traditional, Korean, Serbian _(+29 more)_ | | | 7 | Occupational Personality Questionnaire OPQ32r | P | Personality & Behavior | 25 minutes | English International, French (Canada), Portuguese, Chinese Simplified _(+35 more)_ | | _`end_of_conversation`: **false**_ ### Turn 6 **User** > Do we really need Verify G+ on top of all the technical tests? Feels redundant. **Agent** Not redundant — they measure different things. The technical tests confirm the candidate already knows the stack. Verify G+ measures general reasoning ability, which predicts how quickly they'll learn parts of the stack they haven't seen and adapt when production throws something unfamiliar at them. For a senior IC making architectural calls, that signal matters. That said, if you want a leaner shortlist, dropping Verify G+ is a valid tradeoff and the battery still stands. Your call. | # | Name | Test Type | Keys | Duration | Languages | URL | |---|------|-----------|------|----------|-----------|-----| | 1 | Core Java (Advanced Level) (New) | K | Knowledge & Skills | 13 minutes | English (USA) | | | 2 | Spring (New) | K | Knowledge & Skills | 9 minutes | English (USA) | | | 3 | SQL (New) | K | Knowledge & Skills | 9 minutes | English (USA) | | | 4 | Amazon Web Services (AWS) Development (New) | K | Knowledge & Skills | 6 minutes | English (USA) | | | 5 | Docker (New) | K | Knowledge & Skills | 10 minutes | English (USA) | | | 6 | SHL Verify Interactive G+ | A | Ability & Aptitude | 36 minutes | English (USA), Chinese Traditional, Korean, Serbian _(+29 more)_ | | | 7 | Occupational Personality Questionnaire OPQ32r | P | Personality & Behavior | 25 minutes | English International, French (Canada), Portuguese, Chinese Simplified _(+35 more)_ | | _`end_of_conversation`: **false**_ ### Turn 7 **User** > Keep Verify G+. Locking it in. **Agent** Final battery — Java Advanced, Spring, SQL, AWS, and Docker as the technical core; Verify G+ for reasoning; OPQ32r for personality fit on a senior IC who'll mentor and contribute to architecture. | # | Name | Test Type | Keys | Duration | Languages | URL | |---|------|-----------|------|----------|-----------|-----| | 1 | Core Java (Advanced Level) (New) | K | Knowledge & Skills | 13 minutes | English (USA) | | | 2 | Spring (New) | K | Knowledge & Skills | 9 minutes | English (USA) | | | 3 | SQL (New) | K | Knowledge & Skills | 9 minutes | English (USA) | | | 4 | Amazon Web Services (AWS) Development (New) | K | Knowledge & Skills | 6 minutes | English (USA) | | | 5 | Docker (New) | K | Knowledge & Skills | 10 minutes | English (USA) | | | 6 | SHL Verify Interactive G+ | A | Ability & Aptitude | 36 minutes | English (USA), Chinese Traditional, Korean, Serbian _(+29 more)_ | | | 7 | Occupational Personality Questionnaire OPQ32r | P | Personality & Behavior | 25 minutes | English International, French (Canada), Portuguese, Chinese Simplified _(+35 more)_ | | _`end_of_conversation`: **true**_