Frontend Engineer - Agentic AI
Free to start · No card · 5 credits the moment you sign up
Job description
About Us
Hawk is the leading provider of AI-supported anti-money laundering and fraud detection technology. Banks and payment providers globally are using Hawk’s powerful combination of traditional rules and explainable AI to improve the effectiveness of their AML compliance and fraud prevention by identifying more crime while maximizing efficiency by reducing false positives. With our solution, we are playing a vital role in the global fight against Money Laundering, Fraud, or the financing of terrorism. We offer a culture of mutual trust, support and passion – while providing individuals with opportunities to grow professionally and make a difference in the world.
Your Mission
As a Frontend Engineer at Hawk, you will build and maintain the user interface of our agentic AI Investigation Agent. This is the product where compliance analysts configure AI workflows, watch autonomous investigations run, and review, question and act on what the agent concludes.
The frontend is a modern TypeScript monorepo made of a host application and a growing set of independently deployable microfrontends. These remotes are designed to be built once and used in two places: our new shadcn/ui-based Investigation Agent and our existing Material UI-based Case Manager. Your job is to understand this codebase deeply, keep it healthy, and ship new features with care, from the component level all the way to how it is built and deployed.
What You'll Work On:
Features: Build product features end to end in React and TypeScript, such as workflow graph editors, investigation timelines, data-heavy tables and dashboards that make agentic AI output understandable for analysts.
Microfrontends: Develop and maintain Module Federation remotes, keep remote/host contracts stable, and make sure features fit into both the Investigation Agent and the MUI-based Case Manager.
Design system and data layer: Contribute to our shared shadcn/ui + Tailwind component library (documented in Storybook), and consume our Python/FastAPI backends through OpenAPI-generated clients with TanStack Query and Router.
Build, test and deploy: Work in a pnpm + Turborepo monorepo with GitHub Actions CI, Vitest and Playwright tests, and deployments to AWS including per-PR preview environments.
Collaboration: Work closely with Product, UX, backend engineers and Data Science, and use AI coding tools such as Claude Code or Cursor as part of your everyday workflow.
Your Profile:
3–5 years building and maintaining production React applications, with strong TypeScript and modern React skills (hooks, composition, performance, complex state and forms).
Clean frontend architecture: you structure code around features and clear boundaries. You keep UI components presentational and reusable, put data fetching and business logic in hooks and typed API layers, and keep server state separate from local UI state. You prefer composition, small focused components and strict typing, and you treat cross-module contracts as an API.
Design-system experience: hands-on work with a component-library approach, ideally shadcn/ui, Radix and Tailwind. Familiarity with Material UI is a strong plus.
Microfrontends and delivery: Module Federation or similar runtime composition, shared dependencies and host/remote contracts, plus the build and deployment basics behind them: Vite, monorepos (pnpm workspaces, Turborepo or Nx), CI pipelines (GitHub Actions)
Comfort with ambiguity: you're happy working on problems that aren't fully defined yet. You ask the right questions, make sensible assumptions, build a first version and refine it with Product and UX, without waiting for a perfect spec.
AI tooling: daily, practical use of AI coding assistants (Claude Code, Cursor, Copilot, etc.).
Communication: clear communication in English, and the ability to explain technical decisions to both technical and non-technical colleagues.
Bonus:
Some Python: enough to read a FastAPI endpoint or Pydantic model, run the backend locally, trace a bug across the API boundary, or open a small backend PR. You don't need to be a backend engineer.
Infrastructure as code: exposure to Terraform or AWS CDK.
Quality tooling: Storybook-driven development, visual regression testing or accessibility testing.
Auth: Auth0/OIDC integration in single-page apps.
Domain interest: UX for AI products, or previous work in fintech, RegTech or compliance.
Prepare your application
Use the description above to assess your fit for Hawk. This checklist is guidance from Resumize, rather than additional requirements from the employer. Imported listings can be shortened or change after collection, so confirm the complete description and current availability before sending an application.
Match requirements to evidence
Identify the responsibilities and skills the employer explicitly names. For each important requirement, choose one example from your work, education, training, or projects. Explain what you did, how you did it, and what changed as a result. Include a measurable outcome when you can support it. If you lack a requirement, describe related experience accurately instead of adding an unfamiliar skill to your resume.
Put the most relevant examples near the top of your resume. Keep job titles, dates, qualifications, and contact details consistent across your application materials. Use the employer’s terminology when it describes your experience accurately; a copied list of keywords does not explain your contribution. A short, specific bullet is easier to review than a paragraph that mixes several unrelated duties.
Check the working arrangement
Confirm the location, schedule, employment type, and any eligibility requirements on the employer’s site. A remote label does not establish worldwide eligibility or flexible hours. If compensation, benefits, equipment, travel, or contract duration are missing from this listing, write down your questions for the recruiter. Do not assume details from another opening at the same company apply to this role.
Review before submitting
Follow the employer’s requested file format and application instructions. Open your exported resume and check that its text is selectable, its sections read in order, and its links work. Proofread names, dates, and contact information. Share confidential work samples only when you have permission, and use an anonymized example when necessary.
Submit through a trusted employer or recruiting destination. If the original listing has disappeared, search the employer’s careers page for the title rather than assuming the vacancy remains open. Save the application date, job reference, and the version of your resume you sent. Those details help you prepare for a later conversation and avoid submitting conflicting information through several job boards.
Review your resume for writing and readability feedback, or browse other openings if this opportunity is unavailable.