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
💡

What this means for us

  • Engineering is becoming commoditized
  • We need to think more like product managers
  • Understanding the problem > writing the code
  • 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

  • 📝 PM defines what to build
  • 💻 Engineer writes the code
  • 📈 Value = lines of code produced
  • 📚 Deep specialization in implementation
✨

The new model

2026
  • 🤝 We are closer to product than ever
  • 🤖 AI handles much of the implementation
  • 🎯 Value = understanding & solving problems
  • 🚀 Everyone thinks in terms of outcomes
💡 The shift: When AI can write code, your value comes from knowing what to build and why it matters.
🤖

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
THE MINDSET

Direct

Guide AI with clear intent

Review

Always verify the output

Refine

Iterate until it's right

02

Speed &
Execution

🏁

Speed Is the Default Mode

🏁

We aggressively compress time. Engineers optimize what you measure.

TARGETS

Short

Lead Time

Commit → Merged

Small

Batch Size

Reviewable changes

Fast

Cycle Time

Quick feedback loops

Low

WIP

Focus on finishing

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.

🚀

Seniors

EXECUTION

Drive impact and delivery

  • Own and ship features end-to-end
  • High output, high quality
  • 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
🤝 The goal: Seniors ship fast because Tech Leads have removed the obstacles.
🛠

DevEx Is Mandatory

🔥 The rule: If something slows you down more than twice, it's a bug. Fix it or report it.
🎯

Targets

  • Fast local setup
  • Quick CI pipeline
  • Zero flaky tests
📊

Accountability

  • Every quarter: ship DevEx improvements
  • Tech Leads measured on velocity gains
  • DX issues = high priority bugs
FOCUS AREAS

Cursor rules

Linting & formatting

Tests

CI reliability

Fast local setup

🐛

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.

🔔

Clean alerts

No false positives, no ignored alerts. Every alert should be actionable.

🔧

Own the tech debt

Know what's broken, what needs fixing, and keep it visible to the team.

🤝

Prioritize with the team

Work with Tech Lead and team to balance debt vs. roadmap priorities.

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/
Bernat Prospect enrich/
Miquel Engage conversation/, refresh/
Tiago Prospect openapi/

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 Rotation

🔥

Everyone with more than 3 months in the company joins the rotation.

💡 This is how the rest of the company interacts with us.
It shapes how people see engineering. Quality here = trust in the team.

Responsibilities

Handle incidents

Be the first responder when things break

Handle tickets

Triage and route incoming requests

Communicate fast

Keep stakeholders informed

🔥

Fire Role = Coordination

The fire role is about coordination, not fixing everything yourself. You're the conductor, not the entire orchestra.

1

Delegate to the right person

Route issues to service owners or the right team member. Don't try to fix everything yourself.

2

Follow up until resolution

Own the thread. Make sure nothing falls through the cracks.

3

Continuous improvement

We will track quality and response time to keep getting better.

💎

Quality Is the Top Priority This Year

Quality enables speed. Technical debt slows everyone down—including AI.

FOCUS AREAS

🧱

Strong primitives

Reliable building blocks we can trust

🎨

Solid design system

Consistent UI that scales

⚙

Predictable systems

No surprises in production

HOW WE GET THERE

Code reviews

Peer validation

Observability

Logs, metrics, traces

Documentation

AI-ready codebases

Consistent patterns

Standard approaches

Debt cleanup

Regular refactoring

💎

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.

05

Growth &
Closing

🌟

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