Business Services & Consulting • all cities, UT 45
Exceptional Engineer (45)
all cities, UT 45On-sitePosted 1 day ago
Business Services & Consulting
About the Role
Exceptional Engineers
We are hiring a very small number of exceptional engineers. We are not trying to fill seats — we are trying to raise the average. If you join, the bar for everyone after you goes up.
This role is for people who ship fast and ship well, and who have alreadyproven they can do that when the stakes and the pace were highest. If that's you, the rest of this will read as an invitation rather than a wishlist.
What We're Looking For
We're hiring for a specific profile, not a checklist of years. The signals that matter to us:
You operate in the top tier of engineers you've worked with. You're usually the person others go to when something is hard, ambiguous, or on fire. Your past managers and peers would describe you as one of the strongest engineers they've worked alongside.
You combine speed with craft. You ship quickly without leaving a mess behind you. You have strong instincts for what deserves polish and what just needs to work, and you rarely confuse the two.
You've done this during hyper-growth. At a previous company, you were a core engineer while it scaled fast — rapid user growth, scaling systems, scaling teams, or all three. You've felt what breaks at scale and you've fixed it in production, not in theory.
You take real ownership. You don't wait to be assigned problems; you find them, scope them, and close them. When something is broken, you treat it as yours regardless of whose code it is.
You have strong technical taste. Good judgment about abstractions, data models, and tradeoffs — and the humility to change your mind when the evidence does.
Signals That You Might Be A Great Fit
You don't need all of these, but several should resonate:
You've owned a system that went from "works for a few thousand users" to "works for millions" — and you remember exactly where it hurt.
You've shipped something significant in a window that surprised people, and it held up.
You have side projects, open-source contributions, or a track record that shows you build because you can't help it.
You've been an early or key engineer somewhere that grew up fast, and people there would fight to work with you again.
Nice-To-Haves
Experience in observability (monitoring / logging / tracing)
Familiarity with OpenTelemetry, ClickHouse, Kubernetes, etc.
Has been, or wants to be, a founder in B2B/devtools
Why You'll Love Working At SigNoz
Work on a globally used open-source project that engineers actually love
Huge scope and ownership – your work directly shapes how teams adopt SigNoz
Collaborate with high-caliber team who just can't stop shipping
Remote-first, async-friendly culture
Opportunity to help define the future of open-source observability
Exceptional Engineers
We are hiring a very small number of exceptional engineers. We are not trying to fill seats — we are trying to raise the average. If you join, the bar for everyone after you goes up.
This role is for people who ship fast and ship well, and who have alreadyproven they can do that when the stakes and the pace were highest. If that's you, the rest of this will read as an invitation rather than a wishlist.
What We're Looking For
We're hiring for a specific profile, not a checklist of years. The signals that matter to us:
You operate in the top tier of engineers you've worked with. You're usually the person others go to when something is hard, ambiguous, or on fire. Your past managers and peers would describe you as one of the strongest engineers they've worked alongside.
You combine speed with craft. You ship quickly without leaving a mess behind you. You have strong instincts for what deserves polish and what just needs to work, and you rarely confuse the two.
You've done this during hyper-growth. At a previous company, you were a core engineer while it scaled fast — rapid user growth, scaling systems, scaling teams, or all three. You've felt what breaks at scale and you've fixed it in production, not in theory.
You take real ownership. You don't wait to be assigned problems; you find them, scope them, and close them. When something is broken, you treat it as yours regardless of whose code it is.
You have strong technical taste. Good judgment about abstractions, data models, and tradeoffs — and the humility to change your mind when the evidence does.
Signals That You Might Be A Great Fit
You don't need all of these, but several should resonate:
You've owned a system that went from "works for a few thousand users" to "works for millions" — and you remember exactly where it hurt.
You've shipped something significant in a window that surprised people, and it held up.
You have side projects, open-source contributions, or a track record that shows you build because you can't help it.
You've been an early or key engineer somewhere that grew up fast, and people there would fight to work with you again.
Nice-To-Haves
Experience in observability (monitoring / logging / tracing)
Familiarity with OpenTelemetry, ClickHouse, Kubernetes, etc.
Has been, or wants to be, a founder in B2B/devtools
Why You'll Love Working At SigNoz
Work on a globally used open-source project that engineers actually love
Huge scope and ownership – your work directly shapes how teams adopt SigNoz
Collaborate with high-caliber team who just can't stop shipping
Remote-first, async-friendly culture
Opportunity to help define the future of open-source observability
What You'll Do
You operate in the top tier of engineers you've worked with. You're usually the person others go to when something is hard, ambiguous, or on fire. Your past managers and peers would describe you as one of the strongest engineers they've worked alongside.
You combine speed with craft. You ship quickly without leaving a mess behind you. You have strong instincts for what deserves polish and what just needs to work, and you rarely confuse the two.
You've done this during hyper-growth. At a previous company, you were a core engineer while it scaled fast — rapid user growth, scaling systems, scaling teams, or all three. You've felt what breaks at scale and you've fixed it in production, not in theory.
You take real ownership. You don't wait to be assigned problems; you find them, scope them, and close them. When something is broken, you treat it as yours regardless of whose code it is.
You have strong technical taste. Good judgment about abstractions, data models, and tradeoffs — and the humility to change your mind when the evidence does.
You've owned a system that went from "works for a few thousand users" to "works for millions" — and you remember exactly where it hurt.
