Find your next opportunity
Browse fresh openings from leading companies and apply with a resume tailored to the role.
Browse expert rolesBrowse expert rolesBrowse fresh openings from leading companies and apply with a resume tailored to the role.
Browse expert roles14179 openings
4625-4632 of 14179
Hawk
Free to start · No card · 5 credits the moment you sign up
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.
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.
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.
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.
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.
Start with a role or skill you want to use in your next job. Use the location and role filters to narrow the results, then open a listing to review the description. A title alone rarely explains the level of responsibility, working arrangement, or experience a team needs. Compare those details before deciding which opportunities deserve a tailored application.
Employers use different titles for similar work. If an exact phrase produces no results, try a shorter title, a core skill, or an alternative name for the role. Remove one filter at a time to understand which requirement is narrowing your search. A broader search can reveal suitable work without asking you to change your actual qualifications.
For each promising listing, read the responsibilities and separate essential requirements from preferences. Note the location, schedule, employment type, and compensation when provided. Missing details are questions to confirm with the employer. A remote opening may still require a particular country, work authorization, or time-zone overlap, so check the full posting before treating it as a location-independent opportunity.
Choose a few examples that demonstrate the skills this employer names. Explain your contribution and its outcome, using accurate numbers where available. Put the most relevant experience first and keep your resume easy to scan. Avoid adding technologies, qualifications, or achievements simply because they appear in a description. Your application should make your existing strengths easier to understand.
Follow the employer’s instructions for resumes, cover letters, work samples, and screening questions. Review the exported file before submitting it: confirm that contact details are correct, text can be selected, and links reach the intended pages. A resume check can help you spot unclear writing before you apply. Its feedback is advisory and does not predict a hiring decision.
Listings are collected from external sources and may change after they appear here. The employer or recruiting destination controls whether applications are open. If an original link is unavailable, check the company’s careers page for the title or move to another opening. An employer website link is a place to check current vacancies, rather than confirmation that a particular job is still accepting applications.
Keep a simple record of the company, role, job reference, application date, and documents you sent. Record any follow-up instructions and the next action you plan to take. This makes it easier to prepare for interviews, compare opportunities, and avoid applying repeatedly to the same opening through different boards. Review your shortlist as employers update their listings and prioritize opportunities with clear requirements that match the work you want to do.