Uma candidatura completa num minuto — currículo personalizado e carta de apresentação, prontos a enviar.
Sierra Studio in Brazil is seeking a Lead AI Engineer to own the architecture end to end, auditing existing systems, and turning the platform into a scalable, well-documented codebase. You'll work closely with the founder, set standards, and shape the engineering function for an agency-meets-software company.
You will design data pipelines from Klaviyo, Postscript, Attentive, build agentic AI workflows, and lead integrations with email/SMS platforms.
When you apply to Sierra, you join an ecosystem. We specialize in connecting talented Brazilian professionals with exciting career opportunities in a highly-vetted small community of growing companies in the US. Applying to Sierra seamlessly integrates you into this ecosystem, granting automatic eligibility for all relevant opportunities we offer.
Location: Brazil, remote
Compensation: $70k – $120k USD, CNPJ
Reports to: Founder & CEO
Our hiring partner is a US-based retention marketing agency helping DTC brands build personal relationships with their customers at scale through the channels they own: email, SMS, and everything in between. Their thesis is simple: brands shouldn't have to grow by unprofitably spending more on paid social. Everything they do is built around producing programs and messages that customers actually want and that actually perform.
They’re a team of about 12 (strategists, specialists, designers, copywriters, and ops), fully remote, at ~$1.2M in revenue with a goal to double in the next four months. They partner with the leading platforms in the space and are now evolving from an agency with great internal tooling into something closer to an agency and a software company combined.
Our hiring partner is hiring their first engineer.
The founder has already built the foundation himself using AI coding tools: a data layer that pulls Klaviyo data for every client into the company's own Supabase database (so the team can query it in ways the platform's native API doesn't allow), a set of AI skills and workflows the team uses instead of building reports by hand, and a diagnostics tool made of agents that continuously QA client accounts and flag what's broken. On top of that sit early products that are somewhere between prototype and solid foundation.
It works and it's validated. But it was built by one person, and it's reached a level of disorganization that isn't sustainable as the company scales. The products need to be rebuilt with scale in mind, and the whole system needs an engineer who owns it.
That's where you come in. You'll own the architecture end to end: auditing what exists, deciding what stays and what gets rebuilt, and turning it into a fully maintained codebase with clear guidelines. You'll pair closely with the founder, who leads on product while you lead on development, iterating on agency workflows and products with feedback that comes directly from clients. And you'll build agentic flows across nearly every area of the business, from account diagnostics to go-to-market, which today are all built and maintained by the founder alone.
This is a lead role, not a founding-engineer-in-name-only role: you set the technical direction and standards for everything that gets built, and as the engineering function grows, you'll be the one shaping it.
The culture is built around ownership. Everyone geeks out on their craft, shares what they learn, and treats each other like adults. Because the team is remote, there's a lot of flexibility and an equal amount of accountability. People who take a full area, own it end to end, hit deadlines, and communicate proactively do very well here. People who need to be monitored don't.
What makes this role different is where you sit. Most engineers building in this space are inside a software company, one step removed from the people using what they ship. Here you're inside the agency: the feedback loop with clients is direct, the results are measurable in revenue, and you're never limited to what the software can do. You get to own an entire engineering function and be at the front of figuring out what it looks like when an agency and a software company become the same thing. If that sounds like the kind of problem you'd want to go build your way through, you'll like it here.