Full Stack Infrastructure Engineer

The Full Stack Infrastructure Engineer at Code.org is responsible for configuring systems that support the building, monitoring, scaling, testing, securing, and deploying of our educational software. You will own projects from start to finish, collaborate with a diverse team, and ensure excellent live site availability while tackling exciting technical challenges.

Candidates should have substantial experience in deploying and operating high-usage web applications, particularly in AWS environments. You should be skilled in writing clean, testable code, particularly in Ruby or similar languages, and have hands-on experience with production reliability engineering and incident response.

To stand out for this role, it's essential to have strengths in application-aware infrastructure debugging, backend platform engineering, and web security fundamentals. Experience with CI/CD pipelines and frameworks for automated testing also adds great value to your profile.

At Code.org, collaboration is key! Engineers work closely with product managers and other engineers to enhance systems, ensuring that every project aligns with our mission of expanding computer science education. You'll participate in a growth-focused and inclusive culture that values each team member's input.

The interview process involves an initial informational interview to discuss your experience, followed by a complete interview loop that includes cloud foundations, coding assessments, and operational excellence questions. Finally, candidates have an hour-long conversation with the CTO, ensuring a comprehensive understanding of both technical skills and cultural fit.

Discuss specific projects where you've deployed applications in AWS, focusing on the services you used, such as EC2, S3, or RDS. Highlight how these technologies improved the performance and scalability of the applications.

Talk about your approach to security, including familiarity with web security fundamentals, threat modeling, and proactive vulnerability mitigation. Provide examples of how you've implemented security best practices in past projects.

Share the monitoring tools you prefer, such as Prometheus or Grafana, and explain how you've utilized them to track system health and optimize performance, including real-life examples of issues you've resolved.

Describe your protocol for managing incidents, including detection, response time, mitigation strategies, and how you've collaborated with teams to minimize downtime and implement solutions.

Detail how you've set up CI/CD pipelines in your previous roles, what tools you've used like Jenkins or GitLab, and how this process has improved deployment efficiency and code quality.

Explain your strategies for prioritizing tasks based on urgency and impact, such as using Kanban boards or Agile methodologies. Provide examples of how this has helped your teams stay focused and productive.

Share specific challenges around database management, data throughput, or load balancing, and discuss how you addressed these issues through architectural changes or optimizations.

Discuss a specific project where you've introduced meaningful improvements, focusing on the problem, your approach, and the resulting benefits to performance, efficiency, or user experience.

Highlight best practices you follow, such as adhering to coding standards, peer reviews, and unit testing. Provide an example of how this approach has led to higher-quality code and fewer bugs.

Share your personal connection to education and technology, how it has influenced your career path, and your commitment to using technology to enhance learning opportunities for students.