Page 1 of 2
Help guide the future of Ref.
Background (Page 1 of 2)
.
On this page you'll be asked a few questions to better understand your perspective.
How long have you been building software professionally?
*
A
I'm just getting started.
B
1-2 years
C
2-6 years
D
6-10 years
E
10+ years
How much of your work is about making other engineers more effective?
*
A
Almost none — I'm focused on my own deliverables
B
Some — I mentor or unblock people as it comes up
C
A lot — coaching, reviewing, and unblocking others is a core part of my job
D
Most — my job is to make other engineers more effective
How do you and your team using AI coding tools today?
*
A
Each engineer uses their own tools (Cursor, Claude Code, etc.) — no team layer
B
We've standardized on one tool across the team
C
We run autonomous agents (Devin, background agents, etc.)
D
We're experimenting but nothing's stuck yet
E
We're not really using them as a team
F
Other
Looking at this list, which are the 3 biggest pains for your team?
*
Top 1
Top 2
Top 3
Not Ranked
Important engineering decisions are happening inside agent sessions that nobody can see or audit
Running multiple agents at once fries my brain — I can't track what's happening where
My team has no shared practice for reviewing specs before agents start building
Review is becoming a bottleneck — there's more code and specs landing than I can meaningfully check
Junior engineers and late adopters can't keep up with AI-fluent teammates
I lose cohesion when work sprawls across multiple PRs and multiple agents
Critical context lives in teammates' heads — my agents can't reach it
Have you seen Ref's new product? How would you describe it?
Next
