Principal Elixir Engineer

As a Principal Elixir Engineer at Array, your main responsibilities will include leading incident response efforts, designing and implementing secure and scalable Elixir applications, analyzing logs and application data for issue resolution, and conducting regular assessments to ensure the stability and performance of production environments.

To be considered for the Principal Elixir Engineer position at Array, you’ll need at least 12 years of experience in software engineering, substantial expertise in Elixir, hands-on experience with the Phoenix Framework in production, and a strong understanding of functional programming and distributed systems design.

Array offers a competitive base salary starting at $178,000, along with full medical, dental, and vision coverage for employees. Additionally, you can enjoy unlimited PTO, summer Fridays, a generous 401k match, and a $1,000 subsidy for your remote desk setup.

At Array, we pride ourselves on being an equal opportunity workplace. We are dedicated to creating an environment where everyone feels supported and empowered to bring their best selves to work while fostering diversity, equity, and inclusion that enhances collaboration and confidence.

The interview process for the Principal Elixir Engineer role at Array typically involves a conversation with a recruiter, a meeting with the Co-founder (Founding CTO), and a discussion on how we work. This structured approach ensures that candidates get a clear picture of both the role and our company culture.

When answering this question, detail your years of experience with Elixir, emphasizing specific projects you've worked on using the Phoenix Framework. Highlight how you've used these technologies to solve real-world problems and the results you've achieved.

Discuss your approach to incident response, including the tools and processes you use. Provide specific examples of incidents you've managed, the steps you took to resolve them, and the outcome.

Share your strategies for securing Elixir applications, such as implementing access control measures, keeping dependencies up to date, and conducting regular security assessments. Be sure to mention any specific practices you've followed or standards you've adhered to.

Talk about the factors you consider when evaluating architectural changes, including performance, scalability, and maintainability. Provide an example where you made a significant architectural decision and the impact it had.

When responding, explain your understanding of distributed systems and how you've contributed to designing them in prior roles. Mention specific challenges you've faced and how you overcame them.

Describe key functional programming principles that inform your coding practices, such as immutability and first-class functions. Provide examples of how you've applied these principles in your projects.

Emphasize the importance of communication tools and practices you've found effective in maintaining collaboration across remote teams. Share a specific instance where you collaborated with others successfully.

Discuss your familiarity with DevOps pipelines and how you've used GitLab CI/CD in previous roles. Provide examples of how you integrated CI/CD into project workflows and the benefits it brought to your teams.

Talk about the resources you utilize to stay informed, such as blogs, webinars, or community events. Mention how you’ve integrated new trends or technologies into your work.

Provide a specific example of how you encouraged best practices within your team. Discuss the challenges you may have faced and the positive outcomes of those efforts.