Software Engineer II - Front End

As a Software Engineer II - Front End at isaac, your main responsibilities will include designing and developing high-impact projects, translating functional and technical requirements into design, encouraging best practices among the team, engaging in code-reviews, and contributing to a collaborative work environment focused on innovation.

To qualify for the Software Engineer II - Front End role at isaac, candidates should have at least 3 years of experience in software development, solid knowledge of JavaScript, HTML, and CSS, and familiarity with a JS framework such as React or Vue. Experience with algorithms and data structures is also essential.

At isaac, you'll work with modern technologies including JavaScript, HTML, CSS, and potentially React or Vue.js. Familiarity with agile methodologies and working within a data-driven development environment will also be beneficial.

Isaac’s company culture encourages autonomy, a hands-on approach, teamwork, and data-informed solutions. We focus on nurturing a diverse and inclusive environment where everyone can contribute and grow. Your input as a Software Engineer II - Front End will truly be valued!

As a Software Engineer II - Front End at isaac, you can look forward to a variety of benefits including a flexible meal allowance, home office assistance, comprehensive health and dental plans, extended parental leaves, and opportunities for continued education and wellness, among others.

Be prepared to detail your hands-on experience with JavaScript, HTML, CSS, and the specific frameworks you have used. Discuss any projects where you utilized these technologies effectively and highlight your understanding of best practices in front-end development.

Explain your process for understanding functional requirements, outlining the steps you take to convert those into technical specs. Use examples from past work to illustrate your thought process and collaboration skills with team members.

Discuss your commitment to coding standards such as naming conventions, documentation practices, and the importance of code reviews. Highlight experiences where following these practices resulted in improved code quality or team efficiency.

Share a specific project where you encountered challenges, detailing the obstacles faced and how you overcame them. Emphasize your problem-solving skills and how your contributions impacted the project’s success.

Mention specific resources you use, such as online courses, seminars, and tech blogs, and how you apply new knowledge to your projects. Discuss your openness to learning and adapting.

Discuss tools you find helpful for collaboration (like GitHub, Zoom, etc.), techniques to ensure clear communication, and the importance of building relationships with teammates to maintain a supportive working environment.

Express your understanding of web accessibility standards (like WCAG) and mention specific practices you implement to make applications accessible to all users, including use of semantic HTML and ARIA attributes.

Outline your testing strategy, including unit testing and integration testing frameworks you’ve used. Provide examples of how testing has played a role in your development process to ensure quality.

Discuss the benefits of pair programming, such as improved code quality and collaborative learning, and share your personal experiences of working with another developer in this manner.

Emphasize the importance of open communication and collaboration. Share examples where you've engaged in conflict resolution by seeking constructive discussions to reach common ground.