anton-liauchuk/java-interview

This system is a collection of Java-based educational and experimental modules, including a custom Stream API implementation, deadlock demonstrations, and data structure algorithm solutions. It also features a review service for processing candidate scores and SQL queries for person data. The codebase is structured with multiple independent Java projects, each with its own build configuration and test suite.

The repository now includes a Contributor Covenant Code of Conduct (CODE\_OF\_CONDUCT.md) and an MIT License (LICENSE) file, establishing community guidelines and legal terms for the project.

(repo-wide) · high confidence

A new InterviewService component has been added to the review module. This service handles the process of calculating a candidate's score using an ML-based scoring service, persisting the result to the database, and sending a callback to an external service. The implementation includes local Candidate and Score data classes to support this workflow.

review · high confidence

Added a new set of data structure and algorithm implementations, including a brute-force solution for the Maximal Square problem, alongside implementations for Find All Anagrams in a String, Intersection of Two Linked Lists, Longest Substring Without Repeating Characters, Maximum Depth of Binary Tree, Mean of Range in Array, Min Stack, Move Zeroes, Reverse Linked List, Search Insert Position, Single Number, and Valid Parentheses. Each implementation is accompanied by corresponding JUnit 5 tests to verify correctness.

leetcode-221-maximal-square · high confidence

A new SQL file, sql/persons.sql, was added containing two queries: one to select the name and maximum age from the persons table grouped by name, and another to select name and age from the persons table grouped by name and age where the count of names is greater than one.

sql · high confidence

A new Java class, Deadlock.java, was added to the deadlock module. It demonstrates a classic deadlock scenario by creating two threads that acquire two shared monitors in opposite orders, causing a potential lock-up.

deadlock · high confidence

The custom-stream module now includes a custom implementation of the Java Stream API, featuring a ReferencePipeline that supports filter, map, and toList operations on a custom StreamObject type. The module is configured with a Gradle wrapper (gradle-4.10.3) to standardize the build environment, and includes a corresponding JUnit test to verify the stream operations.

custom-stream · high confidence

Introduced build scripts for two new Java projects: 'custom-stream' and 'leetcode-221-maximal-square'. The 'custom-stream' project is configured for Java 1.8 with JUnit 4.12 for testing. The 'leetcode-221-maximal-square' project targets Java 25 and uses JUnit 5.10.0 (via BOM) along with AssertJ 3.27.6 for testing.

(dependencies) · medium confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 50 → 57 (+6.9)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 99 → 99 (+0.4)
• Architecture 69 → 100 (+31.0)
• Maturity 62 → 52 (-10.7)
• Readiness 24 → 35 (+11.1)
• Security 100 → 100 (+0.0)

• Coverage not included — suite not readable by the collector
• Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
• No exposed public API
• Small-team knowledge concentration
• Test reliability not included

• Dependency hygiene PARTLY measured — Maven/Gradle declarations read, no dependency graph resolved
• Documentation: no installation or build instructions (README.md)
• No assertions: debugStream (custom-stream/src/test/java/StreamTest.java)
• Test project verifies nothing: custom-stream (custom-stream/src/test/java/StreamTest.java)
• bus factor 1 — one contributor carries this repository

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

anton-liauchuk/java-interview was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.