I'm a QA Engineer who genuinely loves the process of building quality from the ground up. I work best when I'm close to the team — understanding the why behind every feature, not just the what.
I came to QA through a winding path — law school, product management, customer support, frontend development — and honestly, I think that's my biggest strength. I understand software from a lot of different angles, which makes me better at asking the questions that matter.
What I love most is building a test process from zero. There's something deeply satisfying about looking at a new feature with no test coverage and turning it into something the whole team can ship with confidence.
I'm most effective when I'm embedded in the team — in standups, in refinement sessions, in Slack threads with devs and designers. I don't just test at the end; I try to catch things before they're even built.
My current role — and the one where I've grown the most. I own test coverage for new features end-to-end, from writing test plans against backlog items all the way through exploratory and regression testing before release. A big part of my day is API testing in Postman and digging into SQL logs when something looks off. I work closely with backend, frontend, and design teams daily, and I genuinely enjoy being in the room where requirements get shaped — it's the best place to catch problems early.
My first dedicated QA role, on a B2B marketplace platform. I got to design test cases for new features from scratch — which is exactly the kind of work I love. I handled functional, regression, and end-to-end testing, and got comfortable with REST API testing and Jira-based defect tracking. Short stint, but a big step.
I build responsive web apps on the side — HTML, CSS, JavaScript. Doing this in parallel with QA work has been surprisingly valuable. When you've written the frontend yourself, you test it differently. You know where the edge cases hide.
This role gave me something most QA engineers don't have: a real understanding of how product decisions get made. I defined user flows, worked with technical teams on requirements, and learned to think about quality from the product side — not just the testing side. That perspective still shapes how I approach my QA work.
Two of Iran's most-used digital platforms. This is where I learned that quality isn't just about code — it's about how real people experience a product. Talking to users every day gave me a sharp eye for the kinds of bugs that actually hurt people, and a strong instinct for what "good enough" never is.
Whether you have a role in mind, want to talk about quality engineering, or just want to connect — I'm always happy to chat. Drop me a message.