# Content Creator JuniorPosted August 13, ****Apply Now Takes a few minutes · No account required## About this roleBuscamos un Content Creator Junior para sumarse a nuestro equipo de marketing digital en Argentina.
Vas a crear contenido que ayude a nuestros clientes a conectar con sus audiencias, aprendiendo el ofic, its performance characteristics, and its failure behavior.Architect for peak.
Model expected RPS and concurrency for the holiday season, size and shape systems against it, and validate through load and stress testing well ahead of November — while keeping the off-season footprint efficient.Own the data layer as it evolves.
Make deliberate choices between relational and non‐relational stores, design schemas and access patterns that scale, and evolve them safely as features grow.Build and scale asynchronous infrastructure.
Message queues, event and bus architectures, and the decoupling that lets the platform shed load gracefully instead of failing loudly.Deepen our analytics platform.
Work with our OLAP/warehouse layer (Amazon Redshift) so product, growth, and marketing get reliable data as the underlying models change.Deploy and operate services in AWS from scratch — provisioning, networking, infrastructure as code, CI/CD, and the operational scaffolding that comes with a service being real.Make the system observable.
Meaningful metrics, structured logs, traces, SLOs, and alerts that fire on user visible problems rather than on noise.Take end‐to‐end ownership.
From design through development, rollout, on‐call, incident response, postmortems, and the unglamorous maintenance that makes operational excellence real rather than aspirational.Write things down.
Design docs, architecture decision records, runbooks, and API documentation that let a smallteam move fast without holding the system in one person's head.What We're Looking ForBackend engineering depthSubstantial experience building backend services and scalable APIs in C#/.




NET — or comparable depth in another backend ecosystem with a genuine willingness to work in ours.A track record of services that stayed up and stayed fast as traffic and feature scope grew.Data and messagingIn‐depth working knowledge of relational databases: modeling, indexing, query performance, migrations under load, replication and read scaling.Practical experience with non‐relational stores, and clear judgment about when they are the right tool.Real experience with message queues and bus/event‐driven architectures — delivery semantics, idempotency, ordering, retries, dead‐letter handling, and backpressure.Hands‐on experience with an OLAP/warehouse layer; Amazon Redshift specifically is a strong plus — including how to evolve it as upstream models change without breaking downstream consumers.Scalability, resiliency, and observabilityFluency with scalability principles: caching strategies, connection and resource pooling, horizontal scaling, partitioning, and the trade‐offs between them.Resiliency as a design habit — timeouts, retries with backoff, circuit breakers, graceful degradation, and blast‐ radius containment.Observability treated as a first‐class deliverable, not something bolted on during an incident.Cloud and operationsMeaningful AWS experience, including standing up and deploying services from scratch rather than inheriting them.Comfort owning production: on‐call participation, incident response, and driving durable fixes out of postmortems.How you workYou believe in documentation and produce it as part of the work, not after being asked.You take end‐to‐end ownership — a feature is yours through maintenance, not through merge.You design with peak traffic and RPS in mind by default, so systems hold during the holiday surge and stay economical the rest of the year.You collaborate well on a small team where backend, frontend,



and QA sit close together and everyone's decisions are visible.Nice to HaveExperience with consumer platforms that have pronounced seasonal or event‐driven traffic spikes.Load and stress testing practice — building the harness, not just reading the report.Cost‐aware architecture: right‐sizing, autoscaling policy, and reserved/spot strategy in AWS.Experience with high‐volume transactional messaging or notification infrastructure (email, push).
Security‐conscious design and familiarity with the operational sUSA y Europa, somos tan fuertes como los equipos y valores en el corazón de nuestro negocio.Para ofrecer constantemente soluciones de la más alta calidad a nuestros clientes, solo contratamos al 1% de las mejores personas y fomentamos su crecimiento profesional, personal y espiritual en proyectos desafiantes que inspiran superación y crecimiento.
## Preguntas frecuentes### ¿Cuánto gana un Content Creator Junior Junior en Argentina?
En Argentina, un Content Creator Junior Junior gana en el mercado entre $ 650 y $ 900 por mes.
La remuneración de un Content Creator Junior depende del nivel de su portfolio, la versatilidad en formatos (texto, imagen y video) y el manejo de métricas de desempeño.
También influyen la dedicación full-time, la autonomía para trabajar remoto y la capacidad de sostener entregas de calidad en un contexto de agencia.
### ¿Qué hace un Content Creator Junior en Argentina?
Un Content Creator Junior en Argentina se encarga de producir y adaptar contenido para redes sociales, blogs y campañas de clientes de una agencia de marketing.
Trabaja en equipo con diseñadores y account managers para cumplir objetivos de comunicación, y documenta métricas básicas de desempeño.
Es un rol de aprendizaje constante, donde el foco está en mejorar pieza a pieza.
### ¿Qué estudiar para ser Content Creator en Argentina?
No hay un único camino formal: sirve formarte en comunicación, publicidad, diseño o periodismo, pero lo que más pesa es la práctica.
Hacer cursos específicos de redacción, edición y redes sociales ayuda, pero el portfolio y la experiencia real son lo que abren puertas.
En Evox valoramos piezas concretas, resultados medibles y ganas de aprender.
#J-*****-Ljbffr

📌 Content Creator Junior (Córdoba)
🏢 Evox
📍 Córdoba