About
We built this because most teams can’t see it from the inside.
Why e-StruQtA
Some connections are only obvious from outside the sprint
We spent years inside QA teams, not consulting on them. That’s where we noticed something: the link between a bug pattern and a planning gap, or between “QA is slow” and “QA joins too late,” is obvious once you see it, and easy to miss entirely when you’re inside the sprint every day.
We didn’t start e-StruQtA to sell more process. We started it because we kept seeing those connections, and kept meeting good teams who couldn’t, not from lack of skill, just lack of distance.
Who’s behind it
Two people, one habit of noticing patterns
Simona Cîrciu-Ceacîru
Co-Founder
10+ years in software quality. Currently leads a QA team across multiple projects at once. Built a test automation framework from zero, migrated test management tooling, helped prepare a QA process for ISO 9001. Still runs QA day to day, so nothing here is theoretical.
ISTQB · verified
Bogdan Turcu
Co-Founder
Builds test automation for enterprise software, with a focus on API testing. Background includes industries where a missed defect isn’t an inconvenience, it’s a safety issue. Focuses on API test architecture and automation implementation.
CI/CD · verified
How we work
A short list, kept short on purpose
We say no when we’re not the right fit.
If we can’t find real gaps in two working sessions, we stop, at no charge.
We fix how QA works. We don’t add headcount.
No pitch. Just a conversation.