The Editor’s Connection is hiring a full-stack product engineer to own meaningful product areas from end to end from understanding a real user problem through architecture, implementation, testing, deployment, and ongoing reliability.
ENGLISH PROFICIENCY IS REQUIRED
This position is conducted entirely in English. You must be able to participate fluently in live meetings, explain technical decisions, understand detailed instructions, and communicate clearly in writing without relying on translation tools.
This is not a narrow ticket-completion role. You will have a strong voice in the product, make decisions across the stack, and see your work directly improve how customers, managers, and more than 100 editors operate every day.
Before applying, please read our candidate brief:
https://careers.theeditorsconnection.com
TECHNICAL REQUIREMENTS — MODERN WEB DEVELOPMENT
This is specifically a production full-stack web-development position. Please apply only if you already have substantial hands-on experience building and operating modern web applications.
You should already have production experience with:
- TypeScript and JavaScript across both browser and server environments, including asynchronous behavior, typed interfaces, error handling, and maintainable application structure.
- React application development: component architecture, state and data flow, routing, forms, responsive interfaces, reusable UI systems, and complex customer-facing workflows.
- Node.js backend development with Express or a closely related HTTP framework, including REST APIs, validation, dependency boundaries, service layers, and external integrations.
- PostgreSQL and SQL: relational modeling, joins, constraints, indexes, transactions, connection pooling, query performance, data integrity, and safe, backward-compatible schema migrations. We use Knex for queries and migrations.
- Git-based team development: branches, focused commits, merge requests, code review, conflict resolution, and understanding the exact files and behavior changed before merge. We use GitLab and CI/CD pipelines.
- Regression prevention and testing: establishing coverage for critical existing behavior, writing unit and integration tests, validating affected workflows, and using development, staging, and production environments responsibly. Our current tools include Vitest and React Testing Library.
- Production deployment and recovery: environment variables, secret handling, build pipelines, Docker, staged verification, database migrations, rollback or roll-forward decisions, and post-deployment checks.
- Reliable asynchronous systems: webhooks, background workers, callbacks, retries, timeouts, idempotency, concurrency, duplicate events, partial failures, and preventing runaway CPU, memory, or request loops.
- Web security fundamentals: server-side authorization, RBAC, sessions and tokens, OAuth/OIDC concepts, CORS, CSRF, untrusted input, tenant isolation, and keeping secrets out of Git and browser code.
- Object storage and file workflows: S3-compatible storage, presigned URLs, multipart uploads, lifecycle and cleanup concerns, and integrations with external file providers. We use the AWS SDK, Uppy, Google Drive, and Frame.io.
- Realtime and caching systems: WebSockets/Socket.IO, Redis, cache invalidation, and database-driven realtime updates.
- Observability and production diagnosis: structured logs, browser monitoring, traces, metrics, request correlation, and using evidence to identify a root cause. We use Datadog RUM, logs, APM, and metrics.
- Multi-organization web architecture and domain management: custom domains and subdomains, host-based routing, organization-scoped branding and data, frontend domain-management surfaces, and strict prevention of cross-organization leakage.
- AI-assisted engineering and MCP tools for implementation, review, documentation, and investigation. Our workflow includes AI coding assistants, CodeRabbit, and custom read-only Datadog and PostgreSQL MCP tools. You must still understand and own the architecture and behavior of the resulting work.
Our active product stack centers on React 19, TypeScript, Vite, React Router, Tailwind CSS, Radix UI, Node.js 24, Express, Inversify, PostgreSQL, Knex, Redis, Socket.IO, S3-compatible object storage, Docker, DigitalOcean App Platform, GitLab CI/CD, and Datadog. You must have strong production experience across the major layers and be ready to contribute immediately in TypeScript, React, Node.js, and PostgreSQL.
WHAT YOU WILL DO
- Own a product domain across product thinking, frontend, backend, databases, integrations, deployment, and production support.
- Work directly with the people using the software to understand the real problem before building.
- Design changes that add value without damaging existing workflows, customer data, or system reliability.
- Establish regression coverage before changing critical shared behavior, then test the new behavior and affected workflows.
- Keep changes understandable and reviewable, with a clear explanation of scope, risk, testing, deployment, and recovery.
- Investigate failures, communicate uncertainty early, and improve the system after incidents or near misses.
- Debate ideas constructively, recognize stronger reasoning, and help combine perspectives into a better solution.
WHAT WE CARE ABOUT
We care far more about what you have personally built and operated than prestigious company names, formal titles, or algorithm trivia.
You may be a strong fit if:
- You have personally built or changed production software that real customers, revenue, or business operations depended on.
- You can communicate fluently in English during daily remote collaboration.
- You can explain what you personally owned not only what “the team” built.
- You understand that shipping a feature is not risk-free and can reason about regressions, data integrity, backward-compatible changes, rollback, and recovery.
- You can tell detailed, honest stories about releases, incidents, tradeoffs, mistakes, and what changed afterward.
- You learn unfamiliar technical territory quickly without pretending to understand what you have not yet verified.
- You care more about reaching the best answer than proving your first answer was right.
THE PAID ONE-MONTH TRIAL
The role begins with a paid one-month contract trial. You will work on a meaningful, complex product problem in a controlled environment so we can evaluate how you understand ambiguity, simplify systems, use tests, protect existing behavior, communicate risk, and respond to feedback.
The trial is a genuine working period for both sides to evaluate long-term fit. Strong performance may lead to an ongoing role with ownership of a product domain.
LOCATION
This is a fully remote opportunity intended for candidates based in Latin America. The position requires reliable availability for agreed collaboration hours and fluent spoken English.
HOW TO APPLY
Read the candidate brief before answering the application questions:
https://careers.theeditorsconnection.com
We will ask you to reflect on how our working model fits you and to describe real production work you personally owned. Specific, honest answers matter more than polished corporate language.
Job Type: Full-time
Pay: $27,000.00 per month
Application Question(s):
- Describe one production system you personally helped build or substantially improve that real customers, revenue, or business operations depended on. What did it do, what did you personally own, and what would have happened if it failed?
- Tell us about a production incident, serious regression, or near miss you personally encountered. How was it discovered, what was your responsibility, how was service restored, and what changed afterward?
- Walk us through one feature you personally owned from the user interface through the backend and database. What technologies did you use, what important architectural decisions did you make, and how did you safely release it?
- After reading our candidate brief at careers.theeditorsconnection.com, identify one specific idea that explains why our company could be a good fit for you. Then explain what evidence from your past work suggests you would be a good fit for us.
- If possible provide a link to something you have built or substantially owned, if available. This may be a live product, repository, portfolio, demonstration, or anonymized walkthrough. Briefly explain what we should examine and what you personally contributed.
Language:
Work Location: Remote
