DevSecOps Engineer

As a DevSecOps Engineer at Raft, your primary responsibilities will include building and maintaining ETL pipelines for data operations and leveraging software engineering principles to develop large-scale data applications. You’ll collaborate closely with a team of experts, ensuring that our data platform for the Department of Defense provides timely and accurate information for operators.

To qualify for the DevSecOps Engineer role at Raft, you need at least three years of hands-on experience in the field. Essential skills include familiarity with large-scale databases like PostgreSQL and MongoDB, knowledge of service mesh technologies, and proficiency in automation languages such as Python or GoLang. Additionally, obtaining a Security+ certification within the first 90 days is a requirement.

At Raft, DevSecOps Engineers work with a variety of cutting-edge technologies, including Apache Kafka, Kubernetes, and cloud-native tools. Familiarity with monitoring and logging solutions like Prometheus, Grafana, and Fluentbit is also beneficial to ensure the platforms we build are robust and fault-tolerant.

The work environment for a DevSecOps Engineer at Raft is collaborative and inclusive, focused on innovation and problem-solving. You'll experience a culture that values customer obsession and teamwork, empowering individuals to contribute their unique perspectives while working towards shared goals.

Raft is committed to the professional development of its employees, offering education and training benefits as well as annual budgets for tech-related needs. As a DevSecOps Engineer, you will be encouraged to enhance your skills and stay current with industry advancements, contributing to both your personal growth and the success of the team.

When answering this question, focus on specific ETL projects you've worked on, the tools you used, and the outcome of those initiatives. Highlight your understanding of data governance and any challenges you overcame while ensuring the integrity and efficiency of data processing.

In your response, discuss your familiarity with cloud technologies and platforms, your approach to architecting applications for scalability and reliability, and any specific cloud services you've integrated into your projects. Don't forget to mention your experience with container orchestration tools like Kubernetes.

Detail your knowledge of various relational and non-relational databases, how you've utilized them in past projects, and any performance optimization techniques you implemented. Explain your strategy for selecting the right database for specific use cases, particularly in high-demand scenarios.

Share a specific example from your experience illustrating your role within the team, the challenges faced, the collaborative effort involved, and the final outcome. Emphasize communication and how different perspectives contributed to the solution.

Outline your understanding and implementation of security principles in DevSecOps, mention any specific frameworks or tools utilized, and share how you incorporate security into every stage of the development lifecycle.

Describe your proactive approach to continuous learning in the field of DevSecOps, such as following industry blogs, attending workshops or webinars, and participating in community forums or local meetups.

Discuss the specific monitoring and logging tools you've used, explain your experience with them, and illustrate how these tools have helped you maintain application performance and troubleshoot issues effectively.

Talk about your experience with code review processes, automated testing, continuous integration, and continuous deployment (CI/CD). Highlight how these practices contribute to reduced bugs and smoother releases.

Detail your familiarity with microservices, including the benefits you’ve seen from using this architecture, any specific challenges encountered, and how you’ve managed service communication and data consistency.

Explain your methodical approach to troubleshooting ETL pipeline failures, which may include analyzing logs, verifying data integrity, and reviewing all configurations to identify the root cause, as well as the importance of having a rollback plan in place.