01The challenge
An agency's roles change constantly. On a static site every new role is a developer task, so listings go stale and the site stops being the place candidates look.
Applications are handled in an external recruitment system, and the links into it should not be sitting in the public page source. The whole site is Hebrew and right to left, and it has to be findable by people searching for jobs, which means the pages have to be rendered on the server rather than assembled in the browser.
02The solution
A modular monolith on .NET with separate Jobs, Content and Identity modules, and an Angular site rendered on the server for every public request.
A role only goes live once it passes a publication check: title, summary, description, category, a location or an explicit remote flag, a valid https application link and a closing date in the future. When something is missing the admin gets the full list back in Hebrew rather than one error at a time.
The apply button does not carry the external link. It points at the site's own endpoint, which records the click and redirects, so the recruitment system's address never appears in any public payload or page source, and a role that has closed answers that it is gone instead of forwarding anyone. Which domains an application link may point at is itself an admin setting.
The marketing pages are structured records rather than a page builder: hero, areas of expertise, why us, process, statistics, testimonials, client logos, calls to action, navigation, SEO entries and legal pages, each with its own fields and its own place in the order. Section visibility and ordering are editable, and the only rich text, the legal pages, is sanitized on the server.
