Junior Business Analyst

We need analysts who can support our product owners and development teams in understanding user and business requirements and shaping the resulting product. Our analysts are part of the process of building our products and teams from the ground up.

Who we are and our culture

We’re a new organization, a spin-off arm of an insurance company called ERGO. ERGO is a reputable and solid institution, but its digital presence is just at the beginning. Our new organization exists to completely rebuild all of ERGO’s digital products from scratch, and to do it in a modern, agile way, without the organisational cruft. We want to do it right! We’re setting up self-contained product teams (in Berlin and Warsaw) who will work on a range of projects together, building new apps and websites for end users as well as business users. We want to be the best in the business. Insurance was not a sexy topic in the past, but we want to make a splash, we want to go big, and we’re willing to invest in the right people to help us get there.

We’re serious about building a diverse and tolerant team. Creating the right culture in our new organization is important. We want to grow, but grow well and not indiscriminately, and we won’t put up with so-called “brilliant jerks”.

What you’ll do every day

As Junior Business Analyst, you will support the Product Owner in understanding the users' requirements towards a product and translate it into user stories for the development team. You’ll be part of projects from the kick-off to the finished product during various iterations. In the day-to-day you will:

• Prepare and conduct user workshops and product demos
• Create user journeys to understand the users' perspective
• Analyze user requirements towards the product (incl. process flow, functions and data)
• Work with the development team to explain the requirements and validate the implementation
• Occasionally act as second level support for issues validation
• Some travel to our offices in Düsseldorf and Berlin is required

Why this is a good opportunity

Your voice will be heard. Your voice will be important. You will have the opportunity to create something from the ground up, not stepping into an already-established organization. You will get to build up our digital product portfolio and team processes. You will be working at a company willing to invest in agile methods. We are working in a start-up environment, but backed up by an established market leader. You can expect a very competitive salary and the ability to grow. Last but not least, we offer a cool office space with perks and the newest IT equipment to choose from.

Application requirements

• You should have initial experience in requirements management and/or software implementation
• You need to have worked with teams to deliver results
• You should have great analytical skills
• You can communicate with biz and tech people and are an outgoing person
• Ideally, you have experience working with agile methods
• A valid working visa for Poland - your application cannot be considered otherwise
• FLUENT Polish and English are a MUST for this position - please do not apply if you are not proficient in Polish AND English

Folio requirements

We want to know the details of your work – we’d like to see more than just descriptive bullet points. We’d rather have a few detailed case studies rather than a bunch of success stories with no context. Tell us about the goals, the context, constraints, the team, your role and your thought process.

Make sure to include the following information (where applicable) for each relevant previous project:

Project background: Set the context for the project. What was the goal of the project? What were your constraints? What was the timeline?

Team and your role: What was your exact role? What did you uniquely contribute, and who did you work with?

The work: Show us the range of what you produced.

Success metrics: Why are you showing us this project? Do you have any results that show this project achieved its intended goal?

Your learnings: With hindsight, and based on the process and outcome, was there anything you would have done differently?