Remote Technical Architect – DevSecOps & Cloud Migrations

Remote Technical Architect – DevSecOps & Cloud Migrations

Full-Time 67500 - 82500 £ / year (est.) Remote
G

At a Glance

  • Tasks: Lead technical direction for customer projects and design high-level architectures.
  • Company: Join GitLab, a leader in DevSecOps and cloud migrations.
  • Benefits: Enjoy remote work flexibility, competitive salary, and professional growth opportunities.
  • Other info: Collaborative environment with a focus on innovation and customer success.
  • Why this job: Shape the future of cloud infrastructure and make a real impact.
  • Qualifications: Experience in DevSecOps, cloud migrations, and architecture design.

The predicted salary is between 67500 - 82500 £ per year.

GitLab is seeking a Professional Services Technical Architect to lead the technical direction of customer engagements from scoping to delivery. You will design high-level architectures and plans for GitLab infrastructure, coordinating across Professional Services and partners to ensure deliverables meet requirements and the SOW.

You’ll enable customers deploying GitLab in cloud and on-prem environments using Terraform, Ansible, and the GitLab Environment Toolkit, performing migrations.

Remote Technical Architect – DevSecOps & Cloud Migrations employer: GitLab Inc.

GitLab is an exceptional employer that champions a fully remote work culture, offering flexibility and autonomy to its employees. With a strong focus on professional development, you will have ample opportunities to grow your legal expertise while collaborating with diverse teams across the globe. The supportive environment fosters innovation and inclusivity, making it a rewarding place for those seeking meaningful employment in the legal field.

G

Contact Details:

GitLab Inc. Recruitment Team

StudySmarter Expert Advice🤫

We think this is how you could land Remote Technical Architect – DevSecOps & Cloud Migrations

✨Join Local Tech Meetups

Get out there and mingle with fellow developers by joining local tech meetups. It’s a fantastic way to meet people who might be working at GitLab Inc. or know someone who does. Plus, you can pick up some trendy tech skills and trends while you're at it!

✨Contribute to Open Source Projects

Show off your coding chops by jumping into open-source projects. Not only does this give you practical experience, but it also gets you noticed in the dev community. You'll create a killer portfolio that speaks volumes about your skills to GitLab Inc..

✨Tap into Online Developer Communities

Don’t underestimate the power of online developer communities like GitHub, Stack Overflow, and even Reddit. Participate in discussions, share your projects, and build your visibility. We can often find opportunities through these channels that can lead to a full-time gig at companies like GitLab Inc..

✨Explore Job Boards Specifically for Tech Roles

Keep your eyes peeled on job boards that focus on tech roles. Sites like TechCareers or Stack Overflow Jobs can often have listings for companies like GitLab Inc. that might not show up on broader job sites. Make it a habit to check these regularly, and don’t hesitate to apply directly through our website!

We think you need these skills to ace Remote Technical Architect – DevSecOps & Cloud Migrations

Technical Architecture
DevSecOps
Cloud Migrations
GitLab
Terraform
Ansible
Infrastructure Design

Some tips for your application 🫡

Show off your coding skills:When applying for a software engineering role, it's super important to showcase your coding skills. Make sure your CV includes your tech stack, any relevant programming languages you’re comfortable with, and examples of projects you've worked on. If you have a GitHub profile, link it up! We love to see code in action.

Tailor your portfolio:For a full-time role, we’d expect to see some solid examples of your work in your portfolio. Make sure to include at least two or three projects that highlight your problem-solving skills and your ability to work with different technologies. Focus on the projects that are most relevant to the position at GitLab Inc..

Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at GitLab Inc. and how your skills align with the role. Show us your passion for software development. We dig enthusiastic candidates who understand the value of collaboration and continuous learning!

Be clear and concise:When it comes to writing your CV and cover letter, clarity is key. Avoid jargon that could confuse us and stick to simple, direct language. Highlight your achievements with quantifiable results where possible, and keep everything easy to read. A well-organised application goes a long way!

How to prepare for a job interview at GitLab Inc.

✨Brush Up on Your Coding Skills

For a full-time software engineering role, it's crucial that we stay sharp with our coding abilities. Expect technical questions that might involve solving problems on the spot or discussing algorithms. Practise on platforms like LeetCode or HackerRank to get comfortable with the types of questions that often come up.

✨Know Your Tools and Frameworks

Make sure we’re well-acquainted with the tools and technologies listed in the job description. Familiarise ourselves with any specific frameworks or programming languages mentioned. If GitLab Inc. uses React or Node.js, for instance, be ready to discuss how we’ve used them in previous projects or coursework.

✨Showcase Your Projects

Bring along a portfolio that highlights our best work. This could be code samples, GitHub repositories, or any side projects we’ve built. Make sure we can talk through our thought process for each project, especially the challenges we faced and how we solved them—this shows our problem-solving skills in action.

✨Prepare for Behavioural Questions

While technical skills are key, full-time positions also require cultural fit. Be ready to discuss our previous experiences and how we handle teamwork, conflict, and deadlines. Brush up on the STAR method—Situation, Task, Action, Result—to clearly articulate our past experiences when discussing how we've contributed to a team.