Angular Developer – Enterprise SPA

Were hiring an Angular Developer to help build and maintain large-scale enterprise single-page applications. The work involves real technical depth performance maintainability accessibility and well-structured architecture. Youll be part of a cross-functional product team that cares about engineering quality and straightforward collaboration.

• Build and maintain Angular applications used daily by enterprise clients.

• Implement modern state management and reactive patterns with NgRx and RxJS (or Signals where relevant).

• Write clean testable TypeScript following strict type safety and code review standards.

• Work closely with design to translate UI/UX into accessible consistent components.

• Maintain a shared design system using Storybook and Angular Material (with optional theming).

• Optimize for performance from bundle sizes and lazy loading to runtime efficiency.

• Ensure conformance with WCAG 2.2 accessibility guidelines.

• Integrate APIs built with REST and GraphQL.

• Contribute to automated tests (Jest Cypress Playwright) and CI/CD pipelines.

• Angular 16 TypeScript RxJS / NgRx / Signals

• SCSS / Tailwind Angular Material Storybook

• Jest / Cypress / Playwright

• Vite / Webpack Docker GitHub Actions

• REST / GraphQL

• Accessibility audits via Lighthouse and axe-core

• 3 years of experience building production-grade SPAs in Angular.

• Good understanding of component-driven architecture and modular design.

• Confidence working with reactive state and TypeScript at scale.

• Familiarity with accessibility standards and practical implementation.

• Clear understanding of testing deployment and version control workflows.

• Ability to collaborate with both developers and designers effectively.

• Experience with monorepo setups (NX Turborepo).

• Familiarity with SSR or static rendering using Angular Universal or AnalogJS.

• Interest in frontend tooling design tokens or performance monitoring.

• Established engineering culture that values maintainable solutions over quick fixes.

• Up-to-date tech stack and clean CI/CD setup.

• Cooperative no-nonsense environment where good work is recognized.

• Time and space to do things properly from architecture to documentation.

My Transparency Disclaimer:

I use Teamtailor Co-pilot an AI-powered assistant built into my ATS to help me process applications faster. I want to be explicit about what it does and what I do myself because you deserve to know exactly how youre being evaluated.

What Co-pilot does:

• Reviews your CV and application answers against predefined criteria

• Generates a CV summary so I can orient quickly before reading in full

• Flags how your profile maps against must-have requirements

What I do:

• I personally read every single application. No one gets rejected by an algorithm alone.

• I make all decisions Co-pilot surfaces signals I draw conclusions.

• I reply to every candidate whether you progress or not.

Co-pilot screens every application against the following criteria automatically. These are not nice to haves or weighted preferences if your application doesnt demonstrate all 5 it will not progress to the reviewing stage.

Im being explicit about this so you can self-select honestly before applying. Thats better for both of us.

1. NgRx or RxJS experience
You must have hands-on production-level experience with reactive state management in Angular NgRx RxJS-based patterns or Signals. Reading about it doesnt count. Im looking for applied exposure in real projects.

2. Angular experience
You must have meaningful professional experience building and maintaining Angular applications. Framework familiarity is table stakes here; Im assessing depth not exposure.

3. TypeScript experience
You must actively write TypeScript not just tolerate it. This role involves a codebase where TypeScript discipline matters types interfaces generics in practice.

4. Storybook or Design System maintenance
You must have real experience with Storybook or have contributed to maintaining a component library or design system. UI documentation is treated as an engineering deliverable on this team not an afterthought.

5. Accessibility implementation
You must have implemented web accessibility in shipped work. This is a hard requirement. Projects where accessibility was theoretically considered but not practically applied dont satisfy this criterion.

If youre missing even one of these five please dont apply hoping it goes unnoticed. Ill see it and Ill tell you honestly why it didnt work but its a better use of your time to apply when you genuinely meet all five.

Your responses to the 10 mandatory questions are the main input at the screening -pilot reads them. I read them too. Theres no right answer to game Im looking for accuracy not optimisation.

Heres exactly what Im asking and why:

1. State management libraries used in production (NgRx RxJS Signals Akita None) to assess which reactive patterns youve actually shipped with

2. CI/CD pipeline confidence (scale 15) to understand how independently you can own pipelines not just use them

3. Frontend testing tools actively used (Jest Cypress Playwright Karma/Jasmine None) testing culture is part of this roles expectations

4. GraphQL integration in Angular a direct question; carries real weight in the assessment

5. Years of professional Angular experience context for everything else

6. Version control systems used baseline signal; Git experience is expected

7. Lazy loading familiarity (scale 15) angular architecture awareness at module and component level

8. Build tooling: Vite or Webpack in Angular projects distance from modern Angular workflows matters

9. Storybook experience (scale 15) because we treat component documentation as a deliverable

10. Angular Material components customised with SCSS/theming practical evidence of frontend styling depth

If your application progresses the interview goes deeper into areas that cant be evaluated from a form alone. Heres what Ill be looking at:

Technical depth real trade-offs not textbook answers
Ill ask about architecture decisions youve made why you made them and what youd do differently. Im not looking for perfect answers Im looking for how you think when things get complicated.

State management under pressure
How you reason about NgRx vs Signals vs RxJS in different contexts and where youve seen each approach break down.

Testing philosophy
Not just which tools youve used but how embedded testing is in your actual workflow. Do you write tests because youre told to or because youd feel unsafe without them

Build pipeline ownership
Whether youve configured and maintained CI/CD pipelines yourself or whether youve operated within what someone else built.

Component architecture and documentation
How you think about Storybook as a living contract not a documentation checkbox.

Accessibility approach in practice
How youve made accessibility decisions under real project constraints timelines legacy code team pushback.

Work artifacts
Ill ask to see real things: code samples a repository a Storybook instance anything that shows how you build. It doesnt need to be polished. It needs to be real.

Inbox Reviewing Interview Offer

Every stage has a human decision -pilot assists at the Inbox stage. I take over from there.

Transparency commitment: I reply to every applicant. If you dont progress Ill tell you why as specifically as I can not a template a real note. Youll also receive a short NPS survey after the process. I read every response and it directly shapes how I run this.

Hubert Tech Recruiter @ WhyHireWrong