Display Engineer Spring, TX

MUST HAVE: Practical troubleshooting. Hands-on work with enterprise PCs displays docking hardware validation or related AV systems; able to explain a real issue investigated beyond replacing hardware or rebooting.
- MUST HAVE: Independent problem solving. Defines the symptom attempts reproduction compares working versus failing setups changes one variable at a time and distinguishes evidence from a guess.
- MUST HAVE: Curiosity and learning agility. Researches unfamiliar technology asks productive questions and can grow into specialized display engineering without needing step-by-step direction.

Secondary Skills - Nice to Haves

• graphics drivers
• Firmware
• BIOS

Job Description

The Display Engineer is a hands-on technical role focused on reproducing isolating validating and resolving display and docking issues in enterprise endpoint environments. Work spans monitors notebooks workstations docks cables graphics drivers firmware operating systems and integrated peripherals. The engineer builds representative test setups compares known-good and failing conditions changes variables systematically and documents findings that engineering teams can act on.
We welcome candidates from enterprise endpoint troubleshooting display or AV integration docking support hardware validation and technical escalation backgrounds. Deep knowledge of every display standard is not a prerequisite. What matters is a demonstrated ability to investigate unfamiliar problems independently learn quickly reproduce symptoms isolate causes and verify results rather than relying on part swaps or routine update/reboot steps.
- Lead complex display investigations. Own end-to-end troubleshooting of issues such as intermittent black screens signal loss or cutouts delayed display detection wake/resume failures resolution or scaling problems refresh-rate limitations multi-monitor instability input switching and dock-to-display behavior.
- Reproduce enterprise environments. Build representative test configurations that mirror the reported endpoint monitor dock cable/adapter path operating system firmware graphics driver display settings and connected peripherals so that testing reflects the actual environment rather than a simplified lab scenario.
- Use disciplined root-cause isolation. Perform controlled A/B testing known-good versus known-bad comparisons and structured test matrices. Change one variable at a time and distinguish correlation common denominators hypotheses and confirmed root cause.
- Troubleshoot the complete display path. Investigate DisplayPort HDMI USB-C video Thunderbolt/USB4 cables docks bandwidth constraints and display detection. Build deeper expertise in link training EDID MST/SST DSC and related protocols as needed.
- Validate multi-display and high-demand topologies. Test single- and multi-monitor configurations daisy chains docking paths high-resolution or high-refresh configurations scaling behavior GPU-to-display workloads and combinations that place greater demand on link bandwidth or topology management.
- Separate video from integrated peripheral paths. Troubleshoot monitors that also function as hubs or conferencing devices by independently validating display USB webcam microphone speaker/audio Ethernet hub enumeration and power-delivery paths rather than treating a one-cable monitor as a single subsystem.
- Perform firmware driver BIOS and OS regression validation. Compare behavior before and after monitor or dock firmware graphics-driver BIOS and operating-system changes. Determine whether an update introduces resolves or exposes an interoperability issue and confirm results through repeatable testing.
- Develop repeatable validation plans. Create test cases for cold boot restart sleep/wake reconnect input changes firmware updates topology changes and repeated cycles. Record reproduction rate and expected-versus-actual behavior so results can be compared over time.
- Collect engineering-quality evidence. Capture exact hardware topology firmware and driver versions OS build reproduction steps and rate logs screenshots/video timing data and known-good/known-bad combinations. Produce concise evidence packages that another engineering team can act on without repeating basic troubleshooting.
- Partner with product and R&D engineering. Escalate well-isolated issues with a clear technical question supporting evidence and a working hypothesis. Collaborate with firmware graphics docking platform and display teams to verify fixes or practical workarounds.
- Support deployment and readiness decisions. Validate proposed fixes firmware and driver releases configuration changes and new display combinations before broader deployment. Identify residual risk and provide clear pass/fail findings and rollout considerations.
- Communicate technical findings clearly. Translate complex troubleshooting results into concise updates for technical and non-technical stakeholders. State what is confirmed what has been ruled out what remains under investigation and what should happen next without overstating the evidence.
- Improve the engineering method. Document reusable test procedures troubleshooting patterns evidence templates and opportunities for automation so recurring display investigations become faster more consistent and easier to scale.