Help us build the monitoring layer the internet is missing
We're a small, remote team obsessed with catching silent failures before they hurt businesses. If that resonates with you, we'd love to hear from you.
A small team working on a real problem
We're not building another dashboard. We're building the layer that tells you when something critical breaks silently — the gap every team has but most tools ignore.
Fully remote
Work from anywhere. We're async-first and trust you to manage your own time and focus.
Early-stage equity
Join early. Your work directly shapes the product and your equity reflects that.
Deep ownership
No bureaucracy. You own your work end to end — from idea to shipped feature.
Real impact
When NotiLens catches a silent failure, someone's business doesn't lose revenue. That's what we ship.
Current openings
We hire for craft, curiosity, and care. Every role here has real scope — you won't be doing tickets forever.
The things we actually believe
Not a list of perks. The principles that shape how we build and how we work together.
Silence is a signal — in code and in teams
We say what we mean, flag problems early, and don't let things go quiet when they shouldn't. The same principle that drives the product drives how we communicate.
Ship with care, not speed
We'd rather ship something solid that customers trust than something fast that they have to work around. Quality is the feature.
Context over process
We don't have playbooks for everything. We share context, trust each other's judgment, and expect everyone to make good calls with the information they have.
Small team, big scope
Everyone works across the whole problem. There are no lanes that turn into silos. If something matters, it's someone's job — and that someone might be you.
Don't see your role? Send us a note anyway.
We're a small team. We sometimes hire for roles we haven't written a job description for yet. If you're genuinely excited about what we're building, the best thing you can do is tell us what you'd own.
Who you are — in two sentences
Your background, what you've built or contributed to, and what kind of work energizes you. Skip the objective statement.
What you'd own at NotiLens
Not "I'd love to contribute to your mission." Tell us the specific thing you'd work on — a feature, a system, a channel, a problem. Be concrete.
Why NotiLens specifically
What resonates about the problem we're solving? The more specific, the better — generic enthusiasm doesn't tell us much.
Links to your work
GitHub, portfolio, writing, side projects — anything that shows how you think and what you build. No work samples required, but they help.
Build something that genuinely helps.
We read every application. If there's a fit — now or later — we'll reach out.
[email protected]