Quality Engineer

Role Summary

The QA Engineer ensures the "handshake" between a bots firmware and its physical movements is seamless. Unlike standard firmware testing, this role is centered on functional logic—making sure that digital commands result in the correct physical actions. You will be the primary investigator, verifying that when the firmware says "Go," the bot moves, and when the hardware hits a limit, the firmware knows to stop. You bridge the gap between the code and the machine to ensure the entire system works reliably in the real world.

Key Responsibilities

• Movement Validation: Verify that firmware commands (Move, Rotate, Lift) translate into the correct physical response from motors and wheels.
• Functional Logic Testing: Run "If-Then" scenarios to ensure the bot reacts correctly to its environment (e.g., If an obstacle is detected, Then the movement must stop).
• System Status Matching: Ensure the firmware accurately reflects the bot's physical state, such as battery levels, sensor triggers, or error lights.
• Hardware Troubleshooting: When a failure occurs, use basic logic to determine if the issue is a firmware glitch, a mechanical jam, or an electrical disconnect.

Requirements & Skills

• Hardware-First Mindset: A strong inclination toward physical testing; you are more interested in how the bot moves than how the code is written.
• Basic System Logic: A solid understanding of "Input/Output" flow—knowing how a sensor signal should trigger a specific motor response.
• Testing Morale: A disciplined approach to quality; you take pride in identifying physical inconsistencies and ensuring the bot is "field-ready."
• Basic Technical Tools: Proficiency using a multimeter to check voltage or continuity and comfort using basic hand tools for minor mechanical adjustments.
• Schematic Literacy: Ability to read basic wiring diagrams or system maps to understand how the bot’s components are connected.
• Clear Communication: The ability to explain a physical hardware failure in simple, logical terms to the firmware team.