• You have at least 5 years of professional experience in JavaScript / TypeScript
• You have substantial experience using JavaScript framework(s), understand the value of them, but also know when plain JavaScript is enough
• You are proficient with the component based architecture paradigm
• You’re up for mentoring coworkers and can give in-depth, productive feedback during code reviews. While you appreciate the small stuff, you recognize bikeshedding and can avoid its pitfalls
• You code with reason and can justify the important decisions you made during development
• You can communicate clearly in English, both written and verbally
• You can take the lead on deciding JavaScript best practices. That means the usual like testing, and refactoring; but also higher level concepts such as separation of concerns
• You're aware of the trade-offs involved in engineering, product design, as well as the bigger “business” picture
• You’ve got opinions on code design and you can discuss them, but you’re professional enough to not let those opinions get in the way of a consensus if necessary
• Your work hours have some overlap with EU business hours (we require your local timezone to be within CET +/- 3h)

Desirable

• What would a day in the life of a Front-End team member look like?
• 9AM:
• You start your day by checking the focus column on the Front-End team kanban board
• You pick the next prioritized item, which was ordered during this week's grooming session with the Product Manager
• This week’s focus is bringing the updated website navigation live, so you ensure the side panel matches the Figma design provided by the design team
• You've already reviewed the design and addressed any inconsistencies in the animation with the design team
• Looking ahead, next week’s task involves maintaining and upgrading Webpack to fix an issue with asset building in our CI pipeline
• 1PM:
• As an expert in our Front-End ecosystem, you join a grooming session with a product team needing help with a new Vue modal for attaching multiple documents in a form
• As part of Team Front-End you are expected to offer your consulting services as well to other teams that might be lacking in Front-End expertise
• You suggest extending an existing modal component to support multiple document uploads, simplifying the task
• Thanks to your input, the team can now better estimate their work
• 3PM:
• After lunch, you notice a question in the dedicated front-end channel on Slack from an engineer asking how to center a div
• You take some time to provide a solution using Tailwind CSS
• 5PM:
• The navigation changes are progressing well; your Jest unit tests are green, and the end-to-end specs show no failures
• You request a review from Product and your fellow engineers
• The side panel addition will contribute significantly to the overall redesign of the Silverfin app navigation
• Finally, you unwind by completing some pending merge request reviews you received notifications about on GitLab
• What does working at Silverfin look like?
• We work in nimble teams around 5 people in size, with each team taking ownership of a specific set of features of the application
• Teams are responsible for a full slice across the stack, so both the backend as well as the frontend of each part is maintained by the same people
• As a Senior JavaScript Developer, you will set the JavaScript best practices as well as assist and train the engineers when they are building front-end heavy features
• You’ll also work together with the Product team, which includes building Proof of Concepts for usability tests when we’re designing complex features
• This allows us to validate the assumptions we make during product design
• You will also maintain and extend the front-end tooling that we have in place to enhance the developer experience for everyone that works on front-end code
• We use Vue.js and TypeScript for the interactive parts of our application, and an up-to-date Rails monolith for the backend
• We favor Tailwind CSS for styling
• Rails renders the html for the less interactive parts of the application
• We use PostgreSQL and Redis for persistence and caching, and everything is running on a Kubernetes cluster in Google Cloud
• Our daily tools include GitLab, Quip and Slack, with Google Meet as our remote conferencing tool of choice
• No code gets deployed without a code-review by a peer and testing is a must
• Our pipeline automates deployment when the suite is green, and deploys happen dozens of times a day
• Each team is currently doing Kanban, but they’re free to follow whatever process suits them best
• We regularly hold retrospectives to work towards continuous improvement
• Software for accountants is not considered to be very exciting, but we have our fair share of interesting challenges
• To give you a sense of scale: our database exceeds 10TB, and our largest table crossed the 10 billion row mark
• We interface with more than 30 different external APIs, and provide third parties an API of our own