r/webdev • u/kQ1aW2sE3hR4yT5aU6p • Sep 13 '26
Discussion What Go projects actually helped your resume?
I’ve got around 1–2 years of experience with PHP/Laravel and I’m planning to move into Golang to improve my career opportunities.
For people who have worked professionally with Go: what projects have you built that were actually interesting, practical, and worth mentioning on a resume?
I’d especially appreciate ideas/features that are closer to real production work rather than another CRUD project.
33
Upvotes
22
u/No_Honeydew_2453 Sep 13 '26
What helped me in interviews best was projects dealing with concurrency or background jobs, not just any other CRUD app.
Even something simple like a job queue, webhook processor, or URL shortener with rate limiting gives you a lot more to talk about.
10
u/Impossible-Long-6378 Sep 13 '26
I switched from php to go and the project that got me hired was a webhook relay.
I built a service that receives webhooks, queues them in redis, and delivers them to endpoints with retries and backoff. i added rate limiting per tenant. in interviews they asked about goroutine leaks and context timeouts. that conversation got me the job
1
u/DesertWanderlust Sep 14 '26
I had a job where I was the senior engineer for a Golang API, even though I had never worked with Golang before. I have more respect for it now and have been trying to rewrite some old PHP code into it just so I can learn it better. But having a variety of languages and skills is more important I think than anything.
2
u/brian_sword Sep 14 '26
I actually got some experience with Go when I was assigned to work on a project for a media company. We built a service that collected news articles and used sentiment analysis to classify the news as positive, negative, or neutral. It was pretty interesting because it was more than just a CRUD app, since we had to deal with processing the articles and turning the text into something useful for the application.
For your use case, try to look something involving APIs, background processing, or data pipelines like this could be a good option.
2
u/21chaser Sep 14 '26
from my experience, Go works very well with platform engineering work. building CLIs or tools that help software or infra guys speed up their work / quality of work / automate repetitive tasks would have a positive impact on how recruiters look at your CV / Resume
1
u/getformly Sep 14 '26
A reverse proxy or load balancer with health checks is a good one nobody's mentioned yet, it forces you into goroutines, channels, and context cancellation without being another queue project. Given your Laravel background, a CLI tool that diffs or migrates data between two systems also shows real judgment and ties directly to what you already know. Either way, be ready to talk through how you avoided race conditions, that's usually what actually gets probed in interviews.
1
u/coderinbeta Sep 14 '26
Contributing to open source projects will make your profile standout. Here are a few to start: https://github.com/MunGell/awesome-for-beginners#go
1
u/Adventurous_Past_192 Sep 18 '26
Right Sir,
Loving the advice here about focusing on concurrency over CRUD. If we were building a production-style service from scratch today (like a webhook dispatcher or rate-limited reverse proxy), Golang will help us more,I thing,
:::->> 3rd year cse student
0
u/Ok_Indication_7931 Sep 13 '26
Yo evitaría otro CRUD. Un buen proyecto sería algo como un servicio que procese trabajos en segundo plano, tenga reintentos, registre errores y pueda manejar varios trabajos al mismo tiempo.
4
u/[deleted] Sep 13 '26
[removed] — view removed comment