Which Go Projects Are Actually Worth Putting on a Resume?

Keep the scope small but make it look like something a team could actually run: build a JSON API with PostgreSQL, authentication, a background worker, solid tests, structured logging, and metrics. Deploy it and document decisions around migrations, error handling, and scaling. You can also contribute to an existing Go open-source project, since reviewing unfamiliar code and submitting a focused change demonstrates skills that a personal demo may not.

A service that collects articles and runs sentiment analysis is another good direction. It involves APIs, background processing, text transformation, and turning raw data into something useful instead of simply storing records. Data pipelines and processing services are great ways to make a project feel realistic.

Projects involving concurrency and background processing tend to give you much more to discuss in interviews than a standard CRUD app. A job queue, webhook processor, or URL shortener with rate limiting can demonstrate goroutines, retries, timeouts, and safe concurrent work.

A reverse proxy or load balancer with health checks is a strong option. It naturally introduces goroutines, channels, request forwarding, timeouts, and context cancellation. Another useful idea is a CLI that compares or migrates data between systems, which connects well with your Laravel experience while showing practical engineering judgment.

A webhook relay worked really well for me. It accepted incoming webhooks, queued them in Redis, delivered them to destination endpoints with retries and exponential backoff, and applied rate limits per tenant. Interviewers were particularly interested in how I handled context timeouts and prevented goroutine leaks.