SummaryWe are looking for a Junior QA Automation Engineer with solid technical fundamentals, a strong quality mindset, and the ability to clearly separate business intent from technical implementation.The ideal candidate is motivated to grow in test automation for financial systems based on Java, BDD, and messaging-based architectures. Junior QA Automation Engineer (Java / BDD / Financial Systems)Contract type: B2B onlyWork model: hybrid (Warsaw) Must HaveJava & Automation FundamentalsBasic knowledge of Java 17Ability to read and modify existing codeUnderstanding of core concepts: classes, interfaces, collections, exceptionsFamiliarity with basic design patterns (Builder, Factory – conceptual level)BDD & Test AutomationBasic knowledge of Cucumber and BDDUnderstanding of Gherkin syntax (Given / When / Then)Ability to create and maintain BDD scenariosClear distinction between business scenarios and technical step implementationUnderstanding that automated tests are production-level codeCI/CD & ToolingCI/CD awarenessBasic experience with JenkinsAbility to run jobs, read build logs, and identify failuresQuality & Engineering MindsetQA-oriented mindset with strong focus on quality, stability, and test maintainabilityAnalytical thinking and attention to detailUnderstanding of system architecture fundamentalsKnowledge of client–server architectureBasic understanding of microservices architecture and inter-service communicationAttitudeStrong willingness to learn and growOpenness to feedback and continuous improvement Should HaveUnderstanding of software testing fundamentalsExperience in manual testing (commercial or project-based)Ability to work with Kibana (searching, filtering, analyzing logs)Basic proficiency with Unix/Linux CLI Nice to HaveBasic knowledge of financial markets, especially FXUnderstanding of concepts such as currency pairs, orders, trades, spot vs forwardBasic familiarity with the FIX protocolUnderstanding of FIX message structure and message typesBasic understanding of Spring Framework concepts (e.g. dependency injection)Familiarity with JUnit 5 (test structure, assertions, lifecycle)