docs: import qa workflow knowledge from grilling session
This commit is contained in:
50
docs/qa-profile.md
Normal file
50
docs/qa-profile.md
Normal file
@@ -0,0 +1,50 @@
|
||||
---
|
||||
last_updated: 2025-07-15
|
||||
tags: [qa-engineer, profile, role, yara724]
|
||||
source: import-knowledge
|
||||
---
|
||||
|
||||
# QA Engineer Profile — Yara724
|
||||
|
||||
## Background
|
||||
|
||||
- **Education**: Mechanical Engineering (Solid Mechanics) — CS/SE fundamentals are limited compared to software engineers.
|
||||
- **Experience**: ~1 year as QA Engineer.
|
||||
- **Code-reading level**: Beginner — reads Backend, User Frontend, Expert Frontend repos when necessary.
|
||||
|
||||
## Official Title vs Actual Role
|
||||
|
||||
Although the official title is QA Engineer, the role combines responsibilities from multiple disciplines:
|
||||
|
||||
- QA Engineer
|
||||
- Requirement Analyst
|
||||
- Product Analyst
|
||||
- Technical Writer
|
||||
- Bug Investigator
|
||||
- API Tester
|
||||
- Database Inspector
|
||||
|
||||
## Responsibilities
|
||||
|
||||
- Functional Testing
|
||||
- Regression Testing
|
||||
- Exploratory Testing
|
||||
- Creating Jira Stories and Tasks
|
||||
- Bug Reporting
|
||||
- Product Analysis
|
||||
- Requirement Analysis
|
||||
- Documentation
|
||||
- UI/UX Improvement Suggestions
|
||||
- Backend API Validation
|
||||
- Communication with Frontend and Backend Developers
|
||||
- Supporting Product Design Decisions
|
||||
|
||||
## Projects
|
||||
|
||||
- **Yara** (main project) — insurance claim management platform
|
||||
- **TamasLink** (Call Center)
|
||||
- Other projects (Balan, Beno, Karjo, etc.) on a periodic basis
|
||||
|
||||
## Reporting
|
||||
|
||||
Work requests come directly from both the CEO and CTO.
|
||||
Reference in New Issue
Block a user