Clera
Growth/Product Engineer
About this role
A Y Combinator-backed developer infrastructure startup seeks a Growth/Product Engineer to enhance platform usability and design at their Series A stage. You'll own UX/visual polish across the product, establish a design system, and collaborate with backend teams while working primarily with React, TypeScript, and AWS/GCP infrastructure.
What you'll do
- Elevate platform usability and visual polish across the entire product interface
- Design and implement a consistent design system and visual language for the platform
- Improve the core dashboard UX and organization
- Build and maintain frontend features using React, styled-components, and TypeScript
- Participate in product strategy discussions and shape feature direction
- Collaborate with backend and infrastructure teams on full-stack integrations
What they're looking for
- React and TypeScript
- CSS and styled-components
- Design systems and component libraries
- UX/UI design sensibility
- End-to-end feature delivery
- Go and Kubernetes/Helm (nice-to-have)
- AWS or GCP cloud platforms
- Postgres and Redis
Benefits
- Visa sponsorship available
- High product ownership and influence on direction
- Collaborative, product-focused engineering culture
- Open to all experience levels including new graduates
- Fast-paced startup environment with rapid learning opportunities
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Clera
Clera builds an agentic operating system that automates complex workflows and processes through AI agents, with a platform designed to simplify distributed infrastructure management for developers. The company is hiring Founding Engineers, Customer Engineers, and Product Engineers to develop both backend systems and user-facing interfaces across their AI automation products.
View all jobs at CleraLikely interview questions
- Walk us through a design system you've built or contributed to—what were the key decisions and how did it impact the team's velocity?
- Describe a feature you shipped end-to-end in production. What were the challenges and how did you handle the frontend-backend collaboration?