Developer Terminal

Batraz Sekinaev / interactive mode

Try help, whoami, projects, stack, contact, lab, clear, exit.

Simulation. No system commands are executed and nothing is sent to a server.

GitHub, opens in a new tabContact
← All projects

TEAM EXPERIENCE / INTEGRATIONS

Pobeda Digital / EGO

Working on integrations in an existing backend

During an internship I worked on a B2B review and reputation platform. I handled separate project tasks after the official internship ended; that period is not represented as continued employment.

Dates
25 June — 25 September 2026
Status
Internship completed
Context
B2B / Integrations

01 / CONTEXT

Why this differs from a personal project

The work meant understanding an existing architecture, preserving compatibility, dealing with external platforms and validating changes through tests.

02 / WORK

Areas of work

01

Otzovik — review integration

A platform without a suitable public API for the required workflows.

  • Authenticated Playwright browser session and data retrieval.
  • Normalization, repeat reads without duplicate records and integration into existing workflows.
  • Focused checks for review retrieval and reply submission.

No employer source code, sessions, credentials or private APIs are shared.

02

MAX — comments and publications

Changes to existing integration modes and event handlers.

  • Updates to comments, webhook processing and inline interactions.
  • MiniApp/Native compatibility and duplicate-event handling.
  • Regression and targeted behavior checks.

This describes completed tasks, not a full platform release.

03

Universal Reviews Connector — research

Exploring integration patterns for platforms with restricted or incomplete APIs.

  • Separating discovery, connector description and deterministic runtime.
  • Confirmed Ozon Seller read-only list/detail path with UUID correlation.
  • Recorded antibot restrictions and incomplete end-to-end acceptance.

No claim of production-ready Ozon integration or fully accepted POC.

03 / PRACTICE

Engineering practices

  • Git branches, pull requests and legacy code changes.
  • Python, HTTP, webhooks, Playwright and integration adapters.
  • Unit, contract, regression and focused real-platform checks.
  • Event deduplication, database migrations and diagnosing failures.

04 / BOUNDARIES

Intentionally excluded

  • Private employer code, tokens, accounts, reviews and customer data.
  • Unverified business metrics or full-release claims.
  • Work after 25 September is not described as extended employment.

05 / TAKEAWAY

What I learned

Changing an existing system means understanding its users, constraints and previous decisions. Keeping established behavior working matters as much as writing new features.

Discuss a similar task ↗All projects