ArchUnit Expert for Spring Boot app verification

I am looking for an ArchUnit expert who can help me implement architectural rules in a Spring Boot projects Tasks: - Implement architectural rules in the Spring Boot codebase - Ensure code quality and adherence to architectural guidelines Skills and Experience: - Strong proficiency in using ArchUnit to implement architectural rules - In-depth knowledge and experience with Spring Boot framework - In-depth knowledge and experience with Spring Boot framework with providing rest-apis but also consuming them as a REST client! Your background is: - multiple years of experience with Java - multiple years of experience with REST APIs If you are a good fit, you are open to get more tasks about implementing solutions fully on your own (e.g. with your team) Budget? will not be disclosed, place your best bid to get considered MS1: - implement full rules to ensure juniors are implementing well spring-boot services - package naming - class naming - class annotations - logger usage (SLF4j annotation) no other logger - no cycles in services MS2: - same as above but for rest endpoint exposing MS3: - dependency management What is next? We will share you a NDA and afterwards a paid test task. Payment? - you estimate in a WBS (optimistic, expected, pessimistic, where optimistic < expected < pessimistic) after getting the task - we discuss about clearances and effort - we mutually agree to effort - we assign you the task after mutually agreed - you implement, test and deliver - you provide also unit /integration tests to ensure code is always working - you document each required step to make interaction of systems to work - we test on our premise (you maybe help to fix issues) - we pay (basically the rules of freelancer) Closed book vs open book? We work only on open book. Closed book means you are unwilling to define a WBS for the work and you add only a price tag to the task. We are sorry we will not hire you in such a case! Deliveries? - in our on premise git (access will be granted to you) - full sources - mutliple samples of body and responses of the api in test/resources which will be used as unit tests - maven - libs, need prior confirm and we prefer to use mostly latest stable versions - JDK 17 (mostly LTS) - your api access code working on our end - provided or fully documented steps to start the docker container the full runtime