Engineering
in 2026

Jaume Puig, CTO @ Enginy

Enginy graphic

Agenda

1

The Shift

Why things are changing and what it means for us

2

Speed & Execution

How we move fast and scale our velocity

3

Ownership

Accountability model and fire rotation

4

Quality

Our top priority this year

5

Growth & Closing

Career alignment and next steps

01

The Shift

🤖

Why Things Are Changing

AI has fundamentally changed software development. Here's what that means for us.

👀

What I am seeing today

  • Most code is now AI-generated or AI-assisted
  • Tasks that took days now take minutes, weeks take hours
  • The barrier to writing code is collapsing
  • Background agents can work on multiple tasks in parallel
💡

What this means for us

  • Implementation alone is becoming commoditized
  • The engineering mindset matters more than ever
  • Understanding problems deeply = great engineering
  • We'll figure out workflows together
THE NEW BOTTLENECKS

Deciding

What to build

Iterating

Fast feedback loops

Maintaining

Quality while moving quickly

🔄

The Model Has Changed

💔

The old model

  • 💻 Engineer = coder
  • 📈 Value = lines of code produced
  • ⏳ Implementation is the main bottleneck
  • 🕑 Less time for problem understanding
✨

The new model

2026
  • 🤝 Engineer = problem solver (as it should be)
  • 🤖 AI handles much of the implementation
  • 🎯 Value = understanding & solving problems
  • 💡 More time to think, design, and validate
💡 The shift: AI removes the implementation bottleneck. This lets us focus on what great engineers have always done: deeply understand problems and design the right solutions.
🤖

AI Is a First-Class Teammate

AI is not a tool we occasionally use. It's a teammate we collaborate with daily.

💻

How we use AI today

  • Drafting code and PRs
  • Debugging and refactoring
  • Writing tests
  • Code reviews and documentation
  • Exploring unfamiliar codebases
🔬

What to expect

  • There is no final or perfect setup
  • Tools will keep evolving rapidly
  • We'll continuously adapt our workflows
  • Experimentation is encouraged
  • Share what works with the team
Treat agents like engineers, not chatbots. Give them tools, context, and constraints.
THE MINDSET

Direct

Be specific about what you want

Review

AI makes mistakes, you catch them

Refine

Good enough on first try is rare

Own

You're accountable, not the AI

Delegate

Let agents grind through edge cases

Parallelize

Run multiple agents at once

Share

Tell the team what works

"The bottleneck in agents isn't intelligence—it's I/O."

🧰

The AI Guild

A space for everyone to discuss, share, and learn about all things AI.

💬

What we discuss

  • New tools and workflows
  • Prompting techniques
  • Use cases and experiments
  • Troubleshooting AI issues
  • Industry news and trends
🎯

Why join

  • Stay ahead of AI developments
  • Learn from each other's experiences
  • Get help when you're stuck
  • Shape how we adopt AI as a team
  • Everyone's welcome, any skill level

Example Workflow with AI Cloud Agents

👨‍💻

Traditional Workflow

0:00h
Backlog
👨 Task 1
👨 Task 2
👨 Task 3
👨 Task 4
👨 Task 5
Coding
Review
Done
🤖

AI-Enabled Workflow

0:00h
Backlog
🤖 Task 1
🤖 Task 2
🤖 Task 3
🤖 Task 4
🤖 Task 5
AI
Review
Done
~3x faster with AI-enabled parallel workflows

02

Speed &
Execution

🏁

Speed Is the Default Mode

🏁

We aggressively compress time. These are the numbers that matter.

TARGETS

Short

< 24h

Time to PR

From picking up ticket to PR ready

Small

< 400 lines

PR Size

Easy to review & revert

Fast

< 2h

Review Turnaround

Don't block teammates

Low

0 stale PRs

Blocked Work

Unblock yourself, have agency

PRINCIPLES

⚡

Merge fast

Don't let PRs rot

📦

Ship small

Easier to review & revert

🚀

Learn by shipping

Iterate in production

📈

How We Scale Speed

Different roles, complementary focus. Together we move faster.

🚀

Team

EXECUTION

Everyone ships. Seniors drive the most impact.

  • Own and ship features end-to-end
  • High output, high quality
  • Seniors: unblock themselves and others
🛠

Tech Leads

ENABLEMENT

Enable the whole team to move faster

  • Build tools and patterns
  • Remove friction from workflows
  • Multiply team velocity
🎯

CTO

DIRECTION

Ensure we're building the right things

  • Set priorities, KPIs & direction
  • Define the framework teams operate in
  • Provide the "why" — business context
  • Direct, honest feedback
🤝 The goal: The team ships fast because Tech Leads have removed the obstacles.
🛠

DevEx Is Core

Fast DevEx = fast engineers. Every minute of friction multiplies across the team.

Strict

enforced

Type Safety

Automatic

every PR

Preview Environments

Fast

target

PR → Deploy

Happy

everyone

Team Satisfaction

FOCUS AREAS

Cursor rules

Linting & formatting

Tests

CI reliability

Fast local setup

Background agents

Tools setup (Cursor, Codex, Claude Code)

🐛

Bug SLAs Are Non-Negotiable

⚠ The commitment: When we promise a response time, we deliver. No exceptions.

SLAs are how we build trust with the business. Missing them damages credibility—not just for you, but for the whole team.

Acknowledge fast

Even if you can't fix it immediately, respond and set expectations.

Escalate early

If you're blocked or need help, raise it before the deadline—not after.

Close the loop

Communicate resolution clearly. Don't leave tickets hanging.

Remember: Our reputation is built one resolved bug at a time. Treat every SLA like a promise to a customer.

How Improvements Happen

Ideas are cheap. Prototypes matter.

Expectation

1

Identify an opportunity

Friction, improvements, new ideas, better patterns

2

Build a small PoC

Show, don't tell. A working prototype beats a proposal.

3

Share it with everyone

Get feedback from the team, iterate on ideas together.

4

Validate

Test in real conditions. Confirm it solves the problem.

5

Ship

Roll it out. Document it. Make it the new standard.

03

Ownership

Ownership Model

SENIOR+

Each Senior+ engineer owns one or more services. You are responsible for the health of your service.

📊

Monitor health

Have dashboards and metrics to track your service's health.

🔔

Clean alerts

No false positives. Every alert should be actionable.

🔧

Own the tech debt

Know what's broken and keep it visible.

🤝

Prioritize with team

Balance debt vs. roadmap with Tech Lead.

Remember: Ownership doesn't mean doing all the work yourself. You can delegate. You can ask for help. But you are accountable for your service's health.
📋

Service Ownership

PROPOSAL

Proposed ownership distribution across teams and services.

Person Team Services
Oriol Engage web/
Palo Prospect api/ (shared)
Bernat Prospect enrich/, openapi/
Miquel Engage conversation/, refresh/
Tiago Prospect api/ (shared)

Ownership ≠ Doing Everything Alone

Owning a service doesn't mean you're on your own. It means you're the point person who ensures things get done—not necessarily the one doing everything.

🤝

Delegate

Involve others. Assign tasks to the right people.

👋

Ask for help

Reach out when stuck. No one expects you to know everything.

🎯

Be accountable

You're responsible for outcomes, not just effort.

The mindset: "This is my service. I make sure it's healthy—by leading, coordinating, and getting the right people involved."
🔥

Fire Role

🔥

First responder for anything burning or breaking. Resolve urgent issues before planned work.

PRIORITIES (RANKED)

1️⃣

Incidents

Outages, degraded service, major regressions

2️⃣

Bugs

Urgent customer issues from support

3️⃣

Failing Alerts

Monitors firing, early warning signals

4️⃣

Product Work

Features, roadmap, tickets

3+ months at the company → you join the rotation

1 person per team on fire duty at a time

Weekly rotation

🔥

Fire Role = Coordination

You're the conductor, not the entire orchestra. Coordinate, don't hoard.

OPERATING PRINCIPLES

🎯

Triage First

Always confirm what is the most urgent fire right now

📢

Communicate

Update the team immediately, escalate in #incidents

🤝

Handoff

Pass context to next owner at end of shift

DO

  • Route issues to the right owner
  • Follow up until closed
  • Keep stakeholders in the loop
  • Flag recurring issues

DON'T

  • Go dark—acknowledge within 5 min
  • Fix everything yourself
  • Let tickets age—escalate if stuck
  • Assume someone else will handle it
🔔

Zero Fake Alerts Policy

The goal: Clean up fake alerts so every notification is a real issue worth investigating.

>90%

actionable

Alert Quality

Alert fires = real problem

DO

  • Fix the root cause
  • Tune thresholds for your service
  • Report noisy alerts as bugs
  • Investigate every alert

DON'T

  • Ignore alerts
  • Say "it's a known issue"
  • Leave root causes unfixed
  • Assume someone else will fix it

Why it matters: Alert fatigue kills incident response. When we ignore alerts, real issues slip through.

💎

Quality Is the Top Priority This Year

We've improved a lot this year. Let's keep the momentum going.
🐛

Fewer Bugs

  • Fix bugs fast, don't let them pile up
  • Write tests for critical paths
  • Review code thoroughly
  • Learn from production issues
💚

Healthy Services

  • Monitor what matters
  • Clean up noisy alerts
  • Own your service's health
  • No surprises in production

Why it matters: Quality enables speed. Technical debt slows everyone down—including AI.

💎

What Quality Means at Enginy

Quality is not about perfection. It's about predictability, trust, and speed.

🚀

Few surprises in production

Ship with confidence. Bugs happen, but they shouldn't be the norm.

👤

Clear ownership

Every service has an owner. Every issue has someone accountable.

✅

Confidence when deploying

Tests pass, alerts are clean, rollbacks are easy. Deploy without fear.

🤖

AI-ready systems

Clean code, clear patterns. Systems that humans and AI can work with.

⚡

Great DevEx

Fast feedback loops, smooth tooling. Happy engineers build better software.

🤝

Customer trust

Customers don't notice problems. Reliability builds long-term trust.

05

Growth &
Closing

👥

Growing the Team

2x GROWTH

Adding ~1 engineer per month throughout 2026.

9

Q1 2026

➔

20

Q4 2026

Q1 Q2 Q3 Q4
🏗 Teams 2 3 3 4
💻 Product Engineers 9 11 14 16
🎯 Tech Leads 2 3 3 4
🌟

What It Means For You

€3M → €10M is the company goal. Building the future of engineering is your opportunity.

🤖

Master AI-Native Engineering

Learn to work alongside AI as a true collaborator. This is how the best engineers will work—and you're doing it now.

📈

Scale Problems

Solve challenges that don't exist at €3M. Real growth means real engineering problems worth solving.

🛠

Better Tools

We want to invest as a company to get you the best tools, latest AI models, and cutting-edge tech.

👑

Leadership Opportunities

Growth creates roles. Step up, own more, lead teams. The path is wide open for those who want it.

🚀 The opportunity: Few engineers get to build at this pace, with these tools, at this stage. Make the most of it.
📈

Career Path Alignment

These expectations map directly to career progression. Nothing here is arbitrary.

COMPETENCIES

🚀

Ownership

Bugs, tasks, planning

🔍

Problem Solving

Systems, tooling, AI

💡

Entrepreneurial

Product, trade-offs, initiative

📊

Performance

Output, code quality

🧩

Team Integration

Collaboration, mentorship

🔗 Link: Engineering career path (Notion)

Questions?

Let's discuss