Senior Backend Developer

Tehtävä

Mitä odotamme

• Building new features and integrations with third-party systems you don’t control.
• Owning end to end integration and shipping your own work to production
• Performing improvements, investigations and bug fixes to ensure system reliability.
• Creating and maintaining automated tests for robust and efficient software.
• Helping to refine user stories and tasks, ensuring they are well understood and actionable.
• Maintaining a clear and efficient code structure based on best practices and Domain-Driven Design.
• Conducting code reviews to ensure code quality.
• Ensuring proper separation of domains and promoting low coupling within the codebase
• An MVP mindset, you build, you ship out, you collect feedback and make it better.
• Ability to plan ahead just enough before going down the rabbit hole of painting the full picture.
• You know your way around working effectively within a team, but have the ability to work independently on large scale (high availability) SaaS products with zero-downtime.
• 3-5 years experience with PHP and/or Java (proficient in one, genuinely hands-on with the other, and happy to work across both)
• Commercial experience with Laravel and/or SpringBoot frameworks (proficient in one, genuinely hands-on with the other, and happy to work across both)
• Solid experience with relational databases like MySQL or PostgreSQL and a deep understanding of transactions and isolation levels.
• Knowledge of AWS, Kubernetes, and Docker for scalable, high-performance back-end development.
• Understanding of event-driven architectures and experience with event-driven technologies like Apache Kafka.
• Fluent in English, both written and spoken, to collaborate with international colleagues and remote teams.
• You are dogmatic regarding technical implementations without pondering trade-offs and constraints (time, effort, complexity, value, ...).
• You expect to always have completely clear and static roadmaps and feature requirements (we are agile, plans change as information becomes available).
• You are unwilling to constructively contribute to technical, product and business discussions.
• You cannot commit to a direction/decision you disagree with (we can't always please everyone)