Junior Platform Engineer

As a Junior Platform Engineer at Wex, you will assist in building and maintaining infrastructure-as-code using Terraform, support provisioning of cloud infrastructure in both AWS and Azure, and help troubleshoot enterprise tools like GitHub Actions and Kubernetes. Your role will involve collaboration with senior engineers to improve our platform's adoption and contribution to documentation efforts for better self-service capabilities.

To qualify as a Junior Platform Engineer at Wex, candidates should have experience in software development or infrastructure engineering. Familiarity with at least one programming language, such as Python or Go, is beneficial, as is a basic understanding of CI/CD workflows. A keen interest in cloud platforms like AWS and Azure, alongside tools like Terraform or Kubernetes, is also desired.

Junior Platform Engineers at Wex work with a variety of tools including GitHub for source control, Terraform for infrastructure-as-code, and Kubernetes for container orchestration. Additionally, they may interact with automation tools like ArgoCD, and secrets management technologies such as HashiCorp Vault as part of their everyday tasks.

Wex is committed to the professional development of its Junior Platform Engineers by offering mentorship programs with experienced engineers, a dedicated professional development budget, and opportunities for involvement in significant platform transformations that enhance learning and career advancement.

The work environment for Junior Platform Engineers at Wex is fast-paced and highly collaborative. You'll be part of a supportive team that emphasizes hands-on learning, encourages communication, and promotes a culture of innovation as you take meaningful steps towards building efficient internal platforms.

Infrastructure-as-code (IaC) refers to the practice of managing and provisioning computing infrastructure through machine-readable definition files, rather than physical hardware configuration. For a Junior Platform Engineer, understanding IaC is crucial because it enables better scalability, consistency, and the ability to automate deployment processes, ultimately making infrastructure management efficient.

Troubleshooting GitHub Actions starts with isolating the issue. First, check the logs for any errors related to the workflow; these may provide clues about what went wrong. Then, verify that the configurations are correct, and if possible, run the actions in a simplified environment to recreate the issue. Always engage with the community or documentation for insights on known issues.

In my previous experience, I have worked with both AWS and Azure, where I assisted in provisioning cloud infrastructure and utilizing various services offered, such as EC2 instances in AWS and Azure App Services. I also have familiarity with their respective management consoles and CLI tools, which aid in deploying applications seamlessly.

CI/CD stands for Continuous Integration and Continuous Deployment, which are practices used to automate the software delivery process. Continuous Integration refers to the regular merging of code changes into a central repository, followed by automated testing to validate each integration. Continuous Deployment extends this by automatically deploying tested changes to production, ensuring frequent releases and immediate feedback.

I prioritize continuous learning by engaging with online courses, attending webinars, and participating in community meetups. I subscribe to relevant blogs and follow industry news which keep me updated on the latest tools and best practices in the field. Collaborating with experienced colleagues is also invaluable for gaining practical insights.

One challenge could be managing the complexity of multi-cloud environments. To address this, I would invest time in mastering the tools used for cloud management and seek mentorship from seasoned team members to better understand the various configurations and maintenance strategies needed to ensure a seamless operation.

I have hands-on experience with Terraform in creating infrastructure configurations. In this role, I would leverage Terraform to build and maintain our infrastructure-as-code, starting with simple projects and progressively transitioning to more complex configurations, collaborating closely with the team to ensure best practices are followed.

In a recent project, our team faced challenges with deploying a service across multiple environments. We held brainstorming sessions to gather insights, divided responsibilities based on each member’s strengths, and collaborated closely to implement a robust CI/CD pipeline that improved our software delivery process significantly.

Some essential security best practices include regular code reviews to detect vulnerabilities early, utilizing secrets management tools to store sensitive information securely, and applying the principle of least privilege for access controls. Additionally, staying informed about industry standards, such as PCI or HIPAA, is vital for compliance.

I am drawn to Wex because of its commitment to innovation and collaboration in the tech space. The opportunity to be involved in significant platform development and transformation projects is incredibly appealing. I believe that the support and resources Wex offers align perfectly with my career aspirations to grow as a skilled platform engineer.