Backend Developer

Frequently Asked Questions

What is a day in the life of a Backend Developer?

• You'll build new features, fix bugs, and chip away at technical debt across the Creative Factory platform, the image and video template editors, plus the newer GenAI features (image generation, background removal).
• You'll spend most of your time on the Kotlin/Spring Boot backend, picking up React/TypeScript frontend work as you grow into it. The team is deliberately building toward full-stack coverage.
• You'll review code both ways: reading and understanding a teammate's work, and having your own reviewed in turn, so no single person is a bottleneck.
• You'll use AI coding tools daily (around 80% of what the team ships starts as AI-generated), but you'll read, understand, and take ownership of what you commit rather than shipping unreviewed output.
• You'll work in a fairly new codebase with thin documentation. The team and its tooling are only about three months old, so part of the job is exploring and piecing things together rather than following a set path.
• You'll occasionally coordinate with the Feed Team and Campaigns Team on how templates connect to catalogs and ads across Meta, Snapchat, and TikTok, and more loosely with Insights and Integration.
 

What will I need to thrive in this role?

• Solid Kotlin experience. This is the one non-negotiable. Strong Java developers open to switching are a reasonable second choice.
• Hands-on Spring Boot and PostgreSQL. jOOQ, S3-compatible storage, or Google Cloud (Cloud Run, Cloud SQL, Cloud Functions, GKE) are a genuine plus.
• Comfort with, or real interest in growing into, React/TypeScript and some Node.js. You don't need to be a frontend expert on day one.
• The ability to review AI-generated code critically. You can explain anything you commit, not just point at the fact that it works.
• A self-starter mindset. The team is small and new, so you'll often be figuring things out with the context available rather than following a playbook.
• Genuine curiosity about the product itself, the creative templates, image and video generation, not just the code behind it.
• Czech language skills, since the team works day to day in Czech. Being based in or near Brno helps but isn't required.

 

What does high performance look like?

• You ship features and fixes across both ends of the stack without needing someone else to unblock you.
• Your code reviews, given and received, catch real issues, not just style nits, and you can explain any AI-generated code you commit.
• You're comfortable owning a piece of the platform (image templates, video templates, or the GenAI layer) end to end.
• You help move the team toward unifying workflows that have historically lived in separate codebases, rather than just adding to the pile.
 

What is my potential for career growth?
As the team grows past four people, there's real room to move toward a senior, full-stack profile: owning more architecture decisions, driving the ongoing unification of the image and video codebases, and getting involved in newer initiatives like the Creative Intelligence work with Pattern's data science team. How fast that happens depends mostly on you. The team is small enough that taking on more scope is mostly a matter of being ready for it. 

 

What does success look like in the first 30, 60, 90 days?

The team and its tooling are only about three months old, so a lot of ramp-up is exploring and piecing things together rather than following existing documentation.

• First 30 days: get oriented on the backend (Kotlin, Spring Boot, PostgreSQL), since that's where the codebase and technical debt live, and start shipping small fixes with support from the team.
• By 60 days: you're picking up real backend tickets end to end and giving and receiving code reviews on that side.
• By 90 days: you're starting to branch into frontend work as your confidence grows. Nobody expects full-stack productivity this early. This is about steady progress, not a deadline.
 

What is the team like?

You will work alongside Michal (FE) and Honza (BE), and be supervised by Adam Šuba, the team's Full Stack Lead, who'll also be your closest day-to-day mentor as the most senior full-stack engineer on the team. You'll also work closely with Kamil (PM) and Danil (Designer). This team is data driven and results oriented. You will collaborate regularly with members of your team to implement actionable solutions. Ideas and input are encouraged from all members.

Sounds great! What’s the company culture?

We are looking for individuals who are:

Game Changers- A game changer is someone who looks at problems with an open mind and shares new ideas with team members, regularly reassesses existing plans and attaches a realistic timeline to goals, makes profitable, productive, and innovative contributions, and actively pursues improvements to Pattern’s processes and outcomes.

Data Fanatics- A data fanatic is someone who recognizes problems and seeks to understand them through data, draws unbiased conclusions based on data that lead to actionable solutions, and continues to track the effects of the solutions using data.

Partner Obsessed- An individual who is partner obsessed clearly explains the status of projects to partners and relies on constructive feedback, actively listens to partner’s expectations, and delivers results that exceed them, prioritizes the needs of your partners, and takes the time to create a personable experience for those interacting with Pattern.

Team of Doers- Someone who is a part of a team of doers uplifts team members and recognizes their specific contributions, takes initiative to help in any circumstance, actively contributes to supporting improvements, and holds themselves accountable to the team as well as to partners.

What is the hiring process?

• Introduction interview with our Pattern recruiting team 
• Hiring manager interview
• Short take home assignment
• Final interview with Adam and Honza 
• Offer

How can I stand out as an applicant?

Talk concretely about how you use AI coding tools day to day, not just that you use them. We ship a lot of AI-assisted code here, and what matters most is that you read, test, and can explain anything you commit.
Show real curiosity about the product itself: the creative templates, the image and video generation, not only the code behind it.
Speak specifically about Kotlin work you've owned end to end. This is the one skill we won't compromise on, so depth matters more than breadth here.
Share an example of learning a large, thinly documented system mostly on your own. Our tooling is only a few months old, so this role runs on exploration more than a set process.
Tell us if you genuinely want to grow into full stack work, and why, rather than treating frontend as something you'll tolerate.