About the role
You’ll lead the frontend on one or two delivery engagements at a time — typically Angular SPAs talking to .NET or Node backends. We expect senior engineers to set technical direction, not just execute against tickets.
You’ll work with product owners on our client side, and with backend / DevOps engineers on our side. Code review and architecture decisions are public — we write them down so the next person inheriting the codebase has a fighting chance.
How we hire
One intro call → a paid take-home or a deep-dive on something you’ve built (your choice) → a 90-minute architecture conversation → an offer. About two weeks end to end.
What you'll do
- Lead the frontend architecture on Angular projects — module boundaries, state strategy, data flow, performance budgets.
- Build and maintain reusable component libraries that the rest of the team plugs into.
- Mentor mid-level engineers through code review, pairing, and design discussions.
- Drive accessibility, internationalization (incl. RTL), and performance as first-class concerns, not afterthoughts.
- Own the build pipeline for the frontend — bundling, CI, type safety, lint, test coverage.
What we're looking for
- 5+ years of professional frontend experience, with at least 3 years on Angular (2+ / latest LTS).
- Deep TypeScript fluency. You can read and reason about generics and conditional types without thinking.
- Strong grasp of RxJS — operators, marbles, the actual back-pressure model.
- Experience with at least one state-management approach (NgRx, Akita, Signals, or service-with-subject patterns) and the trade-offs of each.
- Frontend testing fluency (Jasmine/Jest + Cypress or Playwright).
Nice to have
- Angular Universal (SSR) experience.
- Micro-frontend or module-federation work.
- Design-system contribution (Storybook, Figma-to-code workflows).
- Bilingual (English + Arabic) — useful for RTL/i18n work on our regional clients.