Aref Farahani
Quality Assurance Engineer
I investigate software behavior to find what others miss.
Product behavior · APIs · Integrations · Automation · Evidence
About
I don’t test
software.
I investigate
how it
behaves.
QA Engineer · Product thinker · System investigator
Scroll to trace the journey02 · Career trace
Start
2014
Toorintan
Manual Tester
First steps into software testing and quality.
Persian Sazeh Parto
QA Tester
Building a foundation in systematic testing and defect analysis.
Karina Mobile Solutions
QA Engineer
Focused on mobile product quality and user experience.
Pasargad Electronic Payment
Senior QA Engineer
Automation unlocked. APIs, performance, cross-browser.
Asan Pardakht
QA Engineer
Mobile, Web and PWA quality at scale. Pixel perfect.
DigiExpress
QA Engineer
Exploring data, APIs and business logic. Following defects deeper.
Now
Rechat
SQA Engineer
Real estate platform across multiple systems and integrations.
03 · By the numbers
0+
Years of experience
0+
Products & platforms
0+
Bugs found & reported
0+
API endpoints tested
0+
Browsers & devices covered
0+
Teams collaborated
04 · Beyond QA
I'm Aref Farahani, a quality engineer with a passion for understanding how complex systems behave.
I enjoy turning ambiguity into clarity, building useful tools, and sharing what I learn along the way.
Outside of work, you'll find me reading, traveling, and chasing better coffee wherever I go.
A small state failure.
A big impact.
What happened
The editor lost the restored selection while the persisted membership remained.
Reselecting the same member created a duplicate.
The UI forgot.
The persisted state didn’t.
Follow the data
It looked correct all the way…
until it reached the user.
Hello {{recipient.first_name}},
Delivered
Hello {{recipient.first_name}},
Literal output
Expected
Hello [resolved name],
Observed
Hello {{recipient.first_name}},
The editor wasn’t the product.
The delivered artifact was.
Check the context
Same entity.Same state.Different truth.
Context / Session
State
Completed
Value
Value A
Context / Public
State
Completed
Value
Value B
The data wasn’t wrong.
The context was.
Featured lab
Repository
Intelligence
Turning repository history into testing context.
History
Timeline of change
Connections
Reveal what matters
Context
Drive smarter testing
Change found. Impact understood. Testing context ready.
Repository Intelligence traces a change through the files it touches, the consumers and dependencies that reference them, the tests and impact analysis that follow, converging into QA context — the actionable testing insight the investigation produces.
How I think
Understand.
Break.
Improve.
Repeat.
My QA process is a continuous loop of curiosity, evidence and improvement.
Curiosity first
Start with questions,
not assumptions.
Evidence driven
Observe deeply,
validate clearly.
Measurable impact
Every cycle should make
the product stronger.
Continuous learning
Every investigation should
make the next one smarter.
Ask better questions.
Find what matters.
Connect the dots.
Expose the gaps.
See patterns.
Scale the value.
Every answer creates
a better question.
The QA mindset is a continuous cycle: question, understand, explore, break, observe, and automate, before returning to question again with a better question than the one that started the cycle.
Found a bug?
Escalate it.
Production is on fire?
Something behaves differently at 2 AM?
Or you just want to say hello?
Current status
Available for
Interesting problems
No ticket required. 😎
© 2026 Aref Farahani
Quality engineering
Investigate. Understand. Improve.