Automation QA Engineer - Python (工作地點：新店)

Job Summary:

We are looking for a Python Automation QA Engineer to develop and maintain automated testing solutions for products. This role requires strong Python scripting skills and hands-on experience in test automation frameworks and debugging.

Key Responsibilities:
-Develop and execute Python-based automation scripts for testing and data analysis
-Design and improve test automation frameworks and pipelines
-Perform manual and automated testing when required
-Debug, analyze, and resolve test issues efficiently
-Collaborate with cross-functional teams (Dev / QA / HW)
-Document test cases, results, and processes clearly

Must-Have Skills

• 2+ years Python development experience
• Ability to build scripts / projects independently from scratch
• Experience in test automation or QA environment
• Familiar with pytest / unittest
• Knowledge of CI/CD & Git
• Strong debugging and problem-solving skills

**Please answer the Pre‑screen Questions below.**
Tell me about the most complex project you were part of that went poorly.
Follow‑ups:
What was your role?
What went wrong?
What unplanned problems arose and how did you deal with them?
What lessons did you learn?
What was one thing you did to make it more successful or to get it back on track?
Tell me about a project for which you lacked key information or direction but needed to make progress.
Follow‑ups:
What resources did you consult to proceed?
How did you determine which data points were most important?
Did you encounter any other obstacles and how did you overcome them?
What was the eventual outcome?
If faced with the same situation again, what would you do differently?
What testing work experience do you have?
AI Interest:
How do you use AI tools at work to improve efficiency?

**Please use AI tool to make your CV into a data-driven version.-> Attach the file in the replying email.**
How to write a data‑driven CV?

1. The "Action‑First" Rule
Never start a sentence with “Responsible for” or “Tasks included.”
These phrases are passive and describe the job, not your performance.
Use Strong Action Verbs that imply leadership and technical skill.
Instead of: “Responsible for xTS testing.”
Use: “Spearheaded full‑suite xTS verification…”
or
“Automated xTS retry logic…”
________________________________________
2. The Google “XYZ” Formula
This is the gold standard for quantifying achievements.
Every bullet point should follow this structure to show context, scale, and technical proof.
X (Accomplished): The result (e.g., “Reduced test cycle time”).
Y (Measured by): The data point (e.g., “by 40%”).
Z (Action): The tool/method used (e.g., “by optimizing Tradefed retry parameters”).
________________________________________
3. The “Power of 3” Metrics
Try to include at least one of these three types of numbers in every project description:
Time: e.g., “Accelerated RCA process by 15 hours/week.”
Volume: e.g., “Triaged 500+ critical bugs during the NPI phase.”
Quality: e.g., “Achieved 0% regression rate in production firmware.”
________________________________________
4. Technical Contextualization
Numbers are more impressive when attached to specific high‑level tools.
Mentioning Buganizer, AOSP, or Tradefed alongside a number proves that your technical proficiency drove the result.
Example: “Improved bug triage accuracy by 20% using Python scripts to automate Stack Trace analysis.”
________________________________________
5. The “Before & After” Contrast
Whenever possible, show the state of the project before you arrived and how it improved because of your intervention.
Example: “Transformed a manual sentiment review process into a data‑driven Weekly AQM Report, increasing actionable engineering insights by 35%.”

Nice-to-Have
Android / mobile testing experience
Experience with ADB / Linux
PDF type
Understanding of Android system architecture
Hardware setup / testbed experience