Key Responsibilities:

• Owning and evolving complex systems that span multiple teams, services, and repositories.
• Driving architecture discussions and facilitating high-impact technical decisions.
• Designing, implementing, testing, deploying, and maintaining production systems.
• Conducting thorough, high-volume code reviews across repositories to ensure quality, share context, and unblock teams.
• Pairing with and mentoring engineers across teams to improve technical capabilities and productivity.
• Diagnosing and resolving complex production issues, including algorithmic and data-correctness problems.
• Building and maintaining data ingestion pipelines, event-driven services, and cross-service infrastructure.
• Breaking down large, ambiguous, cross-team initiatives into well-sequenced projects and tasks.
• Improving shared engineering practices and infrastructure, including CI/CD, developer tooling, observability, testing, and security.
• Documenting system architecture and creating runbooks to facilitate knowledge sharing and operational excellence.
• Collaborating closely with engineering leads and business stakeholders to translate ambiguous problems into effective technical solutions.
• Building user-facing features end-to-end when needed, from data models through Phoenix LiveView interfaces.

About RYZ Labs:

Our values and what to expect:

• Customer First Mentality - every decision we make should be made through the lens of the customer.
• Bias for Action - urgency is critical, expect that the timeline to get something done is accelerated.
• Ownership - step up if you see an opportunity to help, even if not your core responsibility.
• Humility and Respect - be willing to learn, be vulnerable, and treat everyone that interacts with RYZ with respect.
• Frugality - being frugal and cost-conscious helps us do more with less.
• Deliver Impact - get things done in the most efficient way.
• Raise Our Standards - always be looking to improve our processes, our team, our expectations. Status quo is not good enough and never should be.

Originally posted on Himalayas