Immediate Java Spring-Boot senior for threema API implementation

We look for Java Spring-Boog and Core-Java senior expert developer Your job will be to implement requirements which are mutually agreed on this API [login to view URL] maybe helpful: [login to view URL] Mandatory!!!! You have to have a installed threema (TMA) on PC/Laptop and on your smartphone to run on your local environment. You document EACH step how you can run locally the code and threema for testing/CI AND you have a proof that you did this already in the past! Milestones MS1: Implement a spring boot service to listen to incoming threema messages on - direct messages List<MessageDto> sendThreemaDirectMessages(List<MessageDto>) - group messages List<MessageDto> sendThreemaGroupMessages(List<MessageDto>) - channel messages List<MessageDto> sendThreemaChannelMessages(List<MessageDto>) - forward the incoming messages via e-mail List<MessageDto> forwardThreemaMessages(List<MessageDto>, EmailAccountDTO) MS2: - listen to e-mail mailbox on new e-mails fetch the e-mails and send message to corresponding TMA channel List<MessageDto> forwardEmailMessages(EMailAccountDTO) MS3: - add TG user to channel List<UserDto> addUsersToTgChannel(List<UserDto>) - add TG user to group List<UserDto> addUsersToTgGroup(List<UserDto>) Implementations: - a Interface representing the above methods - the impl of the interface - the DTOs are hardcoded examples in multiple JUnit tests, so that the JUnit tests is basically your "main" method replacement with multiple entry points NO UI for now required! NO database required! No REST endpoint exposing for the above named methods required! (only consuming the apis in the given links) 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 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 - you may require to help us here on setup - provided or fully documented steps to start the docker container