From Questions to Confidence: Preparing for Your Security Systems Technician Interview

Engaging introduction

You installed your first camera years ago. Since then, you have learned to trace elusive faults, commission NVRs at 2 a.m., and calm anxious site managers when an access controller misbehaves right before a VIP visit. Now it is interview day. How do you turn all that hands-on skill into confident, structured answers that win the job?

This guide shows you how to prepare for a Security Systems Technician interview, step by step. We translate technical expertise into compelling stories, surface the most common interview questions, and give you practical exercises you can complete in a weekend. Whether you are applying in Bucharest, Cluj-Napoca, Timisoara, Iasi, Dubai, or Dublin, you will walk in confident, ready to showcase your value.

You will learn how to:

Map your experience to the role and the employer's priorities
Master the most common technical and scenario-based interview questions
Demonstrate your troubleshooting method and safety mindset
Prepare a portfolio that makes your work tangible
Discuss salary ranges with confidence in EUR and RON
Ask smart questions that position you as a problem-solver

If you are short on time, start with the Interview Day Checklist and the 60-Minute Technical Warm-Up. Then return to the full guide for deeper preparation.

Understand the role and what employers value

Before you practice questions, align your experience with the job. Security Systems Technician roles vary by employer, sector, and region, but most include a mix of installation, commissioning, service, and documentation across electronic security systems.

Core systems and tasks

CCTV and video surveillance: IP and hybrid systems, NVR/VMS, camera configuration, storage sizing, analytics tuning.
Access control: Controllers, readers (Wiegand and OSDP), locks (maglocks, electric strikes), door hardware, time schedules, anti-passback.
Intrusion detection: Panels, zones, PIRs, glass-breaks, door contacts, sirens, communications (GSM/IP), EN50131 awareness.
Intercoms and visitor management: SIP, PoE-powered door stations, integration with access control and CCTV.
Perimeter and special systems: Fence detection, LPR/ANPR, enterprise VMS, video walls.
Networking and power: IP addressing, PoE budgets, 12VDC/24VAC power, grounding, surge protection, fiber basics.
Documentation and handover: As-built drawings, cable schedules, labeling, test sheets, end-user training.

What hiring managers look for

Reliable troubleshooting method: You can isolate faults quickly and document fixes.
Safety and compliance: You follow permit-to-work, lockout/tagout, working-at-height rules, and manufacturer instructions.
Customer communication: You explain issues clearly and manage expectations, especially during outages.
Ownership and schedule discipline: You meet SLAs, coordinate with subcontractors, and escalate risks early.
Breadth plus depth: Comfort with multiple brands plus deeper skill in at least one vertical (for example, VMS or access control).
Clean documentation: Your as-builts, configs, and service notes make the next tech's job easier.

Typical employers and sectors

Systems integrators and security contractors (regional and international)
Facilities management and MEP companies managing corporate sites
Manufacturers and distributors with field engineering teams (for example, global brands in CCTV, access control, or intrusion)
End users with in-house security teams: banks, hospitals, data centers, airports, logistics, retail

In Romania, roles cluster around major economic hubs like Bucharest, Cluj-Napoca, Timisoara, and Iasi. International companies often staff projects in industrial parks, malls, and commercial towers where multi-vendor expertise is valuable.

Research the company and role: 45-minute framework

A focused hour of research can increase your success dramatically.

Study the job description and highlight verbs

Extract key tasks: "commission," "troubleshoot," "document," "train," "escalate."
Match each verb to one example from your past work using the STAR method (Situation, Task, Action, Result).

Map brands and technologies

Note specific platforms in the posting (for example, Milestone, Genetec, Axis, Hikvision, Bosch, Lenel, HID, Suprema, Paradox, DSC).
If a brand is new to you, read the quick-start and admin manual, and watch a 10-minute configuration video to understand menus and naming.

Understand the vertical and compliance environment

Datacenter, healthcare, education, government, or retail each have different uptime and privacy requirements.
In the EU, be able to mention GDPR and basic video privacy concepts (camera placement, retention controls, masking).

Research the company's project style

Look for case studies and press releases.
Note if they emphasize enterprise integrations, rapid rollouts, or complex retrofits.

Choose two relevant stories per requirement

Prepare short, concrete stories that show you handled similar tasks. Keep each to 60-90 seconds.

Build a portfolio that speaks for you

A compact, visual portfolio makes abstract claims real. Prepare a 6-10 page PDF you can show on a tablet or laptop, and bring printed copies when appropriate.

Include:

Project snapshots: Before/after photos of a rack, clean cable management, labeled patch panels, door controllers, or camera mounts. Redact any sensitive details.
As-builts and diagrams: One page of a small system topology or a door wiring diagram you created or updated.
Commissioning and test records: Sample checklists, storage calculations, or test reports.
Certifications and training: Manufacturer courses (for example, Axis Communications Academy, Milestone XProtect, Bosch BIS, Suprema BioStar, HID), safety cards, powered access training.
Metrics: Quantify results where possible, such as "Reduced camera downtime by 30% by standardizing PoE switch configs and labels."

In interviews across Bucharest, Cluj-Napoca, Timisoara, and Iasi, a tidy portfolio often differentiates candidates with similar years of experience.

Technical knowledge checklist for interviews

Interviewers often test practical, brand-agnostic knowledge. Use this checklist to self-assess and prepare.

Networking basics for CCTV and access control

IP addressing: Explain subnet masks (/24 vs /27), default gateway, and why APIPA 169.254.x.x appears.
PoE standards: 802.3af (up to 15.4W), 802.3at (up to 30W), and 802.3bt variants. Sum PoE loads to avoid brown-outs.
VLANs and QoS basics: Segregate video traffic; know why multicast and IGMP snooping may be used in VMS networks.
Protocols: ONVIF profiles, RTSP URLs, SIP basics for intercoms.
Remote access and security: VPNs, port forwarding risks, secure passwords, firmware updates, disabling default accounts.

Cabling and power

Copper: Cat5e vs Cat6 performance; maximum lengths (100m for Ethernet) and when to use extenders.
Coax: RG59 vs RG6; HD-TVI/AHD/CVI as hybrid options for retrofits.
Fiber: Singlemode vs multimode basics; when to use SFP modules and media converters.
Power supplies: 12VDC vs 24VAC; basic Ohm's law and voltage drop; fuse sizing.
Grounding and surge: Bonding practices; surge protection for perimeter cameras and controllers.

Example voltage drop calculation:

A 12VDC camera draws 500mA on a 30m 20 AWG pair. The loop resistance of 20 AWG is roughly 65 ohms per km, so 30m loop is about 1.95 ohms. Voltage drop = I x R = 0.5A x 1.95 = 0.975V. Supply at 12V may drop near 11V at the device; check camera spec minimum voltage. Consider thicker cable or local power.

Access control specifics

Readers and protocols: Explain Wiegand vs OSDP and why OSDP is more secure (encryption, supervision).
Door hardware: Differences among maglocks, strikes, and mortise locks; fail-safe vs fail-secure; fire egress rules.
Relays and power separation: Avoid mixing lock power and controller power where not recommended; use diodes for inductive kickback.
Common faults: Door held open alarms due to misaligned contacts; request-to-exit wiring; time schedules and holidays.

CCTV and VMS specifics

Lens and field of view: Focal length, sensor size, and pixel density targets for identification vs detection.
Storage sizing: Bitrate x hours x days x number of cameras, plus overhead; why VBR vs CBR matters.
Recording reliability: RAID levels trade-offs; health monitoring; firmware and driver compatibility.
Analytics: Basic tuning to reduce false alarms (motion zones, sensitivity), privacy masking.

Simple storage example:

24 cameras at an average of 4 Mbps per stream. 4 Mbps = 0.5 MB/s. Per camera per day = 0.5 x 86,400 = 43,200 MB = ~42.2 GB. For 30 days: 42.2 x 30 = 1,266 GB per camera. For 24 cameras: 1,266 x 24 = 30,384 GB, or ~30 TB raw. Add 20% overhead and RAID overhead for drive count selection.

Intrusion and integration basics

Zones and loops: EOL resistors, double EOL supervision; tamper detection.
Communications: IP modules, GSM backup; reporting to ARC/monitoring center.
Standards: Awareness of EN50131 grades and their implications on device choice.

Safety, compliance, and privacy

Working at height: Harness checks, ladder angles, scissor lift training, spotters.
Electrical safety: Isolate, lockout/tagout, test for dead, safe drilling.
Data protection: Camera placement to avoid unnecessary capture; retention and export controls; incident logging; GDPR basics in EU.

Common interview questions and how to answer them

Below are categories you will almost certainly face, sample questions, and high-scoring answer frameworks.

Behavioral and teamwork

"Tell me about a time you had to meet a tight deadline on site."

STAR example: Situation: A retail client in Bucharest had a grand opening in 48 hours and 12 cameras offline after a switch failure. Task: Restore coverage and stabilize recording. Action: Rapidly replaced the switch with a staged spare, re-addressed cameras, applied a VMS device pack, and verified retention. Result: 100% restored within 10 hours; opening proceeded with no incidents. Highlight communication with the store manager and after-hours coordination.

"Describe a conflict you had with a colleague or subcontractor and how you resolved it."

Focus on listening, clarifying roles, and anchoring to the project scope, not personalities. End with a documented action plan and positive outcome.

Technical fundamentals

"Explain PoE and how you calculate if a switch can support all cameras."

Mention 802.3af/at/bt, per-port budget, total switch power budget, worst-case device draw, and headroom (typically 20%). Give a quick math example.

"How would you integrate an ONVIF camera with a VMS that fails to auto-discover it?"

Steps: Confirm network reachability (ping), check VLAN/gateway, update VMS device pack, add via RTSP/ONVIF with correct credentials, sync time via NTP, set stream to H.264/H.265 compatible profile, verify licenses.

"What is the difference between fail-safe and fail-secure locks?"

Fail-safe unlocks on power loss (for example, maglocks). Fail-secure stays locked on power loss (for example, some strikes). Tie answer to life safety and egress requirements.

Scenario-based troubleshooting

"Half of the cameras on a PoE switch randomly drop at night. What do you check?"

Likely power budget or cable/temperature issue. Steps: Review PoE logs and total draw, check camera IR draw increase at night, verify switch temperature, inspect weak cable runs, stagger IR start or raise switch capacity, update firmware.

"Door shows 'held open' continuously."

Check door contact alignment, wiring continuity, controller input configuration (normally open vs normally closed, EOL resistors), magnet gap, and delayed timers. Propose a fix and how you would document the change.

"NVR storage alert: 'Disk dropped from array.'"

Identify RAID type, replace failed disk with same or larger size, monitor rebuild, confirm no multiple disk failures. Communicate retention risk to client.

Safety and quality

"How do you ensure safety when working at height to install a camera?"

Pre-task risk assessment, permit to work, inspect ladders/lifts, PPE, cordon off area, spotter, use fall protection, weather check, and post-task inspection.

"What documentation do you produce after a service visit?"

Service report with timestamped actions, photos, parts used, test results, recommendations, and any changes to network or device credentials. Ensure client signature and update asset register.

Customer communication

"A site manager is angry that a camera is down during a VIP tour. How do you respond?"

Acknowledge impact, give a short diagnosis timebox (for example, 15 minutes), provide an immediate workaround (re-aim adjacent camera, temporary mobile unit), offer ETA for permanent fix, and follow up in writing.

"How do you explain technical issues to non-technical users?"

Use analogies, avoid jargon, show on-screen steps, leave a one-page quick guide, confirm understanding.

Logistics and availability

"Are you willing to travel or be on a call-out rota?"

Be honest. Provide examples of past travel patterns and on-call coverage. Discuss your approach to managing rest and overtime paperwork.

"What tools and test equipment do you bring to site?"

List your core kit: laptop with IP scanner tools, PoE tester, multimeter, cable tester, crimpers, punchdown, tone generator, labeler, SDS drill, PPE. Mention calibration and battery spares.

60-minute technical warm-up before the interview

If you have only an hour to prepare technically, do this:

10 minutes: Review IP addressing and PoE budgets. Prepare one example calculation you can recite.
10 minutes: Skim a VMS quick-start (for example, Milestone or a common NVR). Note how to add a camera manually, set recording, and export video.
10 minutes: Access control refresh: fail-safe vs fail-secure, REX and door contact wiring, OSDP vs Wiegand.
10 minutes: Safety checklist: working at height, isolations, lockout/tagout, permit to work.
10 minutes: Prepare three STAR stories: a tough fault, a tight deadline, and a customer save.
10 minutes: Review your portfolio slides and ensure file paths and videos open quickly on your device.

Demonstrate problem-solving like a pro

Interviewers care less about whether you know every brand and more about how you think. Use this 5-step troubleshooting script in your answers:

Clarify the symptom and scope

Ask: Is the issue isolated or widespread? When did it start? What changed recently?

Reproduce and isolate

Reproduce the issue, then isolate layers: power, physical link, network, device config, application.

Check logs and indicators

Use LEDs, switch logs, VMS alerts, controller event logs.

Apply the smallest safe fix

Re-seat cable, swap port, known-good device, configuration revert, firmware update window.

Verify and document

Test with the end user, capture screenshots, note time spent, create a prevention note.

During the interview, narrate this method briefly as you walk through scenarios. It signals discipline and reduces the temptation to ramble.

Tools, software, and certifications that stand out

Tools and test gear

Laptop with admin rights and standard utilities: IP scanner, SSH/Telnet client, serial console, Wireshark basics.
Network testers: PoE tester, cable verifier, tone and probe, continuity tester.
Electrical: Multimeter, clamp meter if needed, test leads, fuses.
Termination tools: Punchdown, crimpers for RJ45 and coax, fiber cleaning kit if applicable.
Mechanical: SDS drill, anchors appropriate for substrate, torque screwdriver for terminals.
Labeling and documentation: Label printer, QR code labels linked to asset sheets, photo documentation habit.

Software

VMS: Milestone XProtect, Genetec Security Center, Bosch BVMS, or common NVR interfaces.
Access control: LenelS2, Honeywell Pro-Watch, HID, Suprema BioStar, Gallagher, or regional alternatives.
Ticketing/CMMS: ServiceNow, Jira, or client-provided portals for SLAs.
CAD/diagramming: Visio, Draw.io, or similar to update as-builts.

Certifications and training

Manufacturer certifications: Axis Communications Academy, Milestone Certified, Bosch BIS/BVMS, Genetec, HID, Suprema.
Safety: Working at Height, MEWP/Powered Access, Electrical Safety Awareness, First Aid.
Networking: CompTIA Network+ basics can help you frame IP topics.

Add the most relevant items to your CV top section and bring scanned copies in your portfolio.

Salary expectations and market context (Romania and EMEA)

Salaries vary by city, experience, certifications, on-call commitments, and sector (for example, datacenters and critical infrastructure often pay more). The figures below are indicative and may change with market conditions.

Romania - monthly gross salary examples

Junior Security Systems Technician (0-2 years):
- Bucharest: EUR 900 - 1,300 (RON 4,500 - 6,500)
- Cluj-Napoca: EUR 850 - 1,200 (RON 4,200 - 6,000)
- Timisoara: EUR 800 - 1,150 (RON 4,000 - 5,700)
- Iasi: EUR 750 - 1,100 (RON 3,700 - 5,500)
Mid-level (2-5 years, can independently commission and service):
- Bucharest: EUR 1,300 - 2,000 (RON 6,500 - 10,000)
- Cluj-Napoca: EUR 1,200 - 1,800 (RON 6,000 - 9,000)
- Timisoara: EUR 1,100 - 1,700 (RON 5,500 - 8,500)
- Iasi: EUR 1,000 - 1,600 (RON 5,000 - 8,000)
Senior/Lead Technician (5+ years, advanced commissioning, mentoring, small project leadership):
- Bucharest: EUR 2,000 - 2,800 (RON 10,000 - 14,000)
- Cluj-Napoca: EUR 1,800 - 2,500 (RON 9,000 - 12,500)
- Timisoara: EUR 1,700 - 2,400 (RON 8,500 - 12,000)
- Iasi: EUR 1,600 - 2,300 (RON 8,000 - 11,500)

Notes:

Ranges can be higher for datacenter, pharma, or airport environments, or where you cover extensive on-call rotations and travel.
Overtime, meal tickets, company car, fuel card, phone, and training budgets are common benefits and can add significant value.
Confirm whether listed figures are gross or net and understand local tax implications.

EMEA snapshots (gross monthly)

Western Europe (for example, Germany, Netherlands): EUR 2,800 - 4,500 depending on seniority and sector.
Southern Europe (for example, Spain, Portugal): EUR 1,800 - 3,000.
Middle East (for example, UAE, Qatar): AED 6,000 - 12,000 or more, often with housing/transport allowances; tax contexts differ.

How to discuss salary in the interview:

Provide a range based on market and your added value (on-call, certifications, driving license, language skills).
Mention total compensation: overtime, allowances, vehicle, training, and progression to senior or team lead.
Be ready with a recent payslip or offer letter if a formal process requires proof (share only when appropriate and after receiving an offer).

What hiring managers in integrators and end-user teams ask (by sector)

Retail rollouts: Speed, consistency, and documentation. Expect questions about staging NVRs, standard camera configs, and overnight work.
Industrial and logistics: Ruggedized devices, dust and temperature considerations, fiber and long PoE runs, coordination with HSE.
Corporate and datacenters: Change control, maintenance windows, redundancy, badge activation processes, NDA awareness.
Healthcare: Privacy zones, critical areas uptime, patient safety and access, escalation paths.
Education and campuses: Multi-building networks, vandal resistance, holiday schedules and lockdown features.

Prepare one story per sector if your CV spans them, especially for interviews in Bucharest and Cluj-Napoca where multi-vertical portfolios are common.

Questions you should ask the interviewer

Smart questions demonstrate foresight and alignment.

What are the top 3 systems brands on your current sites, and which certifications does the team value most?
How do you stage and document configurations before deploying to production?
What is your typical on-call rotation and SLA structure for critical incidents?
How do you handle change control on enterprise customers, and what tools do technicians use for tickets and as-builts?
What does success look like in the first 90 days? What metrics do you track for technicians?
How do you support training and certification renewals?

Prepare your STAR stories with measurable results

Use this template for each story:

Situation: Brief context with client type and location.
Task: The problem or goal.
Action: Your exact steps, tools, and coordination.
Result: Quantified outcome and customer feedback.

Example 1: CCTV outage, Timisoara logistics hub

Situation: 30% of cameras down after a thunderstorm at a perimeter with frequent false alarms.
Task: Restore service and reduce nuisance alarms.
Action: Verified surge absorbers, replaced two failed midspans, applied VLAN separation, configured motion zones per camera, and added surge protection on fence line.
Result: 100% service restored in 24 hours; false alarms dropped by 60% week over week. Client extended maintenance contract.

Example 2: Access control expansion, Bucharest office tower

Situation: Tenant expansion required 14 new doors with mixed hardware.
Task: Deliver in one weekend cutover.
Action: Staged controllers with correct firmware, assigned OSDP where possible, standardized naming, coordinated locksmith work, created quick user guides.
Result: Zero post-cutover incidents; client survey 9.5/10 satisfaction. Additional 40-door follow-on awarded.

Dress code, documents, and interview day checklist

What to wear

Field technician interview: Smart casual or workwear with clean safety boots if meeting in a workshop environment.
Corporate or client-facing interview: Business casual (collared shirt or polo, clean trousers, closed shoes). Avoid flashy logos.

What to bring

Printed CV and a short project portfolio
Copies of certifications and training cards
References with contact details (if available)
Notepad and pen
Charged laptop/tablet with offline copies of your portfolio
Photo ID and driving license (often requested for field roles)

Day-of checklist

Confirm address, parking, and site access instructions 24 hours in advance
Arrive 10-15 minutes early
Silence phone and smartwatch notifications
Greet with a confident smile and firm but not aggressive handshake
Keep answers concise, with specifics and numbers when possible
Ask your prepared questions near the end
Confirm next steps and expected timeline

Practical exercises to complete before the interview

These small projects give you ready-to-talk examples.

Build a PoE budget spreadsheet

List 16 sample cameras with max power draw. Sum totals and compare to a 16-port 802.3at switch with a 240W budget. Add 20% headroom. Print or include in your portfolio.

Create a small network diagram

Draw a simple topology with router, PoE switch, 8 cameras, an NVR, and a remote viewing PC on a separate VLAN. Annotate IP ranges and trunk ports.

Write a 1-page commissioning checklist

Include device naming conventions, NTP config, password policy, firmware baseline, recording rules, and test captures.

Prepare a troubleshooting flow for a "camera offline" alert

Power check, link LED, switch port status, ping, ARP table, static vs DHCP, device web admin, VMS check, replace with known-good.

Timebox simulation

Take any prior fault you solved and practice a 90-second explanation that highlights your method and outcome.

Handling gaps, brand changes, and limited experience

Employment gaps: Be honest and concise. Focus on what you learned or any freelance or training you did, such as an access control course or personal lab.
New brands: Emphasize transfer skills. If you know Milestone, highlight how that prepares you for Genetec at a high level. Mention manufacturer quick-start guides you studied.
Limited experience: Anchor to safety, attention to detail, and eagerness to learn. Offer references from supervisors who can vouch for your reliability and growth.

Red flags to avoid in your answers

Blaming the client or previous technicians; keep tone professional.
Glossing over safety or skipping permits.
Overstating brand expertise that a 10-minute practical test would expose.
Sharing sensitive site details or configurations without redaction.
Dismissing documentation as unimportant.

Mini mock interview: 10 questions to practice out loud

Walk me through how you would commission an IP camera from unboxing to recording.
How do you decide between maglock and electric strike for a door? What else affects your choice?
A server room camera shows artifacts at night. What could cause it and how do you fix it?
How do you calculate storage for 60 days retention across 40 cameras at 6 Mbps each?
What steps do you take before drilling into a wall or slab?
Describe a time you prevented a repeat incident through documentation or training.
What KPIs should a service team track for quality and speed?
How do you protect systems from cyber risks in small deployments?
Tell me about a time you coached a junior technician.
Why do you want to work with our company and clients in Cluj-Napoca and Timisoara?

Record yourself, then cut filler words and tighten your STAR structure.

After the interview: follow-up that reinforces value

Same day: Send a short thank-you email referencing one or two specific needs they mentioned. Reattach your portfolio PDF if appropriate.
Within 48 hours: If they requested anything additional, send it with a brief note. If you forgot a point, add it concisely.
One week later: If you have not heard back, send a polite check-in, reiterating your interest and availability.

Example message:

"Thank you for the opportunity to discuss the Security Systems Technician role today. I appreciated learning more about your upcoming rollout in Bucharest and the emphasis on structured documentation. I am confident my recent access control expansion project and VMS standardization experience would add value from day one. Please find my portfolio attached again for convenience. I look forward to next steps."

Putting it all together: a 7-day prep plan

Day 1: Research the company and role. Highlight verbs and map to your STAR stories.
Day 2: Build or refresh your portfolio with at least three recent projects.
Day 3: Technical refresh using the checklist. Do the PoE and storage calculations.
Day 4: Practice 10 mock questions. Record and refine answers.
Day 5: Prepare logistics: travel, attire, printed materials.
Day 6: Rest and light review. Skim quick-start guides for top brands mentioned in the posting.
Day 7: Interview day. Review the 60-minute warm-up and your checklist.

Conclusion: turn questions into confidence

Great Security Systems Technicians combine safe hands with clear thinking. Interviews are your chance to show both. Research the company. Prepare real examples that prove your value. Walk in with a tidy portfolio, a repeatable troubleshooting method, and a salary range grounded in the market for Bucharest, Cluj-Napoca, Timisoara, or Iasi. If you do, you will convert tough questions into confident, concise answers.

Ready for your next step? ELEC partners with leading integrators and end users across Europe and the Middle East. If you want targeted roles, interview coaching, or salary insights tailored to your city and skill set, contact ELEC today. We will help you present the strongest version of your story.

FAQ: Security Systems Technician interview preparation

1) What should I wear to a Security Systems Technician interview?

For office-based interviews, business casual works well: collared shirt or polo and clean trousers with closed shoes. For workshop or warehouse settings, clean workwear and safety boots are acceptable. When in doubt, slightly overdress and avoid branded clothing that conflicts with the employer.

2) What documents should I bring?

Bring a printed CV, a short portfolio with photos and diagrams, copies of certifications (for example, Axis, Milestone, HID, Bosch), ID and driving license, and contact details for 2-3 references. Have a digital version of your portfolio on your phone or tablet in case screen sharing is needed.

3) I have not worked with the exact brands listed in the job ad. How do I address this?

Emphasize transfer skills. Explain how your experience with similar platforms maps to their stack (for example, moving from Milestone to Genetec, or from Paradox to DSC). Mention that you studied the target vendor's quick-start guide and watched a configuration video. Offer to complete vendor training in your first 90 days.

4) How can I stand out if I have limited experience?

Show discipline and curiosity. Bring a clean portfolio, however small. Talk through a personal lab or mock setup you built. Emphasize safety, documentation, and a structured troubleshooting method. Strong references and a willingness to cover on-call rotations can also differentiate juniors.

5) How do I discuss salary expectations in Romania?

State a range tied to your experience and city. For example: "Based on my 4 years of commissioning and on-call experience in Bucharest, I am targeting EUR 1,600 - 1,900 gross per month, plus standard benefits." Be ready to discuss overtime, allowances, and training support. Ask whether figures are gross or net.

6) Will there be a technical test?

Often yes. You may be asked to crimp an RJ45, configure a camera on a test bench, calculate PoE or storage, or interpret a door wiring diagram. Practice these tasks and be prepared to narrate your approach, especially your safety and verification steps.

7) What questions should I ask to show I am serious?

Ask about the systems stack, certifications they value, documentation standards, on-call rotations, tooling (ticketing and CMMS), and what success looks like in 90 days. Tailor questions to the sectors they serve in Bucharest, Cluj-Napoca, Timisoara, or Iasi.