• Participar do desenvolvimento e manutenção de aplicações Front End e Back End; • Apoiar a implementação de melhorias evolutivas e novas funcionalidades; • Contribuir com a qualidade e padronização do código; • Auxiliar na análise e resolução de incidentes e problemas técnicos; • Colaborar com o time na construção de soluções alinhadas às necessidades do negócio; • Aprender e atuar gradualmente em diferentes tecnologias utilizadas nos projetos.

• Design, develop and maintain scalable backend services using Python and FastAPI • Collaborate with data scientists and business stakeholders • Integrate backend services with Azure • Implement automated tests with pytest • Develop CI/CD pipelines

• Build and own shared libraries that engineers across the company depend on for data access, messaging, service communication, observability, and resilience • Design APIs that get adopted — your interfaces need to be good enough that teams choose them over building their own; that means thoughtful defaults, clean abstractions, backward compatibility, and strong documentation • Build multi-cloud abstractions that let services run across cloud providers and on-premise environments without vendor-specific code • Design and implement resilience patterns — retries, circuit breakers, load shedding, graceful degradation — as reusable primitives that become the default for every service • Build platform capabilities — feature management, traffic control, disaster recovery, and sharding as composable libraries • Own the security posture of shared dependencies — keep foundational libraries current, remediate vulnerabilities, and ship secure defaults • Participate in architectural governance — propose, review, and shepherd RFCs that set direction for the services ecosystem • Advocate and consult — be a trusted advisor to engineering teams adopting shared libraries; help them make the right architectural choices, unblock integration challenges, and feed their needs back into the platform • Partner with Data Services, Infrastructure, SRE, and Observability — your libraries sit on top of their platforms; build strong working relationships that keep shared libraries aligned with operational reality • Operate what you build — on-call rotations, production triage, and using operational insight to make the libraries better

• Build and own shared libraries that engineers across the company depend on for data access, messaging, service communication, observability, and resilience • Design APIs that get adopted — your interfaces need to be good enough that teams choose them over building their own; that means thoughtful defaults, clean abstractions, backward compatibility, and strong documentation • Build multi-cloud abstractions that let services run across cloud providers and on-premise environments without vendor-specific code • Design and implement resilience patterns — retries, circuit breakers, load shedding, graceful degradation — as reusable primitives that become the default for every service • Build platform capabilities — feature management, traffic control, disaster recovery, and sharding as composable libraries • Own the security posture of shared dependencies — keep foundational libraries current, remediate vulnerabilities, and ship secure defaults • Participate in architectural governance — propose, review, and shepherd RFCs that set direction for the services ecosystem • Advocate and consult — be a trusted advisor to engineering teams adopting shared libraries; help them make the right architectural choices, unblock integration challenges, and feed their needs back into the platform • Partner with Data Services, Infrastructure, SRE, and Observability — your libraries sit on top of their platforms; build strong working relationships that keep shared libraries aligned with operational reality • Operate what you build — on-call rotations, production triage, and using operational insight to make the libraries better