1.13Career Translation

Resume phrasing

• Engineered structured test-generation prompts using the five-element framework (Context, Artifact, Constraints, Coverage Goals, Output Format), transforming AI tools from generic code generators into precision test suite producers
• Reduced AI-generated test rework by 50% through systematic prompt iteration, achieving 25-35 well-structured tests per prompt with correct framework, naming conventions, and coverage targets
• Established prompt-as-specification practice within QA team, treating each prompt as a test specification document with measurable impact on test generation quality

Cover letter framing

I treat AI prompt engineering as a core QA engineering skill, not a casual activity. By structuring every test-generation prompt with five essential elements -- technical context, specification artifacts, framework constraints, explicit coverage goals, and output format requirements -- I consistently produce AI output that is immediately usable in production test suites. This systematic approach transforms AI from a novelty tool into a reliable test generation engine, producing 25-35 targeted tests per prompt versus the typical 2-3 generic tests from unstructured requests.

Interview framing

"I approach AI test generation by treating the prompt as a test specification document. Every prompt I write contains five elements: context about the system and tech stack to prevent hallucination, the actual specification artifact pasted directly rather than described, explicit constraints on framework and coding patterns, measurable coverage goals with negative-to-positive ratios, and output format specifications. I iterate through 2-3 refinement cycles, tracking what went wrong and why. The result is a reusable template that the team can apply to similar features. Trade-offs include the upfront investment in prompt engineering versus the massive payoff in test quality and reusability."

What not to say

• "I just ask the AI to write some tests" -- vague prompts produce vague tests; this signals no prompt engineering skill
• "Prompt engineering is not a real skill" -- it is the primary differentiator between useful and useless AI output for test generation
• "I write one prompt and expect perfect output" -- prompt refinement through iteration is essential and normal
• "More words in the prompt always means better output" -- bloated prompts with irrelevant context degrade quality
• "I do not need to specify the test framework" -- without it, the AI guesses and often guesses wrong