Mircea-Alexandru Raducanu
QA Engineer
JavaScript
TypeScript
UI Component Architecture: 4/10
Accessibility & Semantics: 4/10
Active 3 days ago
+40 (742) 194204
Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
Mid-level E2E Test Automation engineer focused on Playwright-based UI test frameworks and page-object design. The strongest proven skill is building Playwright page objects and fixtures as shown in projects/the-internet/page-objects/file-download.page.ts and projects/the-internet/fixtures/page.fixtures.ts. There is little to no public evidence of CI workflow automation, contract/schema testing, mutation or performance testing in the analyzed human-authored files.
Technical skills
JavaScript
TypeScript• Middle
Frontend
Frontend
DevOps
CI/CD• 3y+
Jenkins• 3y+
GitHub Actions
QA
BrowserStack
QA
Playwright
Postman
AI/ML
ChatGPT
Claude
Claude Code
Copilot
Cursor
Timeline
QA Automation Engineer
•
Middle
QA DNA
•
Full-Time
Developed and maintained end-to-end test automation for multiple products, using Playwright with TypeScript. Performed API tests with Postman to validate endpoints, payloads, and error handling. Designed test plans and test cases to cover business and functional requirements, and executed cross-browser and cross-device checks. Collaborated with developers and product owners in Agile sprints to support high-quality releases.
Playwright
TypeScript
Postman
QA Engineer
•
Middle
Simpology
•
Full-Time
Performed functional, smoke, sanity, regression, exploratory, acceptance, and related testing types to ensure software quality. Built and maintained comprehensive regression documentation and test cases to support QA workflows. Participated in client User Acceptance Testing and verified that delivered features matched business requirements. Documented bugs and confirmed defect fixes with close collaboration with developers.
Business Analyst
•
Middle
Simpology
•
Full-Time
Collected, analyzed, and documented business and functional requirements, converting customer needs into actionable specifications. Performed gap analysis to identify mismatches between business needs and system behavior and proposed improvements. Coordinated with cross-functional teams, including developers, QA engineers, and product owners, to ensure correct requirement implementation in Agile. Configured client-specific business rules using a logical operator engine to drive dynamic UI behavior.
Middle Frontend Developer
Confidence: Medium App Engineer
Playwright test automation developer (Middle level) specializing in building page-object based end-to-end UI test suites. The strongest proven skill is designing reusable page-object architecture and shared fixtures as shown by the structured page and component classes and the page.fixtures.ts fixture composition. There is limited evidence of advanced frontend engineering such as performance audits, accessibility automation in CI, complex state machines, or production application code beyond test automation.
UI Component Architecture
4/10
How interface parts are built
Clear page-object composition and separation of responsibilities across page and component classes, but no evidence of a custom design system or novel component architecture.
Evidence
ma-raducanu/pw-mr-bit/mr-bit/objects/pages/base.page.ts: BasePage instantiates SignUpModal, LoginModal and WheelModal showing composition of page and component objects
ma-raducanu/pw-test-auto-project/projects/automation-exercise/page-objects/signup-login.page.ts: SignupLoginPage defines many Locator fields and a registerNewUser method implementing interaction flows
Responsive & Cross-browser
3/10
Works on all screens and browsers
Basic cross-browser and mobile viewport configuration via Playwright device presets and explicit viewport settings; no advanced responsive strategies or RTL/i18n plumbing visible.
Performance Optimization
2/10
Speed of the interface
Some basic test-run performance controls (parallel runs, worker limits) are configured but there is no measured optimization, bundle analysis, virtualization or deeper performance engineering.
Accessibility & Semantics
4/10
Usable for everyone
Good use of semantic selectors (getByRole) which aids accessibility and robust selection; however there is no sign of automated a11y testing, ARIA handling for custom widgets or CI enforcement of accessibility rules.
State Management & Data Flow
3/10
Managing data in the app
Reasonable async discipline for UI tests including waitForEvent for downloads and visibility checks before interactions; no evidence of advanced request cancellation, optimistic updates, cache invalidation or state machines.
Evidence
ma-raducanu/pw-test-auto-project/projects/the-internet/page-objects/file-download.page.ts: downloadFile uses page.waitForEvent('download') and getDownloadedFilePath throws when path unavailable
ma-raducanu/pw-test-auto-project/projects/the-internet/fixtures/page.fixtures.ts: base.extend provides page object instances as fixtures, showing structured test-data flow
UX & Visual Polish
3/10
Look and feel quality
Tests assert edge states such as visibility and disabled controls which improves UX reliability, but there are no skeletons, perceived-performance strategies, undo patterns or deliberate transition tuning.
Evidence
ma-raducanu/pw-mr-bit/mr-bit/tests/casino.spec.ts: many assertions using toBeVisible, toHaveClass and toBeDisabled to validate UI states
ma-raducanu/pw-test-auto-project/projects/automation-exercise/page-objects/signup-login.page.ts: registerNewUser fills form fields and drives the full sign-up flow
Expertise
Frontend Architecture & Build Tools• Middle
Industries
Gaming• Middle
Technologies
Frontend
TypeScript• Middle
Recommendations
- Develop and maintain Playwright end-to-end test suites using the page-object model and shared fixtures for medium to large web applications.
- Implement cross-browser regression pipelines and CI integration that include trace/video capture and a11y checks to raise test coverage and release confidence.
- Expand into component integration and automated accessibility testing (axe or similar) and add measured performance checks for LCP/INP as part of test runs.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle QA Engineer
Confidence: High SDET
Mid-level E2E Test Automation engineer focused on Playwright-based UI test frameworks and page-object design. The strongest proven skill is building Playwright page objects and fixtures as shown in projects/the-internet/page-objects/file-download.page.ts and projects/the-internet/fixtures/page.fixtures.ts. There is little to no public evidence of CI workflow automation, contract/schema testing, mutation or performance testing in the analyzed human-authored files.
Test Automation Frameworks
6/10
Building automated tests
Solid Playwright-based test framework using Page Object Model, custom fixtures and selector discipline; shows practical test orchestration but no advanced platform-level architecture or custom parallelization beyond Playwright defaults.
Test Coverage & Strategy
3/10
What and how to test
Test structure includes tagged regression suites and some skipped/dynamic tests, but coverage is heavily happy-path and tutorial-style; negative-path and boundary tests are sparse.
API & Integration Testing
4/10
Testing how parts work together
API mocking is present via an explicit Postman-generated mock server that implements alternative status codes via headers, enabling negative-path and status-code testing, though no contract testing frameworks or schema validation are used.
Performance & Load Testing
Testing speed under load
Not evidenced in public code
Bug Reporting & Analysis
2/10
Finding and describing bugs
Minor evidence of bug awareness (inline BUG comment) and simulated error responses in the mock server, but no reproducible bug reports, root-cause analysis, or documented flaky-test investigations.
CI Test Integration
3/10
Running tests automatically
Basic CI-awareness in Playwright config (retries, workers, trace/video retention) but no CI workflow files, matrix configuration, or failure artifact pipelines were found.
Expertise
SDET & Test Engineering• Middle
Industries
Gaming• Middle
Technologies
QA
JavaScript
Playwright
Postman
BrowserStack
Recommendations
- Develop and own Playwright E2E suites for web applications using and extending the current POM and fixtures patterns.
- Implement API contract/schema validation and integrate the Postman mock server into automated integration tests to cover negative and edge cases.
- Add CI pipeline definitions (GitHub Actions or other) with per-branch matrices, artifact capture and per-test retry/quarantine policies.
- Introduce mutation or property-based tests and explicit negative-path tests to raise test quality and surface edge-case behavior.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: