Role Description You're the engineering anchor of an initiative — working as part of a tight team with your PM and designer, and alongside engineering peers on adjacent initiatives. You have a hand in the full lifecycle: shaping the problem, deciding the technical approach, directing AI agents to implement much of the code, shipping to production, and — with your team — owning the outcome. You're measured by impact, not by lines of code merged. When an agent can ship something safely, your job is to make sure it's done right and the metric moves. When the work calls for careful, hand-written code in a sensitive area, you write it yourself. What makes this role exciting: - You ship end-to-end. From problem-framing through production to the post-launch metric review — you see the whole arc and own the result with your team. - You work as a true product partner. You sit at the table with PM and design, bringing engineering judgment to product calls and product sense to engineering calls. - You get real autonomy — with the right checkpoints. You make most technical calls yourself, with architect review on significant architectural decisions and fast input from peers. - You operate at a staff bar. You're trusted to make the call, ship the hard thing, and stand behind the outcome. What You'll Own - The technical approach — architecture, data model, integration choices, rollout plan, observability, and rollback strategy for your initiative. - Implementation quality — the prompts, guardrails, evals, tests, and review loop that let agents ship safe, correct, production-ready code. - Cross-functional partnership — daily working contact with your PM (scope, tradeoffs) and designer (UX decisions, in-tool prototyping), regular collaboration with engineering peers, and weekly check-ins with your EM. - The initiative outcome — the metric the initiative was set up to move. - A high bar for what ships — production correctness, security, performance, observability, and the experience for customers and pros. Problems to Solve - Leading AI agents at a staff-level quality bar. - Owning decisions with high autonomy. - Shipping outcomes, not features. What Success Looks Like (Year 1) - Initiative outcomes hit — You've shipped 3–4 initiatives end-to-end, and at least two clearly moved their metric. - Agent workflow that travels — The prompts, evals, and review loop you built are picked up by peers on other initiatives. - Faster cycle time — Median time from problem-framing to first production rollout on your initiatives is meaningfully shorter. - Quality holds — No customer- or pro-facing regression traceable to agent-authored code that slipped through your review. - Visible leverage — Peers point to artifacts you left behind — runbooks, evals, agent workflows, post-launch write-ups — as references they use. Who You Are - AI-native. Claude Code, Cursor, Codex, or equivalent are how you ship today. - Operating at a lead level. You've been the person making the call, shipping the hard thing, and standing behind whether it worked. - Outcome-driven. You measure your week in "did the metric move" and "did the experience get better." - A strong horizontal partner. You hold your own with a strong PM and designer, and you collaborate well with engineering peers. - Decisive and documented. You make architecture, data-model, and rollout calls, write them down, get fast input, and move. - A force multiplier. Your impact compounds beyond your own initiative because you leave reusable artifacts behind. - Customer- and pro-minded. You care about the outcomes for both. Good to Know - An individual-contributor role with room to grow. - A product-engineering role, end-to-end. - Hands-on, with a high quality bar. - Shipping to a live marketplace. Tech You'll Touch - AI agents — Claude Code, Cursor, Codex, internal agent stack, MCP servers, evals tooling. - Backend — PHP/Laravel. - Frontend — TypeScript/React/React Native. - Data — Redshift, dbt, Segment, Airflow. - Infra — AWS, Datadog, Sentry, GitHub Actions. - Documentation & process — Brain, Confluence, Jira. Salary and Benefits - Competitive salary of USD $80,000–$100,000 annual base. - Work from anywhere. - High ownership and autonomy. - Fast-moving team that loves to build, learn, and grow.

• Profesional que traduce los requerimientos de negocio en soluciones funcionales dentro de la plataforma low-code.

• Desarrollar aplicaciones móviles siguiendo el sistema determinado en base a las reglas, estándares e indicaciones especificas establecidas • Produzca aplicaciones móviles completamente funcionales que escriban código limpio • Diseñar interfaces para mejorar la experiencia del usuario. • Conocimiento profundo de al menos un lenguaje de programación como Swift y Java. • Familiaridad con los principios de diseño de programación orientada a objetos. • Las principales plataformas que son: Android de Google y Windows Phone de Microsoft.

• Maintain large-scale pipelines for processing web corpora. • Work on filtering and quality-scoring systems to identify high-value web documents. • Analyze web data composition across domains, languages and time periods. • Develop and maintain highly-performant deduplication pipelines. • Collaborate with cross-functional teams, including researchers and engineers, to ensure data pipelines meet the demands of cutting-edge language models.