ZipRecruiter

Log In

1

Mid Level Front End Developer Jobs in California

krg technology inc

Java Front End

Mountain View, CA · On-site

Bachelor's degree or foreign equivalent in Computer Science, Engineering (any), or a related field ... level technical design; and building applications using jQuery. Must have one (1) year of ...

Redolent, Inc.

Front End Developer

Sunnyvale, CA · On-site

$124K - $144K/yr

... level debugging and analysis skills using ADB - Experience with the application submission/provisioning process - Experience leading a small team of developers and delegating tasks - Excellent ...

Clera

AI Engineer (Mid-Level)

San Francisco, CA · On-site

$180K - $400K/yr

As a mid-level AI Engineer on the core product team, you'll own production LLM-based services end ... frontend and backend code, and operating production systems with CI/CD, monitoring, and testing.

Clera

AI Engineer (Mid-Level)

San Francisco, CA · On-site

$180K - $400K/yr

As a mid-level AI Engineer on the core product team, you'll own production LLM-based services end ... frontend and backend code, and operating production systems with CI/CD, monitoring, and testing.

Stanfield Systems

Java Developer - mid

Folsom, CA · Remote

$50 - $58/hr

Mid-Level Java Developer Experience:3-6 years Start Date:7/15/2026 Type: W2 Employee Base location ... Java EE / Jakarta EE(with WildFly or JBoss) * Front-end development with HTML, CSS, and JavaScript

Jobsbridge

Sr. Front-End Developer

San Jose, CA

$134K - $177K/yr

... next level. 5+ years relevant experience Responsibilities: Take detailed requirements,determine the right front-end strategy and craft exceptional user experiences. Collaborate closely with the ...

previous page

Showing results 41-60

All JobsMid Level Front End Developer JobsMid Level Front End Developer Jobs in California

Mid Level Front End Developer information

See California salary details

$41.9K

$109K

$153.5K

How much do mid level front end developer jobs pay per year?

As of Jul 31, 2026, the average yearly pay for mid level front end developer in California is $108,967.00, according to ZipRecruiter salary data. Most workers in this role earn between $102,600.00 and $119,400.00 per year, depending on experience, location, and employer.

What are the key skills and qualifications needed to thrive in the Mid Level Front End Developer position, and why are they important?

To thrive as a Mid Level Front End Developer, you need solid proficiency in HTML, CSS, JavaScript, and modern frameworks like React or Angular, typically supported by a relevant degree or practical experience. Familiarity with version control systems like Git, responsive design tools, and optionally certifications such as Microsoft Certified: JavaScript Developer add value. Strong collaboration, problem-solving abilities, and effective communication distinguish top performers in this field. These skills ensure that you can build user-friendly, high-quality web interfaces and work efficiently within cross-functional teams.

What are some typical daily responsibilities for a Mid Level Front End Developer?

Mid Level Front End Developers spend much of their day coding and refining user interfaces based on project requirements and feedback from stakeholders. They regularly collaborate with designers and back-end developers to ensure seamless integration of visual and functional elements, as well as participate in code reviews to maintain high quality standards. Additionally, they often troubleshoot bugs, optimize page performance, and keep up with the latest web technologies to improve user experience. This role blends both independent problem-solving and teamwork in a dynamic, fast-paced setting.

What is a Mid Level Front End Developer job?

A Mid Level Front End Developer is responsible for building and optimizing the user interface of web applications using HTML, CSS, and JavaScript frameworks like React or Vue. They collaborate with designers and back-end developers to ensure a seamless user experience. Typically, they have 2-5 years of experience and are expected to write clean, maintainable code while troubleshooting UI/UX issues. Additionally, they may contribute to component libraries, improve performance, and follow best practices in responsive design and accessibility.

What are the most commonly searched types of Front End Developer jobs in California? The most popular types of Front End Developer jobs in California are:
What are popular job titles related to Mid Level Front End Developer jobs in California? For Mid Level Front End Developer jobs in California, the most frequently searched job titles are:
What job categories do people searching Mid Level Front End Developer jobs in California look for? The top searched job categories for Mid Level Front End Developer jobs in California are:
What cities in California are hiring for Mid Level Front End Developer jobs? Cities in California with the most Mid Level Front End Developer job openings:
Mid Level Front End Developer jobs near you
Infographic showing various Mid Level Front End Developer job openings in California as of July 2026, with employment types broken down into 82% Full Time, 6% Part Time, 1% Temporary, and 11% Contract. Highlights an 83% Physical, 4% Hybrid, and 13% Remote job distribution, with an average salary of $108,967 per year, or $52.4 per hour.

Staff Frontend Engineer (Design Systems & UX)

Deep Origin

South San Francisco, CA • On-site

Full-time

Medical, Dental, Vision, Life

Posted 15 days ago

Job description

About Deep Origin
Deep Origin is a biotech startup building an operating system for science that transforms how life science research is conducted. Led by Michael Antonov, co-founder of Oculus, and backed by Formic Ventures, we are redefining the infrastructure behind modern drug discovery. Our AI-driven platform enables scientists to accelerate discovery, reduce cost, and bring breakthrough innovations to life faster. As we scale, engineering excellence is a critical lever in advancing our mission to dramatically reduce disease and extend human healthspan.
Role Description
This is a Staff-level frontend engineering role for someone with strong product and UX judgment. You'll architect and ship the front-end systems behind an operating system for science, while helping define whether the product is actually good to use, not just functional. We don't have a dedicated product design team, so frontend engineers play a direct role in shaping interaction design, usability, and product quality. We want an engineer who can look at a complex scientific workflow, identify what is unclear or inefficient, propose a better direction, and ship high-quality product UI in close collaboration with the team.
As a Staff engineer you set technical direction for the front end: component architecture, the design system, state management patterns, performance budgets, and the standards that keep the codebase coherent as the team and product grow. You also bring strong product and UX judgment to how our tools look, feel, and behave across drug discovery tools, simulation interfaces, data explorers, and research workflows. In this role, frontend architecture and product UX are tightly connected: you help define the point where design quality meets production code. You raise the team's craft through architecture, shared patterns, code review, pairing, and pragmatic product judgment, helping the team ship interfaces that are coherent, usable, and technically sound.
Requirements
  • 7+ years building production web applications, with deep command of React, TypeScript, JavaScript, CSS, and HTML, and a track record of owning front-end architecture from design through ship.
  • Real technical leadership. You've set front-end standards, made architecture decisions, and pulled up the engineering bar for a team, not just shipped your own features.
  • Strong design instincts and spatial sense. You notice when the padding is off, when a flow has one step too many, when a table is burying the column that matters.
  • Experience with data-heavy, workflow-heavy, or tool-heavy products: scientific software, developer tools, analytics platforms, design tools, or similar.
  • Comfort with ambiguity. Hand you a loosely defined problem and you'll sketch a few approaches and make the case for one.
  • Product thinking at the interaction level. You ask whether the flow makes sense and whether the user has enough context, not just whether the screen looks good.
  • Solid front-end fundamentals at scale: state management, responsive and cross-browser work, testing, performance profiling, and clean version control habits.
  • Comfort with data visualization past the standard chart library, where the visualization is the interface.
  • A portfolio or body of work that shows craft, ideally with code you can talk through.

Nice to have
  • Experience with scientific or biotech software.
  • Background in or exposure to computational chemistry, biology, or physics, scientific research workflows, or drug discovery.
  • Experience establishing design patterns or component standards on a team without dedicated product designers.
  • Familiarity with 3D rendering or molecular visualization libraries (e.g., Mol*, NGL, 3Dmol.js) or WebGL.

What This Isn't
  • A visual or graphic design role. We're not looking for someone to make marketing assets.
  • A design-only role where you hand off specs. You write and ship the code.
  • A standard frontend role with a "design eye." The title says Frontend Engineer because you architect and ship code at a Staff level, but you'll be driving UX and design decisions, not implementing someone else's.
  • A design manager role. This is hands-on IC work.

What you'll do
  • Architect and ship the front end. Lead component architecture, the design system, and shared front-end infrastructure in React and TypeScript. You write reusable, well-tested code that holds up as the team and product grow. You're a committer, not a consultant: you open PRs, review frontend code, and hold the quality bar in the codebase yourself.
  • Set front-end technical direction. Drive decisions on state management, rendering strategy, performance budgets, and the patterns that keep the platform coherent, and write the RFCs and reviews that get the rest of the team on the same page.
  • Turn ambiguous product intent into concrete UI direction. Pull context from Product, Science, Engineering, leadership, customer feedback, Slack threads, prototypes, and existing workflows. Synthesize that input into clear flows, lightweight specs, implementation plans, and shippable UI.
  • Define the UX patterns the platform runs on: Shape patterns for navigation, data display, workflow composition, error and empty states, loading behavior, progressive disclosure, and complex multi-step flows. Turn repeated product needs into reusable component and interaction standards
  • Make user flows coherent end to end. Context should carry through each step, the next action should be obvious, and the surrounding UI should help rather than get in the way. The flow has to solve the user's problem, not just look clean.
  • Prototype and build production UI for complex scientific workflows: work on multi-step pipelines, parameterized simulations, molecular viewers, results dashboards, and other data-heavy research workflows.
  • Work directly with complex scientific and technical data. Understand what a researcher needs to see, how they need to manipulate it, and how to make dense workflows, structured results, simulations, and visualizations understandable and actionable.
  • Integrate the front end with backend APIs and distributed platform services. Keep the product reliable and fast across browsers, devices, and environments.
  • Treat performance and accessibility as engineering work, not polish. Set performance expectations, chase down bottlenecks, improve accessibility, and pay down UI and technical debt as part of normal product development.
  • Find and fix UX debt. Improve screens that were never fully designed, flows that were stitched together over time, and inconsistencies that accumulated as the product evolved.
  • Set and evolve frontend engineering standards. Help define expectations for automated testing, code review, CI gates, component quality, accessibility, and maintainability as the platform scales.
  • Raise the team's product and frontend craft. Pair with engineers, review code, share patterns, and make product-quality concerns visible early. Help the whole team build better judgment so quality does not depend on one person being in every conversation.
  • Make pragmatic product and interaction decisions. Use strong judgment on layout, hierarchy, motion, and interaction design. When the path is clear, move quickly; when tradeoffs are meaningful, frame the options and drive alignment with Product, Engineering, Science, and leadership.

Values & Working Style
  • High agency. You do not wait for perfect specs. You pull context, identify the missing decisions, propose a path forward, and create momentum.
  • Ownership. You care about the full path from product intent to production behavior. You stay close to the details until the product works well for users.
  • Comfort with ambiguity. You can operate in an early, fast-moving company where requirements are incomplete, priorities shift, and the best way to align is often to make the work concrete.
  • Clear communicator. You work well with both technical and non-technical people. You can explain tradeoffs, frame options, and make complex product or technical decisions easier to reason about.
  • Pragmatism. You optimize for impact, not for being right. You know when to prototype, when to systematize, when to pay down debt, and when to move quickly.
  • Bias toward working software. You use prototypes, preview environments, and production code to make product discussions concrete.

Location, Work Authorization & Benefits
  • This role requires working onsite in San Francisco at least 3 days per week.
  • Applicants must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment visa at this time.
  • Competitive compensation package with meaningful equity.
  • Comprehensive health, dental, and vision coverage.
  • Annual team gatherings and company events.
  • Free lunch, snacks, beverages, and onsite gym access (for in-office employees).
  • The opportunity to shape the future of health, longevity, and our ability to simulate life.

Why This Role Matters Now
As we scale our AI platform and expand into new scientific initiatives, the quality of our interfaces directly shapes what researchers can accomplish. Complex science becomes more useful when the product makes workflows understandable, decisions clear, and powerful tools accessible. This role sets the craft bar for the frontend engineering and product UX at a point where we're growing fast. The job is making complex science usable, to turn ambiguity into shippable product, and to help the team build interfaces that are coherent, fast, reliable, and worthy of the science behind them.

Apply