This website uses cookies to ensure you get the best experience.

Visma e-conomic A/S and our selected partners use cookies and similar technologies (together “cookies”) that are necessary to present this website, and to ensure you get the best experience of it. If you consent to it, we will also use cookies for analytics purposes.

See our Cookie Policy to read more about the cookies we set.

You can withdraw and manage your consent at any time, by clicking “Manage cookies” at the bottom of each website page.

Select which cookies you accept

On this site, we always set cookies that are strictly necessary, meaning they are necessary for the site to function properly.

If you consent to it, we will also set other types of cookies. You can provide or withdraw your consent to the different types of cookies using the toggles below. You can change or withdraw your consent at any time, by clicking the link “Manage Cookies”, that is always available at the bottom of the site.

To learn more about what the different types of cookies do, how your data is used when they are set etc, see our Cookie Policy.

These cookies are necessary to make the site work properly, and are always set when you visit the site.

Vendors Teamtailor

These cookies collect information to help us understand how the site is being used.

Vendors Teamtailor
Skip to main content
Visma e-conomic A/S career site
Software Development · Copenhagen - Gærtorvet 1-5

Senior Frontend Engineer

You’ve come to the right place if you enjoy designing component APIs, standards and tooling that make other engineers faster – without sacrificing accessibility or quality.

Let’s get to know you in areas relevant to the role. Ready?Required

Skip the traditional motivational letter. Instead, share concrete examples and real experiences that showcase your skills. AI is a great tool, but use it wisely - we’d love to learn the real you.

Do you have a work permit allowing you to work in Denmark?Required

What aspects of building component APIs, tooling, or frontend architecture are you most curious to work on in a design system team?

What do you consider the biggest difference between working in a Design System team compared to working in a Product Team?

Tell us about a design system or shared frontend decision you made that didn’t age well. What broke, and what did you learn?

What’s a frontend or design system opinion you hold strongly, but know reasonable engineers might disagree with? Why do you still hold it?

Describe a time where you knowingly shipped a ‘less-than-ideal’ frontend solution in a shared system. What constraint forced that decision and what actions did you take afterwards?

Is there anything else you’d like to share about yourself? This is your space to add any additional information you feel is important. It’s optional, so write as much or as little as you prefer.

Personal information

When submitting your application to us, your information is processed in accordance with our Privacy Policy.