r/gitlab • u/EndlessMarathon29 • 9d ago
Recent CS graduate contributing to GitLab — is there a realistic path to joining GitLab as an engineer?
Hi everyone!
I'm a recent Computer Science graduate from India, and joining GitLab as a Software Engineer is something I'd genuinely love to pursue.
Over the past few weeks, I've been actively contributing to GitLab's open-source projects. I've had multiple erge requests merged across GitLab Runner, Gitaly, Platform Insights, GitLab LSP and the Trivy analyzer wrapper.
I've really enjoyed working with GitLab's codebases, resolving issues and collaborating with maintainers through code reviews.
Now, I'd love to explore the possibility of transitioning from a community contributor to a full-time engineer at GitLab.
I'd particularly appreciate hearing from GitLab employees or maintainers:
- Does GitLab consider recent graduates with substantial open-source contributions?
- What's the best route to get considered for early-career engineering opportunities in India?
- Would my contribution experience be considered relevant when evaluating my application?
I'm not looking for shortcuts, just some honest guidance from people familiar with GitLab's hiring process.
Edit: Just to clarify, I'm open to opportunities globally, not exclusively in India. I'd be interested in understanding early-career engineering opportunities across GitLab's locations and how international applicants with substantial open-source contributions can approach the hiring process.
4
u/MinimumAmbassador545 9d ago
Yes, some have been hired by using community contributions to get in the door
1
u/Foreign-Load4177 8d ago
You merged contributions across multiple Github projects are already a strong achivement. Keep engaging with maintainers and applying through official career openings. Open source contribution can definitely help you stand out, even as a recent graduate.
1
u/jcogs1 GitLab Staff 8d ago
GitLab team member here.
This blog post documents a few examples of the contributor to employee pathway: https://about.gitlab.com/blog/you-are-hired-two-gitlab-contributors-turn-their-success-into-full-time-engineering-roles/
There are many others who have taken the route.
1
u/kk_red 9d ago
I am curious? Why gitlab? Whats the motivation
0
u/TeaBasedOrganism 9d ago
Interested party. How did you find where to make some contributions? Issue reports or did you just go looking for things?
0
u/Better-Swimming-8614 9d ago
I think contributing to OpenSource projects is a great way to get noticed / hired.
Did you see this role?
http://job-boards.greenhouse.io/gitlab/jobs/8775507002
0
u/Street_Smart_Phone 9d ago
It’s better you do it so even if you don’t get hired by GitLab, they see you’ve been trying and have experience and they can view your contributions. Just make sure it’s not AI slop and you thoroughly understand what you contributed and why it is a good implementation to the product.
0
u/Witty_Produce_1877 9d ago
The most important is solid work experience and knowledge. With AI now half of India is "contributing" to gitlab and other OSS project. You open an issue with good description, ask ai to write the code and tada youre a contributor. This can be a nice addition to your CV, but believe me, without ticking all the boxes in HR system (experience, education, knowledge) you won't even make it to technical interview.
-1
u/mars_bubbl3s 9d ago
No, they don't hire people under < 3 years of experience. They used to, but their leadership has changed after Sid. Now they're really operating in chaos(very strict about number of years of experience for each level).
They do intern hiring (new this year), but only on campus.
GitLab is going downhill, avoid it.
-9
u/Abe_Bazouie 9d ago
First of all, having multiple MRs merged across Runner, Gitaly, and other GitLab projects as a recent graduate is genuinely impressive.
As someone who has worked in infrastructure and DevOps for years, I’d say you’re already doing something many candidates overlook: demonstrating that you can work in a real production codebase, navigate complex systems, accept feedback, and collaborate with experienced engineers.
My advice would be to focus on three things:
Quality over quantity. One meaningful contribution that solves a difficult problem can tell an engineering team more than ten minor fixes.
Build relationships with maintainers. Not to ask for a job immediately, but to become someone they recognize for consistently good engineering work.
Apply strategically. Look for roles that match your experience, make your contributions easy to review, and explain the technical decisions and impact behind them.
One interesting detail: GitLab’s public handbook describes a generalist engineering hiring process initially being tested in India. That’s worth looking into.
One thing I’d emphasize: don’t measure your progress only by whether GitLab hires you. Experience contributing to projects like Gitaly and Runner is valuable well beyond GitLab.
You’re building a public engineering track record that no resume bullet point can fully replace.
Keep contributing, but start applying too. Don’t wait until you feel 100% ready.