I’m a Senior Software Development Engineer in Test / Test Automation Engineer focused on building reliable quality-engineering systems rather than simply automating individual test cases.

My background spans federal, banking, e-commerce, and enterprise software, with experience as both an individual contributor and technical lead.

I specialize in:

• 🧪 Test automation architecture
• 🎭 Playwright, Cypress, and Selenium
• 🔌 UI and API automation
• 🚀 CI/CD quality engineering
• 🌐 Cross-browser and responsive validation
• 🔐 Authentication and secure application testing
• ☁️ Cloud-based test execution
• 📊 Reporting, observability, and quality metrics
• 👥 Technical leadership and mentoring
• ⚡ Performance, maintainability, and execution optimization

My goal is not simply to make tests pass.

I build quality-engineering systems that make software easier to ship with confidence.

Requirements
     │
     ▼
Quality Strategy
     │
     ├── UI Automation
     ├── API Testing
     ├── Cross-Browser Validation
     ├── Authentication Testing
     ├── Test Data Management
     └── Performance Validation
     │
     ▼
Automation Framework
     │
     ▼
CI/CD Quality Gates
     │
     ▼
Fast Feedback + Actionable Reporting
     │
     ▼
Production Confidence

I approach quality as an engineering discipline integrated into the software delivery lifecycle, not as a separate testing phase.

E2E Testing · UI Automation · API Automation · Regression · Smoke Testing · BDD · Visual Testing · Cross-Browser · Performance Testing · Risk-Based Testing

I have designed and maintained automation frameworks using:

• Playwright for modern end-to-end UI and API automation
• Cypress for JavaScript/TypeScript-based application testing
• Selenium WebDriver for mature enterprise and cross-browser automation
• Cucumber / Gherkin for behavior-driven workflows
• TestNG / JUnit / Mocha / Jest / Chai
• Page Object Model and reusable framework abstractions
• Data-driven and hybrid automation approaches
• Parallel execution and retry strategies
• Network mocking and API stubbing
• Dynamic test-data generation
• Trace, screenshot, video, and artifact collection

I have worked on automation architectures that reduced overall execution time by more than 70% through framework optimization, parallelization, and improved test design.

I integrate automated validation directly into delivery pipelines so quality is part of the engineering process rather than a separate phase.

Commit
  ↓
Static Validation
  ↓
Build
  ↓
Smoke Tests
  ↓
API + UI Automation
  ↓
Parallel / Cross-Browser Execution
  ↓
Artifacts + Reporting
  ↓
Quality Gate
  ↓
Deployment

Experience includes:

• GitHub Actions
• Jenkins
• Azure DevOps
• Bamboo
• Bitbucket
• AWS-based test infrastructure
• Automated artifacts
• Parallel execution
• Retry strategies
• Environment-specific pipelines
• Automated reporting and quality gates

Java · TypeScript · JavaScript · SQL
Maven · Git · REST · JSON
Jira · Allure · ELK · Datadog

A significant part of my experience involves applications where authentication cannot simply be bypassed for automation.

I have worked with:

• OIDC
• Okta MFA
• Microsoft identity platforms
• Enterprise SSO
• Secure session handling
• Authentication-token validation
• Role-based access
• Restricted enterprise environments

This requires automation architecture that respects the real security model instead of creating unrealistic test-only shortcuts.

QA Test Engineer · 2020 — Present

• Led an automation team of 6 engineers
• Designed Cypress and Playwright automation frameworks
• Automated UI and API regression coverage
• Integrated automated testing with GitHub Actions
• Implemented parallel execution and artifact management
• Built AWS-backed testing workflows using EC2, Aurora DB, and S3
• Developed dynamic test-data provisioning
• Implemented test analytics and reporting
• Supported Selenium Grid and performance testing
• Mentored engineers in advanced automation practices

Software Engineer in Test · 2018 — 2020

• Architected Cypress-based automation
• Developed UI and API regression coverage
• Integrated Cypress into CI/CD
• Implemented Applitools visual validation
• Automated OIDC and Okta MFA workflows
• Used AWS for scalable testing infrastructure
• Applied network stubbing and parallel execution
• Reduced execution time by approximately 40%

Software QA Engineer · 2015 — 2018

My earlier QA foundation included:

• Functional testing
• Exploratory testing
• Regression testing
• Requirements analysis
• Test planning
• Acceptance criteria
• Cross-browser validation
• Responsive testing
• Defect lifecycle management
• Root-cause analysis
• Deployment validation

That manual-testing foundation still influences how I design automation today:

Automation is strongest when it is built on solid testing judgment.

I’m currently building my portfolio as an engineering project rather than a static résumé site.

Astro 7.2
├── Strict TypeScript
├── Semantic HTML
├── Native Modern CSS
├── OKLCH Design Tokens
├── Astro Content Collections
├── Minimal Client JavaScript
├── Native Browser APIs
└── GitHub Pages

The engineering principle behind the project is simple:

Maximum capability with minimum unnecessary complexity.

That means using browser and platform capabilities first, adding dependencies only when they solve a real engineering problem.

Pull Request
     │
     ├── Astro Validation
     ├── TypeScript
     ├── Formatting / Linting
     ├── Build
     │
     ├── Playwright
     │     ├── E2E
     │     ├── Cross-browser
     │     └── Failure artifacts
     │
     ├── Cypress
     │     └── Complementary regression
     │
     ├── Accessibility
     ├── Performance
     ├── Link Validation
     │
     ▼
   Deploy

🌐 Explore the portfolio:
https://mohamedmoheyeldin.github.io

I’m exploring how AI can improve real engineering workflows without replacing sound engineering judgment.

Current areas of interest include:

• AI-assisted software development
• AI-assisted test development
• Code analysis and refactoring
• Developer workflow automation
• Local LLM experimentation
• Hardware-aware local AI
• AI-assisted repository maintenance
• ChatGPT / Codex engineering workflows

I prefer evidence-based AI usage over simply adding “AI” to a technology list.

🎓 Bachelor’s Degree — Computer Science
American College of Commerce and Technology

• 🥒 Cucumber BDD Automation Framework
• 🔄 Implementing SAFe 5.1
• 🧭 Leading SAFe 4.0

Building      → Personal Engineering Platform
Improving     → Playwright & Cypress architecture
Exploring     → AI-assisted engineering workflows
Designing     → Modern native CSS systems
Automating    → CI/CD quality gates
Learning      → Local AI and developer tooling

I’m interested in conversations around:

SDET · Quality Engineering · Test Automation · CI/CD · Playwright · Cypress · Selenium · Software Engineering · Developer Tooling · AI-Assisted Engineering