<aside> ๐Ÿ™Œ Mission The job of an architect is hard. Accountable for multi-million construction projects, they need to wear different hats: creative draftsmen, material specialists, detailed planers, excel professional and more. To manage the cost side of projects, they spend hours searching, building and formatting excel sheets or try to use legacy software like Orca.

Our mission is to give architects an easy-to-use solution so they can spend time building homes instead of excel sheets.

</aside>

About Compa

Compa was founded in 2020 and for now we are a team of 13 people. All our effort goes into becoming the German (for now) market leader for architect backoffice software. To get there we focus on building a self-serve cloud product that makes architects lives 10x better.

On our way to our first 1.000 customers, we will stay a small team. As such, we can fully focus on shipping customer value as quickly as possible.

We are backed by the best and most knowledgeable B2B SaaS investors in Europe.

We are remote-first but have an office in Berlin.

What you will do

You will discover and implement new features alongside our team of 7 engineers, our designer and the founder. We donโ€™t have any product managers, so all engineers take responsibility of solving customer problems from beginning to end (discovery, design, delivery).

You will be working on both BE and FE of your epics. Because of our current team constellation, we look for someone with a spike in BE (DevOps experience is a plus!). But you should be happy to jump on FE tasks when needed (we can help you learn it).

You have to be excited about creating customer value as quickly as possible in our stage. Technology is a tool to get us there, not the solution.

<aside> โ—

We value fast impactful architect solutions and promptness to react (incl. Identifying and fixing critical problems) over being bug-free and scalable. We bring modern solutions to the old industry. We value high ownership and detailed understanding of user problems over high ownership of specific technical parts.

</aside>

We take the hard long-term decisions over short-term success