Job Opportunities API

Element451 is building the AI-powered platform reshaping how colleges and universities recruit, enroll, and support their students — and the frontend is where that experience comes to life. You’ll build the product surfaces that staff and students touch every day, on a modern Angular stack with AI woven directly into the interface. It’s a rare chance to own meaningful features end to end, treat AI as a real craft rather than a buzzword, and help shape how a high-performing team builds software in the AI era. If you want your work to matter, your judgment to carry real weight, and your skills to keep growing alongside people who care deeply about the craft, you’ll feel at home here. The Role You’ll build high-quality software with full end-to-end ownership — from shaping a feature in planning through keeping it stable in production. This is an explicitly AI-forward role: AI tooling is a professional discipline here, applied thoughtfully across every phase of the work, not a shortcut for generating code. Senior Engineers operate with a lot of autonomy, hold their work to a high standard, and lift the quality of the work happening around them. We hold a high bar — and we give you the ownership, context, and support to meet it. We’re upfront about expectations because the engineers who thrive here tend to want exactly that kind of environment. What You’ll Own You own the frontend features you ship — from the first design conversation until they’re live and working well for real users. We see “done” as a feature that’s validated, accessible, and performant in production, not just merged or handed to QA. Day to day, that looks like: - Building features on our existing component library — composing from shared components, keeping code well-structured and maintainable, and managing reactive state (NgRx / RxJS / signals) that stays predictable as the app grows. - Owning the data layer of your features: modeling GraphQL queries for reads and REST calls for writes, handling loading, error, and empty states deliberately, and keeping client state reliably in sync without race conditions or memory leaks. - Holding the line on performance — bundle size, lazy loading, change-detection cost, and render performance — so screens stay fast on real devices and connections, not just on your machine. - Treating accessibility and cross-browser/responsive behavior as part of the definition of done, not a follow-up ticket: semantic markup, keyboard and screen-reader support, and correct behavior across breakpoints. - Building to the design system and pushing it forward — matching design intent closely, and improving shared components rather than forking one-off variants. - Backing your work with tests: unit tests for component and service logic, and Playwright E2E coverage for the paths that matter. - Shipping safely behind feature flags, watching your features in production (Sentry, real usage), and owning issues from the shared triage queue when they land in your area. On AI: you treat code assistants, test generation, debugging, and design exploration as core craft — and you hold AI-assisted work to exactly the same bar as anything you write by hand. Every AI-generated output is reviewed, tested, and fully owned before it merges. Speed never substitutes for judgment. You also share what works, helping encode effective patterns into how the whole team operates. How You’ll Show Up - We hire for behavior as much as for experience. Technical skill gets you considered; how you operate determines whether you’ll thrive here. These are the values we live by, and the ones we hire for: - Understand the “why” before the “what.” You seek the reasoning and context behind the work before diving in, so what you build actually solves the problem. - Own the outcome. You take responsibility for the result, not just your slice of the work — from first design conversation to stable in produ