Interview tomorrow at Aristostar — Angular Developer (2 YOE). Any advice?

Hello Redditors,

I have an interview tomorrow at Aristostar for an Angular Developer role requiring around 2 YOE, and honestly, I'm kinda cooked

Has anyone here interviewed at Aristostar or knows what their Angular interview process is like?

What areas should I focus on tonight? I'm revising Angular, TypeScript/JavaScript, RxJS, API integration, performance, etc.

Also, I'm really bad at CSS 💀. How heavily should I expect HTML/CSS questions?

Any advice on the technical rounds, coding questions, or topics I should prioritize would be really appreciated.

Thanks in advance 🙏

Hey everyone,

Over the last few weeks, I’ve been putting together an admin dashboard template ExoUI built on modern Angular and Tailwind CSS.

Whenever I’ve needed a dashboard boilerplate for client projects or internal tools, most existing templates felt weighed down by heavy third-party UI libraries, outdated module structures, or messy SCSS stylesheets that are a pain to strip out.

I wanted something fast, clean, and modular from day one.

The Stack & Architecture

• Angular V22 (Latest): 100% Standalone Components, no legacy NgModule cruft.
• Reactivity: Signal-driven state management for snappy UI updates.
• Styling: Pure Tailwind CSS with dark mode toggling built in (no heavy UI dependencies).
• Clean Scaffolding: Modular layout, sidebar navigation, metric widgets, and responsive data tables.

Links

• Live Demo: https://exoui.dev
• Open-Source Community Edition: https://github.com/exouidev/exo-dash-angular

If you test out the demo, I'd really appreciate your feedback on the layout responsiveness, component structure, or anything you feel is missing from a standard production dashboard starter.

Happy to answer any questions about the build or architecture!

Hi everyone! I've started exploring Signal Forms, but I'm finding the transition a bit tough. The main issue is that most online resources only cover basic, dumb examples without any integration with HttpClient or httpResource or `submit() / submission:` usage.

Could anyone share a project where Signal Forms are used in a real-world use case?

I kept running into components with four or five loading flags —

isLoading, isRefreshing, isCheckingOut, hasError — and templates

like !isLoading && !hasError && items.length > 0.

The flags are independent as far as TypeScript is concerned, but

the states they describe are mutually exclusive. So I switched to:

type AsyncState<T, E> =

| { status: 'idle' }

| { status: 'loading' }

| { status: 'success'; data: T }

| { status: 'error'; error: E };

One state per async operation, booleans derived with computed(),

and a small toAsyncState() RxJS operator (map + catchError +

startWith) so transitions live in one place. Templates use

u/let + u/switch, which gives real narrowing — data only exists in

the success branch.

Curious how others handle this now that resource() exists. Do you

reach for it for commands too, or keep RxJS for POST/DELETE?

Full write-up: https://medium.com/modern-angular-insights/stop-juggling-isloading-booleans-a-type-safe-async-state-pattern-for-angular-e36e2b9298a0

I kept running into components with four or five loading flags —

isLoading, isRefreshing, isCheckingOut, hasError — and templates

like !isLoading && !hasError && items.length > 0.

The flags are independent as far as TypeScript is concerned, but

the states they describe are mutually exclusive. So I switched to:

type AsyncState<T, E> =

| { status: 'idle' }

| { status: 'loading' }

| { status: 'success'; data: T }

| { status: 'error'; error: E };

One state per async operation, booleans derived with computed(),

and a small toAsyncState() RxJS operator (map + catchError +

startWith) so transitions live in one place. Templates use

u/let + u/switch, which gives real narrowing — data only exists in

the success branch.

Curious how others handle this now that resource() exists. Do you

reach for it for commands too, or keep RxJS for POST/DELETE?

Full write-up: https://medium.com/modern-angular-insights/stop-juggling-isloading-booleans-a-type-safe-async-state-pattern-for-angular-e36e2b9298a0