/ TEAMS · Specialist engineering · Go / Golang
Source engineers experienced in Cloud-native backend services and systems integration. for business-critical production systems, safe integrations and measurable technical ownership.
2,000+ engineers in our active talent network · Regional recruiters
/ SYSTEM STACK
Go concurrency goroutines
contexts cancellation
pprof profiling
gRPC APIs
Go modules
/ AVAILABLE TO HIRE
Profiles show the experience we can source. Individual candidate availability is confirmed after enquiry.
Mid-level Go / Golang Engineer
Inquire availability3+ years of experience · Romania
Go / Golang Engineer with 3 years in production systems, focused on Go concurrency goroutines and contexts cancellation.
Languages: Romanian, English B2+
Mid+ Go / Golang Engineer
Available6+ years of experience · Poland
Go / Golang Engineer with 6 years in production systems, focused on contexts cancellation and pprof profiling.
Languages: Polish, English C1
Senior Go / Golang Engineer
Inquire availability13+ years of experience · Czechia
Go / Golang Engineer with 13 years in production systems, focused on pprof profiling and gRPC APIs.
Languages: Czech, English B2+
Senior Go / Golang Engineer
Inquire availability8+ years of experience · Serbia
Go / Golang Engineer with 8 years in production systems, focused on gRPC APIs and Go modules.
Languages: Serbian, English B2+
/ Engineering teams
Onectus uses its active engineering network and regional recruiting partners to search against concrete systems, environments and responsibilities. We evaluate practical experience rather than treating a framework mention or certification as proof of delivery. Particular availability and engagement terms are confirmed after an enquiry. For this role, practical knowledge of Go concurrency goroutines, contexts cancellation, pprof profiling helps define the engineering search.
/ Technical specializations
The right profile depends on your actual architecture, performance constraints, integration boundaries and operational responsibilities.
Go / Golang responsibilities include go concurrency goroutines, related contexts cancellation, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
Go / Golang responsibilities include contexts cancellation, related pprof profiling, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
Go / Golang responsibilities include pprof profiling, related grpc apis, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
Go / Golang responsibilities include grpc apis, related go modules, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
Go / Golang responsibilities include go modules, related production race detection, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
Go / Golang responsibilities include production race detection, related go concurrency goroutines, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
/ Project scenarios
Build a high-throughput API service. Define constraints around go concurrency goroutines, map dependencies and test how the proposed implementation behaves under real operating conditions.
Diagnose goroutine leaks. Define constraints around contexts cancellation, map dependencies and test how the proposed implementation behaves under real operating conditions.
Reduce p99 latency in a Go backend. Define constraints around pprof profiling, map dependencies and test how the proposed implementation behaves under real operating conditions.
Refactor distributed service interfaces. Define constraints around grpc apis, map dependencies and test how the proposed implementation behaves under real operating conditions.
/ Practical evaluation
A senior engineering interview should surface directly relevant implementation details, debugging history and operational judgment.
Describe a production issue involving Go concurrency goroutines and what evidence led to a fix.
Which decisions around contexts cancellation and pprof profiling were you personally accountable for?
Describe a production issue involving pprof profiling and what evidence led to a fix.
Which decisions around gRPC APIs and Go modules were you personally accountable for?
/ Sourcing process
Define platform versions, deployment constraints, traffic patterns, required integrations and ownership.
Search the active network and partner channels for platform-specific engineering experience.
Discuss real systems, code or configuration decisions, troubleshooting and change control.
Confirm role boundaries, location or remote access, availability, security and interviews.
Profiles, availability and engagement terms are confirmed for each request.
/ Questions
Yes. Tell us the relevant versions, operational environment and the responsibilities connected to Go concurrency goroutines. We qualify hands-on experience during each search.
These can be included when central to the project. We distinguish practical implementation work from general familiarity and ask about failure scenarios and testing.
We look at production decisions, trade-offs, incident diagnosis, code or infrastructure ownership and the ability to explain decisions without relying on a technology checklist.
Share your architecture, technical constraints, collaboration model and priorities. We can then discuss relevant sourcing channels, evaluation criteria and next steps.
/ Onectus · TEAMS
Tell us the technology, production responsibilities, experience level and working model. We'll activate the appropriate engineering sourcing channels.
