Senior Software Engineer

• Help shape the engineering vision for backend microservices and serve as the team’s primary technical reference.
• Help plan changes, identify technical debt, propose improvements, and define the technical backlog.
• Independently lead initiatives that involve multiple teams.
• Partner with team leadership and temporarily step in for them when necessary.
• Evaluate and help define the adoption strategy for new technologies and GenAI tools, ensuring they strengthen the team without making systems more fragile.
• Develop a deep understanding of the team’s applications and be able to explain and challenge why they were designed and implemented in a particular way.
• Develop tools and identify best practices that improve the team’s workflow and productivity.
• Share best practices and create learning and knowledge-sharing opportunities within the team.
• Help improve colleagues’ ideas, while identifying problems and proposing solutions.
• Communicate technical decisions clearly and with a solid rationale, encouraging this practice across the team.
• Take on essential tasks even when they are not particularly appealing, setting an example for less experienced team members.
• Look beyond your own team and propose improvements and solutions for other areas of the company as well.

• At least 5 years of software development experience.
• Strong experience with backend development using Java and Spring.
• Strong technical foundation in algorithms, programming languages (Java/Spring), the JVM, networking, databases, and distributed systems.
• Expertise in microservices architecture, with the ability to understand, challenge, and explain why systems are designed in a particular way.
• Experience designing robust, observable, and scalable solutions, and orchestrating complex solutions across multiple components and teams.
• Daily use of GenAI, with experience evaluating the adoption of AI tools without making systems more fragile.
• Experience leading production support, incident response, and post-incident reviews.
• Experience identifying technical debt, proposing improvements, and helping define the technical backlog.
• Clear communication, always grounded in a solid rationale for each decision, and openness to having your own ideas reviewed and challenged.