Enterprise Services Engineer

About the role

Enterprise Services Engineers enable direct platform engagement to help customers achieve operations, risk, compliance, asset, and security outcomes. Work is conducted remotely across Germany with possible on-site customer engagements.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Identify opportunities for customers to increase value from the Tanium platform in support of their operations, risk, compliance, asset, and security objectives.

Perform daily health-checks for assigned accounts and communicate results through clear verbal and written communication.

Track activity, after action reviews, root cause analysis, and daily status reports with contributions aligned to Technical Support Engineers.

Preserve and share knowledge across engagements by documenting best practices and Play Book entries.

Enable customer IT support staff to manage and troubleshoot the Tanium platform effectively through technical direction.

Align solutions with customer priorities by collaborating with Customer Success Managers on Tanium operational status within key accounts.

Requirements

Hold a security clearance at minimum Secret, with Top Secret or DV preferred for engagement eligibility.

Possess a Bachelor degree or equivalent experience as required for professional service roles.

Bring 5+ years of experience in IT or consulting to handle enterprise engagements and stakeholder management.

Maintain 5+ years of experience in Systems Administration or Systems Engineering to demonstrate hands-on platform or infrastructure expertise.

Have experience working with public sector customers and understanding their operational, risk, compliance, and security constraints.

Speak German and English to enable effective communication with stakeholders in both languages.

Apply strong troubleshooting skills to diagnose issues and implement solutions in complex environments.

Break problems down into manageable, ordered parts and articulate the problem statement and plan of attack to others.

hands-on Tanium experience, which serves as a major plus for demonstrating platform proficiency during engagements.

Apply broad knowledge across several technical domains and deep knowledge in endpoint security, endpoint support or troubleshooting, incident response, systems management, systems administration, software engineering, or utility scripting (e.g., Bash, PowerShell, VBScript, Python).

Demonstrate critical thinking skills to assess situations and recommend appropriate courses of action.

Practical notes

Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

The role may involve remote and on-site work, requiring travel to customer locations as needed.

Time is reserved for volunteer work through volunteer time off to support community causes.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.