IT Support Technician (IT-Support)

What this role typically covers

• Incident intake, triage, and resolution (L1/L2 depending on project).
• Device setup: laptops, desktops, mobile devices, peripherals, printers.
• Account support: access, MFA, password resets, group membership.
• Clear documentation: steps taken, root cause hints, and handover notes.

Gross pay baseline (01 Jan 2026)

This page presents gross figures. Net pay depends on your tax class, residency/tax situation, and deductions.

Who succeeds here

• Comfortable with Windows endpoints + Microsoft 365 daily operations.
• Uses checklists: onboarding, device handover, access requests, and approvals.
• Knows when to escalate and how to write a clean escalation note.
• Respects security and privacy rules (least privilege, no “quick hacks”).

What you will do on Germany-based projects

Service desk & ticket discipline

• Receive incidents/requests, confirm impact/urgency, and apply consistent triage.
• Resolve common issues: email/Teams access, password/MFA resets, VPN connectivity, printing, device performance.
• Work with SLAs: update users, set expectations, document the next action before pausing a ticket.
• Escalate correctly: reproduce steps, attach logs/screenshots (when permitted), and describe business impact.

Onboarding, devices, and asset flow

• Prepare and hand over laptops/desktops: imaging/enrollment, endpoint security checks, basic hardening steps (per policy).
• Configure user access: directory accounts, group access, shared mailboxes, and standard app packages.
• Maintain asset records: serials, handover confirmations, replacements, returns, and damaged equipment reporting.
• Support offboarding: access removal coordination, device return scheduling, and documentation closure.

On-site communication

• Explain resolution steps in clear English and avoid ambiguous “fixed” messages.
• Coordinate with local stakeholders (office/site management) and respect operational constraints.
• Keep confidentiality: no sharing of sensitive data, credentials, or internal screenshots outside approved tools.

Minimum expectations

• CV in English (PDF preferred) — required for review.
• Hands-on experience in user support (helpdesk, desktop support, or service desk).
• Confidence with at least one ticketing system (ServiceNow/Jira/Zendesk or equivalent).
• Basic endpoint troubleshooting workflow: isolate → test → document → confirm with user.
• Professional conduct and reliability (shift readiness, punctuality, respect for security rules).

Technical stack (typical)

Strong advantages

• German A1–A2 helps with safety briefings and local coordination.
• ITIL vocabulary and “SLA thinking” (updates, ownership, and handovers).
• Experience with structured onboarding/offboarding in corporate environments.

What “working via a Polish company in Germany” usually means

Many Germany-based projects operate with multi-site teams. When a Polish company assigns staff to Germany, the practical focus is compliance, predictable payroll, and clear responsibility lines on-site. You are expected to work to Germany-level standards (working time rules, safety, documentation), while HR coordination and administrative handling are centralized.

Operational terms you should understand (plain language)

• Contract & payroll: you receive payslips and a defined gross rate; hours are tracked and reconciled.
• Workplace rules: site security, data protection, badge access, and device handling policies are enforced.
• Social security (case-by-case): depending on your situation and assignment model, the employer prepares the correct documentation.
• Accommodation/travel (project-dependent): some projects include organized housing or support; terms must be clarified before start.
• Tools: standard work equipment is provided or specified; personal device use may be restricted.

This is general operational information, not legal advice. Final eligibility and document sets depend on nationality, role, and project model.

Reality check: a lawful route is required

For non-EU candidates, language alone is not sufficient. Authorities and employers require a compliant employment pathway. Skilled profiles have more realistic options; entry-level access can be limited.

• Skilled worker pathway: realistic when your qualification and experience match the IT scope and can be evidenced.
• Project fit: budgets, security clearance needs, and onboarding capacity affect feasibility.
• Documentation quality: clear CV + certificates reduce verification time significantly.

Internal resource for permit-side preparation (Poland): https://mavial.pl/zezwolenie.html

Prepare these before applying

• CV in English (PDF) + a reachable phone/email
• Passport scan + current location (country/city)
• Certificates (IT, vocational, training) where applicable
• Short project list: dates, environments, ticketing tool, tasks, outcomes
• Optional: recommendation letters or manager references (if available)

Well-structured documents reduce back-and-forth and improve screening speed.

Fast, structured application

1. Create/Upload your CV: mavial.pl/en/cv.html
2. Send your profile via the contact page: mavial.pl/kontakt.html
3. Include availability, preferred city/region (Berlin/Hamburg/Munich/NRW), and your tool stack.
4. We review fit, verify documents, and contact you if the profile matches active demand.

No CV — no review. This rule protects processing time and ensures consistent screening.