- Early StageStartup in initial stages
- Website
- Locations
- Company size
- 1-10 people
- Company type
- Information Technology
- Markets
Stepsize careers
Developer inefficiency costs $300 billion in global GDP each year.
The number 1 cause for inefficiency? Technical debt. Engineers say they could be 50% more productive.
So why do companies let technical debt get out of control?
There's a vicious cycle at play.
Engineers hate tools like Jira — they weren't designed for them. They're in the browser, and engineers spend all their time in their code editors. And you can't even attach code to issues, but that's what technical debt is all about!
So technical debt doesn't get tracked, or if it does it languishes in backlogs.
Without visibility on technical debt, engineers can't manage it. Tech debt piles up, productivity drops, and bugs creep into more and more releases.
Enter Stepsize, the engineer's frontend to issue trackers.
We let engineers interact with tools like Jira directly from their code editors. And being in the code editor, it's super easy to link code to issues, without even uploading the code itself.
That gives teams the visibility they need to break the vicious cycle.
Every engineer knows about the issues affecting their codebase thanks to inline annotations.
And during planning, it takes a couple of clicks to dig up all the issues that could impact a feature's delivery.
No more surprises. Teams can make deliberate decisions about which debt to pay back, and when.
Our customers include scale-ups like Snyk and enterprises like Sainsbury's. They address 50% of the issues they track and say they've been gifted time to work on features.
-----------------------------------------------------------------------------
This is the first step of our multi-decade mission.
Learn more by checking out one of our job descriptions.
The number 1 cause for inefficiency? Technical debt. Engineers say they could be 50% more productive.
So why do companies let technical debt get out of control?
There's a vicious cycle at play.
Engineers hate tools like Jira — they weren't designed for them. They're in the browser, and engineers spend all their time in their code editors. And you can't even attach code to issues, but that's what technical debt is all about!
So technical debt doesn't get tracked, or if it does it languishes in backlogs.
Without visibility on technical debt, engineers can't manage it. Tech debt piles up, productivity drops, and bugs creep into more and more releases.
Enter Stepsize, the engineer's frontend to issue trackers.
We let engineers interact with tools like Jira directly from their code editors. And being in the code editor, it's super easy to link code to issues, without even uploading the code itself.
That gives teams the visibility they need to break the vicious cycle.
Every engineer knows about the issues affecting their codebase thanks to inline annotations.
And during planning, it takes a couple of clicks to dig up all the issues that could impact a feature's delivery.
No more surprises. Teams can make deliberate decisions about which debt to pay back, and when.
Our customers include scale-ups like Snyk and enterprises like Sainsbury's. They address 50% of the issues they track and say they've been gifted time to work on features.
-----------------------------------------------------------------------------
This is the first step of our multi-decade mission.
Learn more by checking out one of our job descriptions.
Backend Engineer (Editors)
Remote only • London
£65k – £75k • 0.2% – 0.3%Senior Backend Engineer (API)
Remote only • London
£80k – £90k • 0.3% – 0.4%Senior Backend Engineer (Editors)
Remote only • London
£80k – £90k • 0.3% – 0.4%Lead Engineer
Remote only • London
£90k – £100k • 0.4% – 0.5%Jared Burgess
Co-founder @Stepsize, Design & Frontend Engineering
Matthieu Louis
Co-founder & CTO @Stepsize
Nick Omeyer
Co-founder & CPO @Stepsize
We help teams tackle the number 1 cause for developer inefficiency: technical debt.
Engineers say they could be 50% more productive. We're building the tools and defining the best practices to get them there.