Web APIs (advanced)
Web APIs (advanced)
See you @Frontend Team
Become a senior frontend engineer contributing to one of the projects in AppUnite. Whether it’s a new single page application, or an existing system with several millions of active users, we’ll find a good fit for you.
Writing new code, reviewing pull requests, designing components and application architecture, consulting and estimating new features, establishing code standards, setting up repositories, tweaking CI/CD, writing unit and automated tests, researching “the next tech stack” – those are just one of many tasks that will make up for your new job.
Working at AppUnite doesn’t mean being closed at one project. We have a lot of inner initiatives connecting all the frontend engineers. Consulting other teams, organising meetups, sharing knowledge is also what we do frequently.
Feeling adventurous? As a senior engineer, we’ll be glad to have you doing more than just writing code. Help us with recruitment. Mentor new engineers.
Fancy becoming a Team Leader? That’s an option too. Cooperate closely with project manager and business owners, so that each of your team members stays satisfied, motivated and does their best. Evaluate their progress, consult it with other leaders, and proactively find solutions to any issues that may come up in your team, project and AppUnite.
You will be responsible for:
- Cooperating with UI/UX designers, project manager and business owner in finding the nicest user interface you can implement,
- Choosing the best technology based on technical/non-technical requirements and constraints,
- Maintaining the quality and security of the product,
- Pairing with other developers, reviewing each others’ code, maintaining and establishing new code standards,
- Making architectural decisions that support the business and are well-suited to its problems (and educating other team members on how to make these decisions),
- Ensuring that you and your team understand the problem domain and are focused on solving the right problems,
- (optionally if willing to lead in the future) Building and leading a team.
We’ll be more than happy if you:
- Have solid knowledge of HTML, DOM and Web APIs,
- Have experience in styling complex apps using tools or methodologies like PostCSS, SASS, CSS modules, styled-components, BEM,
- Create good and maintainable frontend code by applying best practices, design patterns, and principles like SOLID,
- Have experience with responsive web design, mobile web development, server-side rendering, SEO, web performance optimization,
- Have good knowledge of frontend testing practices (unit/integration/e2e testing, component-based testing, visual regression testing) and tools (Jest, Cypress, Storybook),
- Had used REST APIs and developed GraphQL clients/servers,
- Know how to develop isomorphic applications (using Next.js or Nuxt),
- Have a good sense of UI/UX,
- Are open to proposing architectural and structural changes,
- Have strong communication skills,
- Have a growth mindset,
- Are communicative in written and spoken Polish and English.
Our workflow and toolset (which varies depending on the project):
- In the frontend: TypeScript, React (Functional Components, Hooks, Context API), Next.js, Vue.js, Nuxt, Redux, SASS, PostCSS, CSS modules, Jest, Cypress, Storybook, Webpack, Babel, Prettier, Eslint, GitHub Actions, GitLab.
- In the back-end: Elixir, Kubernetes, Google Cloud, Kafka, Kibana, Datadog.
- In general: Slack, Github/Gitlab, Asana/Clickup/Jira, Figma, Notion/Confluence, Sentry, Miro/Mural.
- Most projects operate in ~6 person cross-platform teams, consisting of a project manager, a technical leader, a QA and a few engineers. Such a team is usually focused on a specific part of the product, responsible for all phases of a feature rollout: design, development, release and monitoring.
- Work is usually done in one or two week sprints in an agile manner (with short daily stand-ups, and a retro/planning session once in a while).
- Each code change goes through a full PR-based code review and a QA review.
- Automated CI/CD process with deployment is set up for staging and production environments.
- Frontend apps may include a component library (Storybook-based) that’s based on a design library (Figma-based).
- Automatic browser end-to-end and/or integration component tests may be a part of a feature rollout and an incorporated part of the CI/CD process.
What does the recruitment process look like?
- Video interview with People Team.
- If everything goes smoothly – you’ll be invited to a technical challenge.
- If any other step of the recruitment process is necessary, we will inform you.
- And finally, the decision, after which we can say “welcome on board.”