On behalf of FinTech Client #4, SD Solutions is looking for a talented QA Specialist.
SD Solutions is a staffing company operating globally. Contact us to get more details about the benefits we offer.
Responsibilities:
- Design, document, and execute test scenarios across the many valid combinations of product type, order type, and country/region, as well as exception and failure-path states.
- Trace applications end-to-end across system boundaries — from initial submission, through signing, CRM handoff, review, to final provisioning.
- Validate API-level behavior at each integration boundary: webhook payloads, outbound API calls to partner/boarding services, and order-creation calls — checking request/response shape, data truncation, and error handling.
- Read and interpret application logs/observability tooling (e.g., Datadog or equivalent) as the primary investigation tool: trace background job execution, webhook receipt/filtering, and job failures across known points where a process can silently stall.
- Participate in test design from the feature/design phase — flag when a change spans multiple layers (database, backend logic, UI, generated documents), since inconsistency across layers is a common source of defects.
- Build and maintain regression coverage for known gaps (e.g., feature-flag-gated configurations, missing combinations) and for phases of the lifecycle with limited existing test coverage.
Requirements:
- 2–3 years manual testing experience on complex, business-critical, multi-system applications — a must. This platform handles financial onboarding, legal document generation, and account setup — low tolerance for regressions.
- Strong API testing experience (Postman or equivalent) — a must for this role. Day-to-day work involves validating webhook payloads, signed integration calls, and understanding the difference between real-time API calls and asynchronous/batch data-sync mechanisms between systems.
- Strong log-reading / observability experience (e.g. Datadog or equivalent APM) — a must for this role, prioritized over SQL/database skills. Most triage starts in the logging/observability platform: tracing a process by its reference ID, distinguishing "never arrived" from "arrived but was filtered" from "arrived but failed downstream."
- UI testing experience, with a focus on document fulfillment — a must. A core part of this product generates legal/contractual documents from user-entered data, so testing must go beyond the input screens:
- Input-to-document consistency testing. The on-screen wizard is data entry; a separate generated document (e.g., a PDF built from a template) is produced from that data afterward. A field can look correct on screen but render blank or incorrect in the generated document if template logic doesn't match — testing must compare screen input against actual document output, not just the UI itself.
- Conditional UI verification. Confirm the frontend shows/hides fields, steps, and options consistently with backend business rules (which vary by product type, order type, and country) — no orphaned or missing fields depending on the configuration.
- Document upload/fulfillment step testing, especially for document-driven flows where required paperwork substitutes for automated data entry — correct upload slots, required-vs-optional enforcement, file-type/size validation.
- E-signature surface testing, as far as testable — UI correctly reflects signing status back to the user even where full end-to-end signing is bypassed or restricted in test environments.
- Multi-step save/resume behavior — applications can be saved and resumed mid-flow; test partial completion and progress tracking as a distinct source of data-loss bugs.
- Ability to diagnose which layer (database, backend, UI, or generated document) actually owns a given defect, since the fix differs depending on where the inconsistency originates.
- Working SQL literacy is a plus (occasional direct database lookups for investigation) but is not the primary investigative skill for this role — log tracing and API inspection are.
- Comfortable with asynchronous, event-driven architectures — this system relies on webhooks, pub/sub-style notifications between systems, and background job queues. Testing here means reasoning about timing, retries, and silent failures, not just synchronous request/response.
- Experience working in Agile methodology — advantageous.
- Solid understanding of the SDLC and a strong business-process orientation — this role requires connecting a UI field to its legal/contractual consequence and its downstream system consequence.
- Proactive, ownership-driven, comfortable taking a defect from symptom to root cause across systems you don't own end-to-end.
- Solid grounding in industry-standard testing methods (exploratory, integration, regression) and the judgment to prioritize test coverage by risk rather than exhaustive combinatorial testing.
- Ability to work independently through ambiguity but flag gaps rather than guess — this system has known areas of internal documentation/behavior mismatch that should be verified directly rather than assumed.
About the company:
A global fintech company providing unified payment infrastructure and financial services for merchants and consumers worldwide. The platform integrates multiple payment channels into a single solution, combining in-house technology development and product innovation to streamline transactions at scale.
By applying for this position, you agree to the terms outlined in our Privacy Policy. Please take a moment to review our Privacy Policy https://sd-solutions.breezy.hr/privacy-notice, and make sure you understand its contents. If you have any questions or concerns regarding our Privacy Policy, please feel free to contact us.
Skills Required
- 2-3 years manual testing experience on complex, business-critical, multi-system applications
- Strong API testing experience (Postman or equivalent)
- Strong log-reading / observability experience (Datadog or equivalent APM)
- UI testing experience focused on document fulfillment, input-to-document consistency, conditional UI, uploads, e-signature, and save/resume flows
- Ability to diagnose which layer (database, backend, UI, or generated document) owns a defect
- Comfortable testing asynchronous, event-driven architectures (webhooks, pub/sub, background job queues)
- Solid understanding of the SDLC and strong business-process orientation
- Proactive, ownership-driven approach; able to take a defect from symptom to root cause across systems
- Solid grounding in industry-standard testing methods (exploratory, integration, regression) and risk-based prioritization
- Working SQL literacy for occasional direct database lookups
- Experience working in Agile methodology






