Python / Database Engineer - FT - NA/LATAM

Summary

Client is a data protocol for the entertainment industry. We're seeking an experienced Python and database engineer to help build the technical foundation of our media data platform.

S3C is evolving from a set of capable, single-purpose tools into a layered architecture built around shared domain packages, a service API, workflow automation, and a centralized PostgreSQL database.

This is a hands-on implementation role focused on new, well-scoped components and controlled extraction of functionality from our existing application — not general legacy maintenance. You'll work closely with the CTO, who owns architecture and domain decisions, while you own implementation of clearly scoped deliverables.

What You'll Work On

• Extract core functionality — including metadata/tag I/O, publishing, and annotation logic — into standalone - Python packages with clean, typed boundaries and no UI dependencies.
• Design and implement PostgreSQL data structures supporting metadata history, rights holders, licensing, consent, usage events, and audit/change history.
• Build validation and data-quality logic that detects incorrect, incomplete, or contradictory data and anomalies.
• Develop reusable Python and database components that can support a service API, CLI, and other application interfaces.
• Establish development infrastructure: source control, CI, automated testing, separated development environments, and reproducible/sample test data — so new functionality can be built and tested without access to client data.
• Write maintainable, well-tested, documented code, and surface technical risks, ambiguities, and implementation decisions to the CTO before they become blockers.
• As familiarity grows, help decompose additional legacy functionality in an agreed priority order, and support tactical clarification of data or access issues (while larger client commitments and architectural calls remain with the CTO).

Initial Priorities

• Early work is expected to focus on establishing the engineering foundation for additional contributors to build on:
  *Source control and automated testing
  *A practice environment with representative sample data
  *A separated development environment
  *Shared Python and database components supporting the emerging platform
  *Data structures and validation logic supporting STR3AMCORE's catalog-cleaning and rights-management workflows

This initial work is deliberately self-contained and, where possible, doesn't require access to sensitive client data.

What We're Looking For

• Strong production Python experience, including package/module design, typed interfaces, and reusable components.
• Strong relational database experience: schema design, migrations, SQL, data integrity, and designing for future requirements.
• Experience designing clean boundaries between domain logic, persistence, APIs, and application interfaces.
• Strong testing discipline and experience with automated testing and CI.
• Ability to work independently from written specifications, and to raise problems with a spec rather than coding around it.
• Comfortable in an early-stage environment where some future requirements are still being defined.
• Strong written communication and sound technical judgment.

Nice to Have

• PostgreSQL, SQLAlchemy, Alembic, and FastAPI experience.
• Experience with ffmpeg, media metadata/tag libraries, or media containers.
• Rust experience or interest in selective Rust adoption.
• Experience with self-hosted developer infrastructure (Forgejo, Gitea, GitLab).
• Experience with rights, licensing, royalties, consent, provenance, or audit data models.
• Experience with high-volume media or metadata processing.
• Experience building data-quality rules or automated detection of anomalous/incorrect data.

Engagement Details

• Type: Contract
• Location: Remote; U.S.-based preferred
• Schedule: Significant working-hour overlap with Pacific Time (PST/PDT) required
• Working model: CTO sets architecture, technical boundaries, and domain requirements; contractor owns implementation of agreed deliverables
• Scope: Primarily new, self-contained development and controlled extraction — not general legacy maintenance
• Hours / Duration: TBD based on experience, availability, project scope, and proposed rate
• Reporting: Works directly with the CTO

Strong Candidates

The strongest candidate is more than a capable Python developer — someone who understands that module boundaries, database design, and interface decisions get harder to change as systems scale, and who enjoys building infrastructure other engineers depend on.

You should be comfortable taking a clear spec and boundary, independently turning it into well-structured, tested software, and raising architectural or data-model concerns before they become problems. This is a foundation-building role, not feature-polish or legacy maintenance.