Teya Engineering

Teya builds payments, business accounts, and funding for small businesses across Europe. A card machine on the counter of a bakery. Instant settlement for a barber shop on a Friday night. An account that handles the boring parts of the books so the owner can go home.

More than 75,000 businesses run on what we build. Real money, in real time, with no good day to be down. That sets the bar for the software behind it.

This is where we share the parts of that work we think are useful to everyone else.

We run a lot of services, and we would rather they were boring. The interesting part of a payments platform should be the payments, not the plumbing.

The JVM does the heavy lifting. Java and Kotlin on Spring Boot for most services, always on latest versions.
Events over calls. Kafka carries most of what moves between services, with schemas that are versioned and checked before anything ships.
Postgres until it hurts. Then we partition it. We are slow to add a new datastore and quick to lean on the one we know.
AWS and Kubernetes underneath. That is where our services run and where the platform team invests, so it is where new services should run too.
If we cannot see it, it is not done. Metrics, logs, and traces are part of the change, not a follow-up ticket.
Small pull requests, reviewed by humans. They are easier to reason about, and much easier to roll back at 2am.
There is a paved road, and we stay on it. We optimise for boring.

The technical choices above only hold up because of how the teams around them work. These are our engineering tenets.

🚀 Extreme ownership
- Own your system end to end, from design through production and beyond.
- Improve what you built without being asked, and raise the bar as you go.
- Fix problems at the root so the same mistake does not come back.
💥 Measure yourself on impact, not effort
- Understand why a thing is being built, not just how.
- Part engineer, part product thinker, part project driver.
- If describing, documenting, or tracking a change takes longer than making it, just make it.
🔄 Respond to change over following a plan
- New requirements and new information are welcome, not a setback.
- Plan enough to move forward with confidence, and be ready to change direction when it makes sense.
️🔨 Prefer simplicity over perfection
- The simple thing that ships and can be changed later beats the perfect thing still being designed.
✨ AI first
- Reach for AI by default in how we work, and expect what that means to keep changing.
🪞 Radical transparency and communication
- Work in the open.
- Backlogs, discussions, and retrospectives are there for anyone to read.
- Share the wins and the failures, and make room for the people who share.
🌱 Own your growth
- Seek out knowledge, try new tools, make time to get better. Nobody will do it for you.
- Be part of the engineering community here: share what you know, ask questions, stay curious about what others are doing.
🎯 Prioritise with judgement
- We care about quality and the long term, and we also need steady, imperfect progress.
- Finding the line between one deep focus and a thousand spinning plates is the job.
🎉 Have fun
- We spend a large part of our lives doing this. It should be worth showing up for.

_{Made by the engineers at Teya.}

Teya builds payments, business accounts, and funding for small businesses across Europe. A card machine on the counter of a bakery. Instant settlement for a barber shop on a Friday night. An account that handles the boring parts of the books so the owner can go home.

More than 75,000 businesses run on what we build. Real money, in real time, with no good day to be down. That sets the bar for the software behind it.

This is where we share the parts of that work we think are useful to everyone else.

We run a lot of services, and we would rather they were boring. The interesting part of a payments platform should be the payments, not the plumbing.

The JVM does the heavy lifting. Java and Kotlin on Spring Boot for most services, always on latest versions.
Events over calls. Kafka carries most of what moves between services, with schemas that are versioned and checked before anything ships.
Postgres until it hurts. Then we partition it. We are slow to add a new datastore and quick to lean on the one we know.
AWS and Kubernetes underneath. That is where our services run and where the platform team invests, so it is where new services should run too.
If we cannot see it, it is not done. Metrics, logs, and traces are part of the change, not a follow-up ticket.
Small pull requests, reviewed by humans. They are easier to reason about, and much easier to roll back at 2am.
There is a paved road, and we stay on it. We optimise for boring.

The technical choices above only hold up because of how the teams around them work. These are our engineering tenets.

🚀 Extreme ownership
- Own your system end to end, from design through production and beyond.
- Improve what you built without being asked, and raise the bar as you go.
- Fix problems at the root so the same mistake does not come back.
💥 Measure yourself on impact, not effort
- Understand why a thing is being built, not just how.
- Part engineer, part product thinker, part project driver.
- If describing, documenting, or tracking a change takes longer than making it, just make it.
🔄 Respond to change over following a plan
- New requirements and new information are welcome, not a setback.
- Plan enough to move forward with confidence, and be ready to change direction when it makes sense.
️🔨 Prefer simplicity over perfection
- The simple thing that ships and can be changed later beats the perfect thing still being designed.
✨ AI first
- Reach for AI by default in how we work, and expect what that means to keep changing.
🪞 Radical transparency and communication
- Work in the open.
- Backlogs, discussions, and retrospectives are there for anyone to read.
- Share the wins and the failures, and make room for the people who share.
🌱 Own your growth
- Seek out knowledge, try new tools, make time to get better. Nobody will do it for you.
- Be part of the engineering community here: share what you know, ask questions, stay curious about what others are doing.
🎯 Prioritise with judgement
- We care about quality and the long term, and we also need steady, imperfect progress.
- Finding the line between one deep focus and a thousand spinning plates is the job.
🎉 Have fun
- We spend a large part of our lives doing this. It should be worth showing up for.

_{Made by the engineers at Teya.}

Teya builds payments, business accounts, and funding for small businesses across Europe. A card machine on the counter of a bakery. Instant settlement for a barber shop on a Friday night. An account that handles the boring parts of the books so the owner can go home.

More than 75,000 businesses run on what we build. Real money, in real time, with no good day to be down. That sets the bar for the software behind it.

This is where we share the parts of that work we think are useful to everyone else.

We run a lot of services, and we would rather they were boring. The interesting part of a payments platform should be the payments, not the plumbing.

The JVM does the heavy lifting. Java and Kotlin on Spring Boot for most services, always on latest versions.
Events over calls. Kafka carries most of what moves between services, with schemas that are versioned and checked before anything ships.
Postgres until it hurts. Then we partition it. We are slow to add a new datastore and quick to lean on the one we know.
AWS and Kubernetes underneath. That is where our services run and where the platform team invests, so it is where new services should run too.
If we cannot see it, it is not done. Metrics, logs, and traces are part of the change, not a follow-up ticket.
Small pull requests, reviewed by humans. They are easier to reason about, and much easier to roll back at 2am.
There is a paved road, and we stay on it. We optimise for boring.

The technical choices above only hold up because of how the teams around them work. These are our engineering tenets.

🚀 Extreme ownership
- Own your system end to end, from design through production and beyond.
- Improve what you built without being asked, and raise the bar as you go.
- Fix problems at the root so the same mistake does not come back.
💥 Measure yourself on impact, not effort
- Understand why a thing is being built, not just how.
- Part engineer, part product thinker, part project driver.
- If describing, documenting, or tracking a change takes longer than making it, just make it.
🔄 Respond to change over following a plan
- New requirements and new information are welcome, not a setback.
- Plan enough to move forward with confidence, and be ready to change direction when it makes sense.
️🔨 Prefer simplicity over perfection
- The simple thing that ships and can be changed later beats the perfect thing still being designed.
✨ AI first
- Reach for AI by default in how we work, and expect what that means to keep changing.
🪞 Radical transparency and communication
- Work in the open.
- Backlogs, discussions, and retrospectives are there for anyone to read.
- Share the wins and the failures, and make room for the people who share.
🌱 Own your growth
- Seek out knowledge, try new tools, make time to get better. Nobody will do it for you.
- Be part of the engineering community here: share what you know, ask questions, stay curious about what others are doing.
🎯 Prioritise with judgement
- We care about quality and the long term, and we also need steady, imperfect progress.
- Finding the line between one deep focus and a thousand spinning plates is the job.
🎉 Have fun
- We spend a large part of our lives doing this. It should be worth showing up for.

_{Made by the engineers at Teya.}

Teya builds payments, business accounts, and funding for small businesses across Europe. A card machine on the counter of a bakery. Instant settlement for a barber shop on a Friday night. An account that handles the boring parts of the books so the owner can go home.

More than 75,000 businesses run on what we build. Real money, in real time, with no good day to be down. That sets the bar for the software behind it.

This is where we share the parts of that work we think are useful to everyone else.

We run a lot of services, and we would rather they were boring. The interesting part of a payments platform should be the payments, not the plumbing.

The JVM does the heavy lifting. Java and Kotlin on Spring Boot for most services, always on latest versions.
Events over calls. Kafka carries most of what moves between services, with schemas that are versioned and checked before anything ships.
Postgres until it hurts. Then we partition it. We are slow to add a new datastore and quick to lean on the one we know.
AWS and Kubernetes underneath. That is where our services run and where the platform team invests, so it is where new services should run too.
If we cannot see it, it is not done. Metrics, logs, and traces are part of the change, not a follow-up ticket.
Small pull requests, reviewed by humans. They are easier to reason about, and much easier to roll back at 2am.
There is a paved road, and we stay on it. We optimise for boring.

The technical choices above only hold up because of how the teams around them work. These are our engineering tenets.

🚀 Extreme ownership
- Own your system end to end, from design through production and beyond.
- Improve what you built without being asked, and raise the bar as you go.
- Fix problems at the root so the same mistake does not come back.
💥 Measure yourself on impact, not effort
- Understand why a thing is being built, not just how.
- Part engineer, part product thinker, part project driver.
- If describing, documenting, or tracking a change takes longer than making it, just make it.
🔄 Respond to change over following a plan
- New requirements and new information are welcome, not a setback.
- Plan enough to move forward with confidence, and be ready to change direction when it makes sense.
️🔨 Prefer simplicity over perfection
- The simple thing that ships and can be changed later beats the perfect thing still being designed.
✨ AI first
- Reach for AI by default in how we work, and expect what that means to keep changing.
🪞 Radical transparency and communication
- Work in the open.
- Backlogs, discussions, and retrospectives are there for anyone to read.
- Share the wins and the failures, and make room for the people who share.
🌱 Own your growth
- Seek out knowledge, try new tools, make time to get better. Nobody will do it for you.
- Be part of the engineering community here: share what you know, ask questions, stay curious about what others are doing.
🎯 Prioritise with judgement
- We care about quality and the long term, and we also need steady, imperfect progress.
- Finding the line between one deep focus and a thousand spinning plates is the job.
🎉 Have fun
- We spend a large part of our lives doing this. It should be worth showing up for.

_{Made by the engineers at Teya.}

Teya builds payments, business accounts, and funding for small businesses across Europe. A card machine on the counter of a bakery. Instant settlement for a barber shop on a Friday night. An account that handles the boring parts of the books so the owner can go home.

More than 75,000 businesses run on what we build. Real money, in real time, with no good day to be down. That sets the bar for the software behind it.

This is where we share the parts of that work we think are useful to everyone else.

We run a lot of services, and we would rather they were boring. The interesting part of a payments platform should be the payments, not the plumbing.

The JVM does the heavy lifting. Java and Kotlin on Spring Boot for most services, always on latest versions.
Events over calls. Kafka carries most of what moves between services, with schemas that are versioned and checked before anything ships.
Postgres until it hurts. Then we partition it. We are slow to add a new datastore and quick to lean on the one we know.
AWS and Kubernetes underneath. That is where our services run and where the platform team invests, so it is where new services should run too.
If we cannot see it, it is not done. Metrics, logs, and traces are part of the change, not a follow-up ticket.
Small pull requests, reviewed by humans. They are easier to reason about, and much easier to roll back at 2am.
There is a paved road, and we stay on it. We optimise for boring.

The technical choices above only hold up because of how the teams around them work. These are our engineering tenets.

🚀 Extreme ownership
- Own your system end to end, from design through production and beyond.
- Improve what you built without being asked, and raise the bar as you go.
- Fix problems at the root so the same mistake does not come back.
💥 Measure yourself on impact, not effort
- Understand why a thing is being built, not just how.
- Part engineer, part product thinker, part project driver.
- If describing, documenting, or tracking a change takes longer than making it, just make it.
🔄 Respond to change over following a plan
- New requirements and new information are welcome, not a setback.
- Plan enough to move forward with confidence, and be ready to change direction when it makes sense.
️🔨 Prefer simplicity over perfection
- The simple thing that ships and can be changed later beats the perfect thing still being designed.
✨ AI first
- Reach for AI by default in how we work, and expect what that means to keep changing.
🪞 Radical transparency and communication
- Work in the open.
- Backlogs, discussions, and retrospectives are there for anyone to read.
- Share the wins and the failures, and make room for the people who share.
🌱 Own your growth
- Seek out knowledge, try new tools, make time to get better. Nobody will do it for you.
- Be part of the engineering community here: share what you know, ask questions, stay curious about what others are doing.
🎯 Prioritise with judgement
- We care about quality and the long term, and we also need steady, imperfect progress.
- Finding the line between one deep focus and a thousand spinning plates is the job.
🎉 Have fun
- We spend a large part of our lives doing this. It should be worth showing up for.

_{Made by the engineers at Teya.}

Teya builds payments, business accounts, and funding for small businesses across Europe. A card machine on the counter of a bakery. Instant settlement for a barber shop on a Friday night. An account that handles the boring parts of the books so the owner can go home.

More than 75,000 businesses run on what we build. Real money, in real time, with no good day to be down. That sets the bar for the software behind it.

This is where we share the parts of that work we think are useful to everyone else.

We run a lot of services, and we would rather they were boring. The interesting part of a payments platform should be the payments, not the plumbing.

The JVM does the heavy lifting. Java and Kotlin on Spring Boot for most services, always on latest versions.
Events over calls. Kafka carries most of what moves between services, with schemas that are versioned and checked before anything ships.
Postgres until it hurts. Then we partition it. We are slow to add a new datastore and quick to lean on the one we know.
AWS and Kubernetes underneath. That is where our services run and where the platform team invests, so it is where new services should run too.
If we cannot see it, it is not done. Metrics, logs, and traces are part of the change, not a follow-up ticket.
Small pull requests, reviewed by humans. They are easier to reason about, and much easier to roll back at 2am.
There is a paved road, and we stay on it. We optimise for boring.

The technical choices above only hold up because of how the teams around them work. These are our engineering tenets.

🚀 Extreme ownership
- Own your system end to end, from design through production and beyond.
- Improve what you built without being asked, and raise the bar as you go.
- Fix problems at the root so the same mistake does not come back.
💥 Measure yourself on impact, not effort
- Understand why a thing is being built, not just how.
- Part engineer, part product thinker, part project driver.
- If describing, documenting, or tracking a change takes longer than making it, just make it.
🔄 Respond to change over following a plan
- New requirements and new information are welcome, not a setback.
- Plan enough to move forward with confidence, and be ready to change direction when it makes sense.
️🔨 Prefer simplicity over perfection
- The simple thing that ships and can be changed later beats the perfect thing still being designed.
✨ AI first
- Reach for AI by default in how we work, and expect what that means to keep changing.
🪞 Radical transparency and communication
- Work in the open.
- Backlogs, discussions, and retrospectives are there for anyone to read.
- Share the wins and the failures, and make room for the people who share.
🌱 Own your growth
- Seek out knowledge, try new tools, make time to get better. Nobody will do it for you.
- Be part of the engineering community here: share what you know, ask questions, stay curious about what others are doing.
🎯 Prioritise with judgement
- We care about quality and the long term, and we also need steady, imperfect progress.
- Finding the line between one deep focus and a thousand spinning plates is the job.
🎉 Have fun
- We spend a large part of our lives doing this. It should be worth showing up for.

_{Made by the engineers at Teya.}

Teya builds payments, business accounts, and funding for small businesses across Europe. A card machine on the counter of a bakery. Instant settlement for a barber shop on a Friday night. An account that handles the boring parts of the books so the owner can go home.

More than 75,000 businesses run on what we build. Real money, in real time, with no good day to be down. That sets the bar for the software behind it.

This is where we share the parts of that work we think are useful to everyone else.

We run a lot of services, and we would rather they were boring. The interesting part of a payments platform should be the payments, not the plumbing.

The JVM does the heavy lifting. Java and Kotlin on Spring Boot for most services, always on latest versions.
Events over calls. Kafka carries most of what moves between services, with schemas that are versioned and checked before anything ships.
Postgres until it hurts. Then we partition it. We are slow to add a new datastore and quick to lean on the one we know.
AWS and Kubernetes underneath. That is where our services run and where the platform team invests, so it is where new services should run too.
If we cannot see it, it is not done. Metrics, logs, and traces are part of the change, not a follow-up ticket.
Small pull requests, reviewed by humans. They are easier to reason about, and much easier to roll back at 2am.
There is a paved road, and we stay on it. We optimise for boring.

The technical choices above only hold up because of how the teams around them work. These are our engineering tenets.

🚀 Extreme ownership
- Own your system end to end, from design through production and beyond.
- Improve what you built without being asked, and raise the bar as you go.
- Fix problems at the root so the same mistake does not come back.
💥 Measure yourself on impact, not effort
- Understand why a thing is being built, not just how.
- Part engineer, part product thinker, part project driver.
- If describing, documenting, or tracking a change takes longer than making it, just make it.
🔄 Respond to change over following a plan
- New requirements and new information are welcome, not a setback.
- Plan enough to move forward with confidence, and be ready to change direction when it makes sense.
️🔨 Prefer simplicity over perfection
- The simple thing that ships and can be changed later beats the perfect thing still being designed.
✨ AI first
- Reach for AI by default in how we work, and expect what that means to keep changing.
🪞 Radical transparency and communication
- Work in the open.
- Backlogs, discussions, and retrospectives are there for anyone to read.
- Share the wins and the failures, and make room for the people who share.
🌱 Own your growth
- Seek out knowledge, try new tools, make time to get better. Nobody will do it for you.
- Be part of the engineering community here: share what you know, ask questions, stay curious about what others are doing.
🎯 Prioritise with judgement
- We care about quality and the long term, and we also need steady, imperfect progress.
- Finding the line between one deep focus and a thousand spinning plates is the job.
🎉 Have fun
- We spend a large part of our lives doing this. It should be worth showing up for.

_{Made by the engineers at Teya.}

Teya builds payments, business accounts, and funding for small businesses across Europe. A card machine on the counter of a bakery. Instant settlement for a barber shop on a Friday night. An account that handles the boring parts of the books so the owner can go home.

More than 75,000 businesses run on what we build. Real money, in real time, with no good day to be down. That sets the bar for the software behind it.

This is where we share the parts of that work we think are useful to everyone else.

We run a lot of services, and we would rather they were boring. The interesting part of a payments platform should be the payments, not the plumbing.

The JVM does the heavy lifting. Java and Kotlin on Spring Boot for most services, always on latest versions.
Events over calls. Kafka carries most of what moves between services, with schemas that are versioned and checked before anything ships.
Postgres until it hurts. Then we partition it. We are slow to add a new datastore and quick to lean on the one we know.
AWS and Kubernetes underneath. That is where our services run and where the platform team invests, so it is where new services should run too.
If we cannot see it, it is not done. Metrics, logs, and traces are part of the change, not a follow-up ticket.
Small pull requests, reviewed by humans. They are easier to reason about, and much easier to roll back at 2am.
There is a paved road, and we stay on it. We optimise for boring.

The technical choices above only hold up because of how the teams around them work. These are our engineering tenets.

🚀 Extreme ownership
- Own your system end to end, from design through production and beyond.
- Improve what you built without being asked, and raise the bar as you go.
- Fix problems at the root so the same mistake does not come back.
💥 Measure yourself on impact, not effort
- Understand why a thing is being built, not just how.
- Part engineer, part product thinker, part project driver.
- If describing, documenting, or tracking a change takes longer than making it, just make it.
🔄 Respond to change over following a plan
- New requirements and new information are welcome, not a setback.
- Plan enough to move forward with confidence, and be ready to change direction when it makes sense.
️🔨 Prefer simplicity over perfection
- The simple thing that ships and can be changed later beats the perfect thing still being designed.
✨ AI first
- Reach for AI by default in how we work, and expect what that means to keep changing.
🪞 Radical transparency and communication
- Work in the open.
- Backlogs, discussions, and retrospectives are there for anyone to read.
- Share the wins and the failures, and make room for the people who share.
🌱 Own your growth
- Seek out knowledge, try new tools, make time to get better. Nobody will do it for you.
- Be part of the engineering community here: share what you know, ask questions, stay curious about what others are doing.
🎯 Prioritise with judgement
- We care about quality and the long term, and we also need steady, imperfect progress.
- Finding the line between one deep focus and a thousand spinning plates is the job.
🎉 Have fun
- We spend a large part of our lives doing this. It should be worth showing up for.

_{Made by the engineers at Teya.}

Uh oh!

Uh oh!

Popular repositories Loading

Repositories

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

People

Top languages

Uh oh!

Most used topics

Uh oh!

Uh oh!

Uh oh!

Popular repositories Loading

Repositories

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

People

Top languages

Uh oh!

Most used topics

Uh oh!

Uh oh!

Uh oh!

Popular repositories Loading

Repositories

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

People

Top languages

Uh oh!

Most used topics

Uh oh!

Uh oh!

Uh oh!

Popular repositories Loading

Repositories

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

People

Top languages

Uh oh!

Most used topics

Uh oh!

Uh oh!

Uh oh!

Popular repositories Loading

Repositories

Uh oh!

Uh oh!

Uh oh!

Uh oh!