2-4 years of professional software engineering experience with a track record of independently shipping production-quality features with full test coverage.
Strong proficiency in at least one backend language (Python, Go, or equivalent) and working knowledge of TypeScript or equivalent full-stack capability.
Solid understanding of REST API design, event-driven architectures, relational and non-relational databases, and distributed system fundamentals.
Hands-on experience with CI/CD pipelines, containerisation and orchestration (Docker, Kubernetes, or equivalent), and cloud infrastructure (AWS, GCP, or equivalent).
Proficiency with observability tooling (Datadog, Sentry, or equivalent) and the ability to own incident investigation and resolution within your technical domain.
Demonstrated use of advanced development tooling (GitHub Copilot, Cursor, or equivalent) to operate at an output level that exceeds traditional individual contribution norms.
English proficiency
Preferred Qualifications
Experience building or integrating with payment systems, marketplace infrastructure, or multi-tenant SaaS platforms.
Familiarity with API gateway patterns, webhook systems, or third-party integration design in a production environment.
Exposure to security-conscious engineering practices including input validation, secret management, and compliance-aware system design (SOC 2, PCI DSS, or equivalent).
Responsibilities
Own the full delivery lifecycle for assigned features and systems, from technical design through implementation, testing, deployment, and production monitoring.
Design and implement reliable, scalable frontend and backend services with the architectural care required to support our payment, distribution, and marketplace infrastructure.
Write and maintain comprehensive automated test suites covering unit, integration, and edge-case behaviour, treating test quality as a first-class engineering output alongside the feature itself.
Own observability within your technical domain, configuring monitoring, alerting, and logging that gives the team proactive visibility into system health rather than reactive awareness of failures.
Own incident investigation, root cause analysis, and remediation within your area of ownership, producing post-incident documentation that prevents recurrence.
Use development tooling (GitHub Copilot, Cursor, or equivalent) to compress delivery timelines and raise the quality bar simultaneously, not as a substitute for engineering judgment.
Contribute to technical design discussions, code reviews, and system improvement proposals with evidence-based reasoning, surfacing concerns early and with specificity rather than at the point of launch.
