Senior Frontend Engineer

Real-world data is the competitive edge in AI.

HumanSignal is a human data partner for companies building AI models and products. Our customers ship better AI, faster, because we partner with their researchers from real-world data creation to annotation to delivery.

We design and create datasets from scratch, recruit and manage the domain experts who evaluate model output, and run everything through our own platform, Label Studio, the open-source standard for data labeling and evaluation, used by over 1 million practitioners worldwide.

We specialize in the operationally complex: real-world data collection, multimodal pipelines, and multi-step workflows. Advanced ML and AI teams use our enterprise platform to run their own data factories, and our services team to extend their reach where in-house capacity runs out.

If you want to do work that materially shapes how the next generation of AI products gets built, we'd love to talk.

This is a product-engineering role: not “build what you’re told,” but shape what we build—own the problem, propose solutions, and ship outcomes that matter to users and the business.

We’re hiring a Senior Frontend Engineer with product vision. You’ll lead with craft—shipping fast, accessible UX in React/TypeScript—and partner early with PM/Design to frame problems, prototype to learn, and make pragmatic scope calls. You care about clarity, performance, and simplicity in complex, data-heavy workflows—so the result feels simple, performant, and trustworthy.

• →Build and maintain frontend components and views for labeling, review, and evaluation workflows with performance, accessibility, and scalability in mind.
• →Own outcomes, not tasks: refine scope, suggest trade-offs, propose simpler approaches, and land increments that deliver value fast.
• →Partner with Product & Design from discovery to delivery: clarify user jobs, write lightweight RFCs/PRDs, and shape scope and milestones.
• →Prototype to de-risk UX; use flags/gradual rollouts; gather feedback from users/support and iterate after releases.
• →Raise the bar on FE standards: state management, testing, error boundaries, a11y, i18n, and developer ergonomics.
• →Partner with Support to investigate production issues, reduce UX papercuts, and turn learnings into fixes.
• →Engage with our open-source community (issues, discussions) to understand real-world needs and improve developer experience.
• →Participate in architecture discussions and code reviews; mentor teammates and improve patterns across the codebase.
  
  

• Senior-level experience shipping production React/TypeScript apps (HTML/CSS mastery; ES6+; a11y).
• Strong product sense: you’ve made scope/trade-off decisions and iterated based on real-world usage and feedback.
• Fluency with modern FE tooling (e.g., Vite/Webpack, Jest/Cypress) and state-management patterns.
• Comfort collaborating with APIs and occasionally touching backend code (Django/REST familiarity is a plus).
• Excellent communication at a Senior IC level—you write clear RFCs/PRDs, give actionable reviews, and present trade-offs well.
  
  

• Experience with data/ML tools, OSS, design systems, or performance profiling.
• Familiarity with feature flags/gradual rollouts and qualitative feedback loops (support forums, user sessions).
• Prior work on complex, data-heavy UIs (review tools, multi-step workflows, or IDE-like apps).
  
  

Python/Django, JS/TS, React, OpenAI API, Spark, BigQuery, Kafka, Jest, Cypress, AWS, Kubernetes, Postgres, Redis.

Trunk-based development with small, reviewable PRs; feature flags for safe rollouts; strong code reviews; pragmatic testing; and close collaboration with Product/Design/Support.

At HumanSignal, we follow a six-week cycle known as "Build and Ship" followed by a "Cooldown." During the first four weeks, the team focuses on creating new features and shipping improvements. We also rotate a small group to handle customer support, ensuring everyone stays in touch with real user needs and we can respond quickly to issues.

After those four weeks, we have a two-week "Cooldown" period. This is when we tackle technical debt, refine our integration processes, and wrap up those lingering tasks that never quite fit into regular sprints but really help us feel good about our codebase and workflows.