Senior Frontend Developer

A bit about TulaCo
At TulaCo we build, launch, and scale successful tech companies. Since 2010 we've been enabling USA-based startups, entrepreneurs, and mid-sized companies to innovate and make impactful applications. Our team unites over 150+ engineers in our HQ in Santa Monica, USA, and across Eastern Europe. We have a startup-like environment that values proactiveness, creative problem solving, and a flat hierarchy, where changes are driven by the team.
If you want to be one of us and work with like-minded people to create really cool apps, learn more about our open position and let us know about you!
What skills will you need? 
Core languages and frameworks

• 5+ years of commercial experience with React and function components with hooks. Knowledge of React 19 and the React Compiler.
• Good knowledge of TypeScript in strict mode, with no untyped code.
• Production experience with the Next.js App Router: layouts, dynamic routes, parallel routes, intercepted modal routes, and route handlers. Next.js 16 knowledge is a plus.
• Knowledge of Vite and React Router for single-page apps.

UI and styling

• Tailwind CSS v4, with CSS-first configuration and design tokens.
• shadcn/ui and Radix UI primitives, and composition patterns such as slots and ref forwarding.
• Class Variance Authority (CVA) and class-merge utilities for component variants.
• Experience with data-heavy UIs: AG Grid, Chart.js, drag and drop, date pickers, and file uploads.

State, data, and forms

• TanStack Query v5 for server state: query keys, cache invalidation, and mutations.
• Zustand for global state, and URL-based state for filters and pagination.
• React Hook Form with Zod schemas for complex forms that have many sections.
• Axios, and REST APIs that are described by OpenAPI

Architecture and engineering practices

• Monorepo experience with pnpm workspaces and Turborepo: task pipelines, remote caching, and filtered builds. The project has more than 60 packages and several apps.
• Feature-package architecture. Each business domain is a separate package. The apps only compose these packages. The candidate must respect package boundaries and use workspace imports.
• Layered data access. The API client is generated from OpenAPI with Orval. Feature packages wrap the client in React Query hooks. UI components do not call the API directly.
• Design system work. The candidate builds and extends shared components and documents them in Storybook.
• Feature flags for gradual releases, with a plan to remove each flag after the release.
• Permissions and multi-tenancy: organizations, accounts, user roles, and authentication flows.
• Observability: Sentry, Datadog RUM, and product analytics tools such as GA4, Google Tag Manager, and Pendo.
• Third-party integrations: Stripe payments, customer support widgets, and video players.
• Deployment basics: Docker and AWS ECS. The candidate does not own the infrastructure, but must be able to read a Dockerfile and debug a build.

AI-assisted development
AI tools are a normal part of the daily workflow on this project.

• Daily, practical use of AI coding agents, such as Claude Code and Cursor, on a large codebase.
• Ability to maintain agent context files (for example, AGENTS.md) at the repository level and the package level.
• Ability to write and use agent skills and plans for repeated tasks and large refactors.
• Experience with MCP integrations, for example Jira, Confluence, and Figma.
• Critical review of AI output. The candidate must check generated code against project conventions, type checks, and tests. The candidate must know that agents can be wrong about new framework versions.
• Ability to write clear task descriptions, acceptance criteria, and PR descriptions that both humans and agents can use.

Quality and testing

• Storybook 10 stories as tests that run in a real browser with Playwright. Chromatic for visual review.
• MSW for API mocks, and generated test data.
• Oxlint and Oxfmt for linting and formatting. Pre-commit hooks for format and type checks.
• Commitment to a clear Definition of Done: type check, lint, tests, format, and build pass before each PR.

Process

• Work with Jira tickets, Conventional Commits, and PR templates.
• Implement UI from Figma designs.

Communication and English

• Excellent written and spoken English. The candidate works directly with English-speaking product owners, designers, and engineers.
• Independent work in a distributed team across time zones.

Bonus Skills:

• Experience in ad tech: campaigns, ad sets, creatives, audiences, tracking pixels, A/B experiments, and CTV/video ads.
• Experience with OpenAPI code generation and API contract changes.
• Performance work: the React Compiler, bundle size, and the rendering of large tables.
• Experience with compliance features, such as rules for political ads.

Interested? We are looking forward to hearing from you!