Lead Software Engineer
Luxoft DXC
⚲ Wroclaw
Wymagania
- Java
- Spring
- TypeScript
- React
- MSSQL
Opis stanowiska
The Lead Software Engineer role at Tricentis sits at the intersection of technical excellence and team effectiveness. You will drive the architectural and technical direction of your team while staying hands-on — owning critical engineering decisions, removing blockers, and helping translate strategy into execution. NeoLoad helps enterprises test at scale — think Black Friday traffic, mission-critical banking systems, global SaaS platforms. Our customers depend on us to ensure their applications won't fail when millions of users hit them simultaneously. You will work with our Prague and Gemenos engineering teams across product streams that span AI-powered testing capabilities, enterprise integrations, and full-stack product development. What You'll Actually Do - Drive technical decision-making for your team: define architectural patterns, evaluate technology choices, and ensure decisions are well-reasoned, documented, and socialised. - Own the tactical execution of your team's engineering roadmap — break down ambiguous problems into well-scoped work, maintain delivery momentum, and proactively surface risks before they become blockers. - Stay hands-on: contribute to critical parts of the codebase, lead by example in code quality and engineering practices, and take ownership of the most complex technical problems. - Collaborate closely with Product and UX from discovery through delivery — challenge requirements, propose better solutions, and ensure the team builds the right thing, not just any thing. - Work across the NeoLoad product and platform — spanning core test execution engines, integrations, and the UIs that make complex data accessible for enterprise users. - Set and uphold engineering standards across the team: code reviews, design reviews, testing discipline, and operational readiness. - Lead production incident response for your team — coordinate investigation and resolution, ensure clear communication during incidents, and own post-incident reviews that drive lasting improvements. - Act as a technical bridge between your team and the broader engineering organisation — aligning on cross-team dependencies, reusable patterns, and platform direction.