MD

Morakinyo Dada

Quality Assurance Tester · Aviation → Software

Software Quality Assurance Analyst · Backed by 15+ years in aviation safety

I apply the same discipline from aviation safety to ensuring software quality.

I am a Quality Assurance Analyst specializing in manual and exploratory testing, API validation, and SQL-based data verification for high-risk workflows such as authentication, payments, and booking systems. I execute and manage structured test cases in qTest, maintaining requirement traceability and supporting controlled, high-quality releases.

Based in Moncton, NB Open to Software Application testing / QA analyst roles
▶ View QA projects View GitHub QA portfolio

Previously: Senior Flight Attendant, Cabin Crew Supervisor, and Inflight Manager delivering safety, compliance, and calm under pressure.

About Me

Profile

I am an early-career Quality Assurance professional with over 15 years of experience in customer service and operational leadership within safety-critical aviation and service-driven environments. My career has been shaped by roles requiring precision, accountability, structured procedures, and strict adherence to regulatory standards.

Before transitioning into software quality assurance, I served as a Senior Flight Attendant, Cabin Crew Supervisor, and Inflight Manager, leading teams, enforcing compliance, managing incidents, and operating effectively in high-pressure, time-sensitive situations. Those experiences strengthened my attention to detail, process discipline, and decision-making under pressure.

My transition into QA was intentional and skills-driven. I have built hands-on experience in functional testing, structured test case design, defect lifecycle management, API validation, and SQL-based data verification. I approach every release cycle with discipline, traceability, and risk awareness, combining operational leadership with systems-focused quality thinking.

What I bring into QA from aviation:
  • Discipline around checklists, procedures, and safety standards.
  • Clear, concise communication during incidents and escalations.
  • Experience documenting issues so others can act on them quickly.
  • Empathy for users whose experience is affected by defects.
Transitioning from aviation safety into software QA
Strong in structure, documentation, and incident handling

Professional Experience

Aviation · Leadership
Senior Flight Attendant · Cabin Crew Supervisor · Inflight Manager
Safety‑critical operations · Incident management · Team leadership

Led cabin teams in safety‑critical environments, ensuring regulatory compliance, procedural accuracy, and consistent service quality. Responsibilities included documentation, risk assessment, incident handling, coaching, and clear communication under pressure.

  • Enforced checklists and safety protocols on every flight, with no tolerance for skipped steps.
  • Documented incidents with clear timelines, actions taken, and recommendations-skills now applied to bug reporting.
  • Coordinated with pilots, dispatch, and ground teams, mirroring cross‑functional work with developers, product owners, and support in QA.
Safety mindset High‑stakes communication Team leadership Incident documentation

Quality Assurance Skills

Testing Stack

My QA approach focuses on understanding requirements deeply, designing clear test cases, validating behavior across layers, and documenting defects in a way that supports developers and improves product quality.

  • Manual and exploratory testing across complex web workflows.
  • Structured test planning and test case execution using qTest with requirement traceability.
  • Defect lifecycle management in Jira with clear reproduction steps and impact analysis.
  • API validation using Postman (status codes, payload inspection, error handling, response verification).
  • SQL queries for backend data validation and login/session checks.
  • Foundational understanding of Selenium automation for UI regression support.
  • Regression and smoke testing to support controlled release cycles.
  • Jira, GitHub, and structured documentation practices.
Tools & Focus Areas
  • Test design techniques: positive, negative, edge cases, boundary value analysis.
  • Postman: collections, environments, response validation, and API troubleshooting.
  • SQL: SELECT queries to verify database integrity and state transitions.
  • Selenium (intro level): element locators, basic automation flows, and regression support.
  • qTest: test case management, execution cycles, and coverage tracking.
  • Jira: defect tracking, workflow management, and release alignment.
Manual & exploratory testing API validation with Postman SQL‑based verification Clear, structured defect reporting

QA Projects

Portfolio
Hands‑on QA lifecycle
Featured project

Manual QA Portfolio

A structured QA portfolio demonstrating disciplined execution across the full QA lifecycle, from requirement analysis and test planning to defect management and regression validation.

  • Comprehensive test plans defining scope, risk areas, objectives, and release criteria.
  • Structured manual test cases with traceable coverage of core flows, edge cases, and boundary conditions.
  • Defect reports documented with severity, priority, impact analysis, and reproducible steps.
  • API validation scenarios and SQL-based backend verification to ensure cross-layer consistency.
  • Regression and smoke test artifacts aligned with controlled release workflows.

Hosted on GitHub with structured documentation and enterprise-style QA artifacts.

View QA Portfolio on GitHub →

Visualizing how I think about login testing:
Valid email + valid password Successful authentication and correct session initialization.
Valid email + wrong password Clear error handling without premature account lockout.
Locked / disabled account Accurate status messaging and access restriction.
Post-login validation Database session record and last_login timestamp verified.

Login Functionality – QA Case Study

Deep Dive

This case study is based on an academic QA project designed to simulate real‑world testing practices. The focus was on validating login functionality—a high‑risk feature responsible for access control and security.

Scope and Approach

  • UI validation and error handling for all states.
  • Positive and negative test scenarios, including edge cases.
  • API response validation (status codes, payloads, error messages).
  • Backend data verification using SQL to confirm login events.

The project strengthened my understanding of end‑to‑end QA workflows and reinforced the importance of thorough testing, clear documentation, and backend validation.

👉 View related QA artifacts on GitHub

Contact

Let’s Talk

I’m open to early‑career QA roles and opportunities where attention to detail, clear communication, and quality‑focused thinking are valued.

Phone +1 (506) 536-7700
Email peter.akindada@gmail.com
GitHub github.com/MorakinyoDada
How I like to work with teams
  • I ask clarifying questions before testing to avoid assumptions.
  • I prefer defects with clear steps, context, and impact rather than vague messages.
  • I see QA as a partner to development, not a gatekeeper.