We are not hiring right now. The door is still open.
Effective date · 1 June 2026
PulseSignal is a small, deliberate team building competitive intelligence infrastructure for SaaS operators. We expand headcount only when revenue makes it responsible to do so. Until then, this page exists to be honest about that — and to leave the door open for the kind of cold inbound that has historically built the best teams.
Current status.
- We are pre-Series-A and revenue-focused. Headcount expansion happens after MRR justifies it.
- When roles open, they will be posted here first, then on LinkedIn and Hacker News "Who is hiring".
- There is no waitlist, no "future roles" form, no candidate pool. Cold inbound is the channel.
How we work
Principles, not slogans.
Ship something true, not something loud.
We publish what we can defend with public sources, then make it useful. Marketing claims have to match what the product actually does.
Small team, full ownership.
Everyone here owns a vertical end-to-end — backend pipeline, frontend surface, customer conversation, runbook. No throw-it-over-the-wall.
Boring stack, sharp instincts.
Python + asyncio + Postgres + Next.js. Nothing exotic. We optimise for owner-operator readability over framework novelty.
Customer-paid before VC-paid.
We charge real money for real work and let customer revenue dictate the roadmap.
Operate in public.
Public changelog, public roadmap, public security policy, public status. The same document customers see is the document we work from.
What we look for
When the door opens, this is the signal.
- You have shipped something that real strangers paid for — open-source or commercial — and can talk about the trade-offs you made.
- You write code that another operator can read at 3 a.m. during an incident without needing you online.
- You have a strong opinion about either (a) scraping resilience at scale or (b) frontend information density, and you can defend it.
- You can hold a one-hour technical conversation in writing without burying the point.
- You are comfortable working asynchronously across timezones, with deep-work blocks and minimal meetings.
Role archetypes
The roles we expect to open first.
These are not active requisitions — we are not hiring today. They are the role archetypes the team has agreed map to the next stages of the company. Cold inbound that maps clearly onto one of these gets faster signal back from us.
Senior backend engineer · Python / asyncio / Postgres
EngineeringOwns the data ingest + scoring pipeline end-to-end (391 patterns, 14 cluster workers, nightly Stage1 cycle). Comfortable reading APScheduler internals, asyncpg cancellation semantics, and writing pytest with real Postgres.
Responsibilities
- Own a vertical slice of the ingestion pipeline (e.g. funding signals, hiring deltas, certification gains) from source to scored candidate.
- Write defensive async code that survives provider rate-limits, partial network failures, and worker-pool exhaustion.
- Author runbooks for the surface you own so anyone on-call can recover without paging you.
- Cut SQL that runs in production unchanged — read EXPLAIN plans, add the right indexes, drop the wrong ones.
Qualifications
- 5+ years building production Python systems with asyncio + Postgres at non-trivial scale.
- You have shipped a system that handles ≥1M records/day or ≥100 concurrent network requests, and you can describe the failure modes you fixed.
- Comfortable with the boring stack: no exotic frameworks, no microservice rewrite urges.
Senior frontend engineer · Next.js / TypeScript / Tailwind
EngineeringOwns the customer-facing surface (marketing + dashboard, Cloudflare Pages + Hetzner). Cares about information density, accessibility, and the difference between a working page and a trustworthy one.
Responsibilities
- Ship dashboard surfaces that compress real signal into one screen without scroll fatigue.
- Maintain the marketing site so promise-literal-match stays at 100% (every claim matches a shipped feature).
- Own bundle-size, Core Web Vitals, and accessibility (WCAG 2.2 AA) — measurably, not aspirationally.
- Write vitest contract locks for every surface so refactors stay safe.
Qualifications
- 5+ years shipping production Next.js (or React) at customer-facing scale.
- Strong opinions about information density, error states, and empty states — and you can defend them in writing.
- Comfortable with Tailwind, server components, and the App Router. You read the Next.js GitHub issues so we do not have to.
Founding account executive · SaaS / mid-market
SalesFirst sales hire. Owns the inbound + outbound pipeline for mid-market SaaS customers ($25–250k ARR). Builds the playbook from zero, including discovery script, objection handling, and the qualification framework.
Responsibilities
- Run discovery calls with VPs of Product Marketing, RevOps, and Competitive Intelligence at SaaS companies.
- Document every objection, every won-deal pattern, every lost-deal reason — the playbook is an artefact, not tribal knowledge.
- Partner with engineering to translate "what customers actually ask for" into roadmap inputs.
- Hit a quota proportional to the price point and conversion data we can show on day one.
Qualifications
- 4+ years closing SaaS deals in the $25–250k ARR band at a category-creating company.
- You have built a sales playbook from scratch before, not just executed someone else's.
- Comfortable selling to technical buyers who will read the changelog before the demo.
Growth marketer · technical / content-led
MarketingOwns the inbound funnel. Writes long-form technical content that the target buyer would forward to a peer, runs distribution, and measures with PostHog funnels.
Responsibilities
- Ship two long-form posts per month that a Director of Product Marketing would actually save.
- Own the SEO surface — keyword landscape, internal linking, schema, page speed — without crossing into spam.
- Run distribution loops: launch partners, founder podcasts, HN/Reddit/LinkedIn organic, paid only after organic is proven.
- Measure activation events from organic to paid in PostHog and report weekly on the conversion bottleneck.
Qualifications
- 3+ years owning a content-led growth motion at a SaaS company selling to technical buyers.
- Writing samples that show you can explain a hard concept simply without dumbing it down.
- Comfortable in Google Search Console, PostHog, and ahrefs/Semrush.
Customer success engineer · founding
Customer SuccessFirst post-sales hire. Owns onboarding, configuration help, escalation triage, and the customer-facing portion of the changelog. The trust surface customers see between sales and engineering.
Responsibilities
- Run hands-on onboarding for every new customer — first briefing configured, first alert wired, first integration live.
- Triage support tickets within 1 business day; escalate to engineering with reproducible repros.
- Maintain the help centre + changelog snippets so the same answer never has to be typed twice.
- Surface product gaps and customer-quoted feedback into the weekly engineering review.
Qualifications
- 3+ years in technical customer success or solutions engineering at a SaaS company with a technical buyer.
- You can read enough Python or SQL to triage a customer integration without paging engineering for every question.
- Empathy that survives a 6am incident — and the writing discipline to document the root cause afterwards.
How to reach out
Skip the resume.
- Email careers@pulsesignal.co with the subject line "Cold inbound · <your-name>". One paragraph on what you want to build and one link to the most interesting thing you have shipped.
- No resumes required. We will read a GitHub profile, a long-form essay, a take-home you already wrote, or a product you sell — whichever shows the most signal.
- We respond to every cold inbound within 7 days, even if the answer is "not right now". A polite no is still a reply.
- If we are interested we move to a paid, scoped take-home (8 hours, paid at market rate) before any structured interview loop.
Interview process
Five stages, ≤14 calendar days end-to-end.
Every stage tells you why it exists. We share the rubric we are scoring against before you walk into it. If we miss an SLA we send you a status update with the new ETA before the deadline lapses.
Stage 1 · Written intro (async, 24h ack)
You email careers@pulsesignal.co. We acknowledge within 24 hours and reply with a substantive yes/no/maybe within 7 calendar days. A polite no is still a reply.
Candidate time: ~30 minutes (one email)
Stage 2 · 30-minute video conversation
A working session — not a behavioural interview. You walk us through a problem you have solved and we talk trade-offs. We tell you what we are working on now and where the work would fit.
Candidate time: 30 minutes
Stage 3 · Paid scoped take-home
An 8-hour, real-shape problem from the surface you would own. Paid at market rate ($150/hr) regardless of outcome. You own the IP; we own a single read-only review pass. Submission window is 7 days so you can fit it around your existing job.
Candidate time: ~8 hours over 7 days
Stage 4 · Take-home review + system-design conversation
90 minutes. First half: we walk through your submission together and you defend the trade-offs. Second half: a system-design conversation grounded in something adjacent to what you would build here.
Candidate time: 90 minutes
Stage 5 · References + offer
Two reference conversations (someone who has shipped code with you + someone you have managed or been managed by). Written offer within 5 business days of references clearing. Two-week consideration window, no exploding offers.
Candidate time: ~1 hour (you make the intros; we do the calls)
Our commitments to candidates.
- Total time from first email to offer is ≤14 calendar days. We do not slow-roll candidates.
- Every stage tells you why it exists. If you ever do not know why we are running a particular step, ask — we owe you a clear answer.
- No trick questions, no whiteboard algorithms in front of an interviewer, no "tell me about a time" behavioural rounds. We optimise for "would this person ship what they say they will ship?".
- We share scorecard rubrics with you before each stage. The same rubric you saw is the rubric we score against.
- Anti-ghosting commitment: if any stage exceeds its SLA, we send you a status update with the new ETA before the deadline lapses.
Equal opportunity
We hire on demonstrated work.
PulseSignal does not discriminate on the basis of race, colour, religion, sex, sexual orientation, gender identity, national origin, age, disability, veteran status, or any other characteristic protected by law. We hire on demonstrated work, written reasoning, and ability to operate with autonomy.
If you need a reasonable accommodation for any part of the application process, email careers@pulsesignal.co and we will work with you.
Reach out anyway.
Email careers@pulsesignal.co with subject line "Cold inbound · <your-name>". Tell us what you want to build and link to the most interesting thing you have already shipped. We respond within 7 days, even if the answer is "not right now".
This page is reviewed when our hiring posture changes. If you are reading it, the status above is current.