Product & Engineering

Behind the purple curtain of Forecast is a phenomenal team of talented Engineers, Product Managers and Product Designers who all come together to make magic happen.

See all open positions
Artboard Layer 1

We value team autonomy. We hire smart people and we want to know what you think! Driven by our core value of Direct & Honest, your opinion on the how and the why matters. Have an interesting product idea or tech suggestion? Your voice will be heard.

What Product & Engineering looks like at Forecast:

To drive synergy and collaboration, we work in product teams. Each team typically comprises of:

Engineers,  Product Manager,  Product Designer,  QA

Each team is responsible for a specific product domain of Forecast. They plan and execute development of the platform in two week sprints.

Our teams:

Resource Management

In our resource management team, we work on creating a real-time and interactive overview for our customers of the workload and capacity of all their employees. This area is one of the key value propositions of our product and an area where we truly differentiate ourselves from the competition.

We work with big amounts of data and creating an amazing user experience in general this team has a lot of focus on how we can optimize our computations and work with this data as efficiently as possible.

We work with technologies as TypeScript, JavaScript, Java, Serverless, HTML Canvas, React JS, RDBMS, DynamoDB

Financials

In our financial team, we work on financial features as project budgeting and invoice basis. We don’t operate in actual accounting, but instead, we can integrate relevant data to accounting, ERP, and CRM systems. Our financial team naturally has an extremely high focus on quality. Financial numbers have to be trustworthy! 

We work with technologies as TypeScript, JavaScript, React JS, Java, Serverless, RDBMS, DynamoDB

Task & Time Management

The domain of task and time management is a crowded space with a lot of competitors. Here in this team, we fight to trump the best in this space. We love to make features that our users enjoy using and allow our self to spend extra time to make things extra nice.

On another technically complicated side, we also build and support some very complicated integrations to 3rd party systems like Jira and Azure Dev Ops. Here we automatically and seamlessly link and synchronize large amounts of data between our platform and one of those connected systems. This requires a lot of complex data modeling/mapping and naturally a dedicated team with an interest in tackling these kinds of complex problems.

We work with technologies as TypeScript, JavaScript, Java, Serverless, RDBMS, DynamoDB, React JS, Virtualization/Visibility Sensor, Drag and drop

What’s behind our tech stack decisions

We’re a company founded by Computer Scientists so unsurprisingly excitement about technology is deep in our DNA.

Here’s topics that excites us and tell a bit about our tech values:

Serverless technologies:

We are pushing our platform in the direction of serverless technologies (written in TypeScript) which enables us to create an extremely robust system and utilize advanced caching solutions to make complex and data-heavy computations perform very nicely

GraphQL/Relay:

We are all in on this communication framework and always to be on the newest versions with the most advanced features. It gives us, as developers, a very powerful way of working with data and caching on our front-end. If you come from a traditional REST-style setup this is miles ahead.

Continuous Deployment:

Without any manual testing (or any other human interaction) new code is automatically tested and pushed to our production environment continuously throughout the day. We have a very fluid build pipeline that our developers love and embrace because code changes usually aren't more than 15-30 minutes away from being in the hands of our end-users.

Automation:

In general we have a very high focus on automation. No one wants to spend time on the boring and tedious tasks - those we always try to automate. That allows us to spend time on building software, designing architecture, and solving hard and interesting problems.

Componentization & Storybook:

Especially on our front-end we focus on strong components that are easily re-usable. Again this for our own sake as developers so we can focus our time on the interesting problems to solve.

HTML Canvas:

Some of the most data-heavy and visually complex areas of our front-end combine React and HTML Canvas, a part of the HTML5 standard that allows for low-level high-performance vector-based graphical rendering.

Stack:

Java, JavaScript, TypeScript, Python, RDBMS (AWS Aurora), DynnamoDB, Advanced AWS infrastructure.

A typical sprint cycle

No days are the same at Forecast and when working here and with an organization that grows as rapidly as we are, you have to be ready to tackle new and exciting challenges all the time. With new challenges continuously we do although try to create rhythm with our Sprint cycle. A structure that makes sure that we can maintain a focus on solving these interesting problems instead of unnecessary bureaucracy and meetings.

We run in two-week sprints with these continuous elements:

This is naturally a team effort where everyone participates and commits to the sprint plan. The team typically sets 2-4 overarching goals for the sprint. These goals are then used to plan and prioritize the work for the sprint.

The team meets every morning to coordinate team efforts and make sure no one is blocked by any impediments. If there are any problems that put the sprint goals at risk the needed team members swarm until those are fixed.

Our fruits of discovery is a weekly time slot where product managers/designers present their concepts for upcoming epics/initiatives. It is often cross-team and stakeholders also participate. This gives the team a forum where we can catch potential problems and everyone can pitch in on the things we are gonna build. It minimizes the risk of running into problems when we develop.

We have this community where all developers can present ideas and knowledge-share across teams. This is true developer time where where developers sets the scene and decides the agenda!

You have a weekly or bi-weekly 1:1 with your manager/tech lead. This is basically the team members time with her manager. Any topic you would like to discuss - this is the place. Common topics are goal setting, team dynamics, support on tackling the difficult things. This is not a status report, but rather a time to ask questions, being honest and sharing things thoughts of the things you are working on.

This is showing off time! Here we present the achieved sprint goals.

What can you expect from a recruitment process with us?

call

 

Initial phone chat

An initial call with a member of our People team to discuss the role and Forecast in more detail, talking you through the company, culture, the team and the process ahead. 

book a demo

Interview with your prospective manager

Next, you’ll speak directly with your prospective manager to go into more detail around your technical background and skill set, how we work in Engineering and get a feel for our company leadership. 

interview

 

Technical Interview

We’ll invite you into our offices to meet with your prospective manager and one of our Tech Leads for your Technical Interview. This portion of the process is a technical scenario style interview, where you’ll talk us through problems and your approach as a Developer. You’ll also have the chance to get a feel for the office environment and team, and meet prospective fellow Forecasters.

We know interviews are a two way process so we encourage you to come prepared with as many questions as you can! 👍