pro
Seonghun Jo
TypeScript, Node.js & automation delivery verification
New to Contra
Seonghun is building their profile!
API and webhook integration for lightweight business systems and internal workflows.
I connect incoming requests, external APIs, structured data, spreadsheets, and notification services into clear, maintainable flows.
The focus is on reliable request handling, input validation, predictable data transformation, error visibility, and traceable outputs rather than opaque “black box” automation.
Example scopes include webhook intake, REST API calls, data synchronization, notification routing, and small integration utilities.
Scope is intentionally bounded: no unsupported production access, no credential handling outside an agreed secure process, and no claims of third-party service uptime or availability.
0
9
Playwright-based regression and acceptance verification for web applications.
I use reproducible browser tests to check whether key user flows, expected UI behavior, and previously working functionality still behave as intended after changes.
The workflow focuses on clear pass/fail evidence, reproducible test steps, regression coverage, and concise issue reporting that can be handed back to the development team.
Scope is intentionally bounded: no unsupported production access, no security warranty, and no subjective design review.
0
11
Google Sheets + Apps Script workflow automation for repetitive data and message processes.
This implemented automation pattern uses Apps Script to receive requests, update structured data in Google Sheets, call Gemini or external APIs, record status and timestamps, and send Telegram notifications.
The goal is simple: replace repetitive manual steps with a bounded, maintainable workflow that is easier to track and hand off.
Example capabilities include structured sheet updates, API processing, status/error recording, and automated notifications.
0
14
Independent acceptance verification for a bounded Node.js / TypeScript delivery.
I verify an exact submitted revision against 3–10 objective acceptance criteria and return reproducible evidence as ACCEPT, DEFICIENCY, or UNVERIFIED.
The deliverable includes an acceptance matrix, evidence locators, a deficiency list, and a clear verification summary. This is designed for milestone or handoff review before approving an outsourced software delivery.
Scope is intentionally bounded: no code fixes, production credentials, security warranty, legal interpretation, or subjective design review.
0
17