About 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. 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 Bug investigation and triage 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 Automated workflow monitoring 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