Tech Lead (Rotterdam)

Technical Leadership at Schuberg Philis At Schuberg Philis, we specialize in mission critical IT, partnering closely with our customers to ensure their most vital systems run smoothly and securely. Our engineers are T-shaped professionals who thrive at the intersection of depth and breadth, combining deep expertise in their fields with a collaborative mindset to ensure 100% customer satisfaction. Working within dedicated, cross-functional, self-steering Customer Teams, we take ownership of complex challenges and co-create solutions that align with our customers’ goals.

From designing and building robust systems to managing secure, business critical platforms, we do it all. We automate as much as possible, support the (customer) team and developers on applications, and keep platforms secure, up to date and available. Within these teams, the Tech Lead plays a key role.

You are a Mission Critical Engineer with added responsibility for technical leadership, quality, and long-term direction. This is a hands-on engineering role, not a management layer. There is no formal hierarchy: you’re not “in charge of” other engineers.

Instead, you influence by expertise, trust, and example. g. government and public sector), in and around the Rotterdam region.

You’ll have regular customer contact, be part of the core customer team, and also be expected to facilitate technical leadership across teams and within our internal Tech Lead community.

Responsibilities

vary depending on the specific customer landscape and domain, but may include: Act as the technical point of contact: Be the default go to person for technical leadership within your customer team. Represent the team toward the customer on technical topics and decisions. Translate complex technical concepts into clear, understandable language for all stakeholders.

Shape and guard the technical vision: Formulate and maintain a clear technical vision for the customer team. Ensure solutions align with the customer’s enterprise, business and security architecture. Balance innovation with stability, risk, and cost.

Lead within the account “triangle”: Work as an equal peer with the Customer Director Sales and Customer Director Delivery (together with the MD forming the Account Team). Jointly own decisions: bigger decisions are made with the consent of the whole Account Team. For technical topics, organize and facilitate the decision-making process toward consent within the team.

Drive best practices and standardization: Promote and evolve SBP best practices instead of reinventing the wheel. Help define reusable platforms, patterns, and reference architectures. Decide when to go “custom” and when to standardize, based on customer value rather than technical curiosity.

g. security leads, data protection leads) to ensure a “whole system in the room” approach. Ensure high standards and quality (plan–build–run): Guard quality across the entire lifecycle: design, implementation, and operations.

Encourage a “thinking by doing” mindset: prototype, validate, and improve continuously. Identify operational and project risks early and coordinate mitigation within the team. Challenge substandard work constructively and help colleagues grow through feedback.

Support agile ways of working to keep the team focused on the right priorities. Be a trusted advisor: Deepen your understanding of the customer’s business domain and apply that context to technical decisions. Ask the question behind the question to get to the real problem.

Help customers think strategically about businesstoIT challenges, sometimes even concluding that SBP is not the right party for a specific need. Work with a wide range of stakeholders: executives, product owners, architects, and engineers.