Start by asking the team what they've already checked (avoid repeating work), then approach it fresh with a structured method: review fault history, go to the machine and observe directly, challenge assumptions. Show that experience means a more systematic — not more aggressive — approach.

Choose your best story. Be specific about the technical complexity, the resources you needed, any mistakes you made and corrected, and the final measurable result. Confidence in telling this story matters as much as the content.

Consider: cost of repair vs. replacement, availability of spare, downtime impact, remaining service life, risk of repeat failure, and whether the root cause has been addressed. Show cost awareness — senior techs think about total cost, not just the immediate fix.

Be honest about your strengths. If you're strong on schematics but less confident on PLC ladder logic — say so, and add "I've been developing this skill." Senior roles require a wide reading range, but intellectual honesty builds trust faster than exaggeration.

Describe a real situation where a predictive technique caught a failure before it happened. This demonstrates the highest level of maintenance thinking: preventing problems rather than just solving them. Mention specific tools or software if applicable.

Effective teaching: explain the "why" behind each step, demonstrate first, let them try with supervision, correct without discouraging, and use real machine time — not just theory. Show you genuinely enjoy developing others — it's what makes a senior role truly senior.

The answer reveals your leadership style. Show you addressed the problem first, then had a calm learning conversation — not a public scolding. A good senior tech creates an environment where junior techs are not afraid to report mistakes early, before they become bigger problems.

Show you delegate work based on skill level, prioritize the most critical tasks for yourself, check in regularly without micromanaging, and escalate to your supervisor when resources are insufficient. Overcommitting and burning out helps no one.

Before calling: document the exact fault codes, what you've already checked, and machine operating conditions. This shows professionalism and saves time. Suppliers respond faster and better when you give them precise information, not just "it's broken."

Mention: criticality ranking for spares, minimum/maximum stock levels, lead time awareness for imports, using CMMS for inventory tracking, and periodic audits. A machine sitting idle waiting for a part is a planning failure — show you prevent that.

This is the difference between a reactive technician and a senior one. Show you dug past the symptom to find the real root cause, designed or recommended a permanent fix, and then tracked results over time to confirm it worked.

Be specific about your 90-day plan: learn the equipment, build relationships with the team, identify quick improvements, and demonstrate reliability. Ambition is good — but showing you understand that trust is earned through consistency is even better.