Clera
Founding Engineer
About this role
Join an early-stage San Francisco startup as a Founding Engineer to build full-stack features from the ground up, shape technical architecture, and influence product roadmap decisions alongside the founders in a high-impact, high-trust environment.
What you'll do
- Build and ship full-stack features in a 0-to-1 product environment
- Own product decisions and contribute to roadmap prioritization with founders
- Establish engineering standards, architecture, and development practices
- Collaborate cross-functionally in a small, flat team structure
- Iterate rapidly based on user feedback and business requirements
What they're looking for
- Full-stack software development (3-7 years)
- Product sense and decision-making ownership
- Architecture and system design
- Ability to work in ambiguous, fast-paced environments
- Cross-functional collaboration
- Rapid iteration and shipping mindset
- FAANG or early-stage startup experience (nice to have)
- 0-to-1 product shipping experience (nice to have)
Benefits
- Salary: $200,000–$300,000 USD annually
- Equity participation as a founding team member
- Direct influence on product and technical direction
- High autonomy and decision-making authority
- Work with minimal hierarchy in a small, high-trust team
- Additional benefits commensurate with founding role
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
- Tell us about a time you shipped a full-stack feature end-to-end. What was your process, and what trade-offs did you make?
- Describe your experience in a 0-to-1 environment. How did you approach technical decisions when requirements were ambiguous or constantly changing?