Intern QA Engineer
AI in this role
About the company
Tabby builds financial products used by millions of users across the GCC. We work on high-load, security-critical systems with strict regulatory requirements.This is not a course and not a shadowing programme. It is an engineering role with real responsibility.
Context
The Process Engineering team sits in Risk and Credit, and it builds and runs the automated business workflows Tabby operates on. The team configures those workflows on an internal automation platform and runs them in production.This role exists to keep that automation reliable: testing changes before they go live, catching failures early and investigating what went wrong when something breaks. Designing the automation belongs to the engineers who build it. This internship is about validating, monitoring, debugging and reporting.
It suits a recent graduate with a sharp eye for detail, stubborn curiosity about why something broke and enough technical comfort to read a script or call an endpoint without being intimidated by it.
Key Responsibilities
This is not a helper or shadow-only role. Interns work on real production tasks under senior review.
Release validation and regression testing
- Run smoke and regression passes before workflow and system releases go live
- Verify that bug fixes and configuration changes behave as expected across the affected processes
- Maintain the release sign-off checklists and flag anything that is not ready to ship
- Track what was tested, what passed and what is still open, so release decisions are made with full visibility
- Reproduce reported issues, isolate the conditions that trigger them and narrow down where in the workflow they originate
- Inspect API requests and responses to find where a call fails: a bad payload, an unexpected response, a broken integration or a downstream error
- Read application logs, execution traces and error messages to gather evidence before escalating
- Write reproducible bug reports: steps, expected and actual behaviour, environment, severity and supporting evidence
- Triage incoming reports from business teams, filter out noise and duplicates and route real problems to the right owner
- Watch the health of the running automations and integrations, and spot failures before users report them
- Investigate failed or stuck runs and work out whether the cause is configuration, a failing integration or a system defect
- Perform safe re-runs and recovery steps for known failure patterns under guidance
- Track recurring failures over time and surface the patterns worth fixing properly
Test cases and documentation
- Execute, review and update existing test cases as the workflows evolve
- Keep test data, environment notes and process documentation current
- Identify gaps in coverage and propose test cases for the scenarios that keep slipping through
- Contribute to a shared knowledge base of known issues, workarounds and debugging playbooks
Working across teams
- Work with business stakeholders, system analysts, product managers and engineers to confirm expected behaviour and validate fixes
- Communicate testing status and blockers early, in language both technical and non-technical people can act on
- Support end users through the rollout of workflow changes by verifying real-world scenarios
Skills, Knowledge & Expertise
Required
- Recent graduate in computer science, engineering, information systems or a related field
- Working understanding of APIs: what a REST request and response look like, how status codes and JSON payloads work and how to send a call with a tool like Postman
- Basic scripting in Python or JavaScript, enough to read an existing automation script, understand what it does and make small adjustments
- Strong analytical instincts and the patience to reproduce an issue methodically rather than guess at it
- Attention to detail and a structured, documentation-friendly way of working
- Clear written English. A bug report is only useful if someone else can follow it
- Willingness to learn quickly, ask questions and own a small piece of work end to end
Strong plus
- QA fundamentals: test cases, regression testing, the bug lifecycle, severity and priority
- Hands-on API testing: Postman collections, environment variables, chained requests or basic API test automation
- Familiarity with webhooks, authentication flows such as API keys and OAuth, or reading API documentation
- Exposure to workflow automation or low-code platforms such as Power Automate, Camunda, Zapier or n8n
- Experience with issue trackers such as Jira or Linear, or with test management tools
- Interest in fintech, payments or high-volume transactional systems
- Any academic project, internship or personal work involving testing, debugging or integration
Eligibility
- Saudi nationals only
- This position is aimed at fresh graduates
- We expect a full-time level of engagement. The programme is not part-time. Performance, ownership and involvement are expected at a full-time level
How we rate this
Intern QA Engineer at Tabby rates 51 out of 100 for how much of the daily work is AI. That makes it Uses AI (AI Level 2 of 4). The level is about AI in the job, not seniority.
Uses AI. An ordinary role that requires AI tools.
- ●●●● Builds AI80 to 100
- ●●●○ Works on AI60 to 79
- ●●○○ Uses AI40 to 59
- ●○○○ Little AI0 to 39
Levels come from how often the tools, models and workflows of the role are named in the posting itself. Open the description and count.
Prepare for this job
A free preview built only from this posting: what it asks for, what you could be asked in an interview, and how to adjust your resume.
Skills and AI tools this role asks for
Questions you could be asked
- What's a project where you used Zapier AI hands-on?
- Walk me through how you've used N8n in your day-to-day work.
- This role expects you to use AI tools as part of the job. Which ones have you used, and for what?
- Tell me about a time an AI tool got something wrong. How did you catch it?
Adapt your resume
- List these exact terms on your resume: Zapier AI and N8n. An applicant tracking system matches the wording, not the idea.
- Attach one line of real, concrete experience to at least one of them — a tool named with nothing behind it rarely survives a human read.
- Put the AI tool in a bullet point about what you did, not just in a skills list — this role treats it as a required part of the job.
Want an expert to read your CV for this job?
Free. Send your CV and the role you want next. We reply by email within 2 to 4 business days.
Get a free CV reviewGet new AI jobs (Uses AI ●●○○ or higher) by email
One email a week with the new AI jobs (Uses AI ●●○○ or higher), each rated for how much AI is in the work. No recruiter spam, unsubscribe in one click.
Free. One email a week. Unsubscribe in one click.
Similar roles
Software Engineering roles that use AI, at other companies.
What kind of AI work fits you?
Answer 12 practical questions in about three minutes. Get a simple profile, the work it points to, and live roles to explore next.
Find my next step