> Markdown version of [/jobs/ext/2525041-telecommute-staff-frontend-engineer-feature-management](https://www.wearedevelopers.com/jobs/ext/2525041-telecommute-staff-frontend-engineer-feature-management). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # TELECOMMUTE Staff Frontend Engineer, Feature Management - **Company:** CATAMORPHIC CO. - **Location:** San Francisco, CA, United States (Remote available) - **Experience:** Expert - **Salary:** $214,800.0 - $295,350.0 - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Code Review, Programming Tools, Release Management, Software Engineering, TypeScript, ReactJS, Large Language Models, Backend, Front End Software Development - **Published:** August 19, 2026 - **Apply:** https://www.dice.com/job-detail/1870b274-5a59-439f-ac24-3df7633ae9bc ## About the Role * 10+ years of software engineering experience with deep frontend expertise, including a surface or system you owned across multiple teams you did not manage. * Strong with TypeScript and React. Our stack is TypeScript and React on the frontend and Go on the backend, and you should be able to work across the API boundary rather than stop at it. * Experience owning a design system that was genuinely adopted. We will ask about migration, enforcement, and what you did when teams did not adopt it, and we care about those answers more than the component library itself. * Product and UX judgment on top of engineering depth. You start from who the user is and what they are trying to finish, you can trace a workflow end to end across a product, and you can tell real friction apart from your own preferences. You hold that view in a room with designers and PMs as a peer. * A track record of cross-team influence without authority. Point to a standard you set, the coalition you built to get it adopted, and what actually changed in the product. * Judgment about leverage. The defining skill here is picking the few things that unlock the most, out of a backlog that will always be larger than one person. * Real experience with data-dense enterprise product UI: large collections, filtering, permissions, environments, bulk operations, and the performance work that comes with them at customer scale. * A point of view on agents in developer tooling. You have built with LLM tool use, MCP, or agent frameworks in production and have an argument about how agent-driven use changes product design rather than just adding a chat box. * Excellent written communication. Most of your influence will travel as documents, prototypes, and code review. ## Description You will work from the product backwards, and knowing who you are building for is most of the skill: * The platform engineer standardizing flag hygiene across two hundred services. * The product manager checking what is live before a customer call. * The release manager running a staged rollout under change control. * The support engineer tracing why a customer saw a variation last Tuesday. * The developer who delegates flag work to an agent, then reviews it. These people need different things from the same screens, and you will know their workflows well enough to tell which friction is worth fixing. Your levers are the shared frontend foundations underneath those surfaces: our design system, the interaction primitives whole classes of workflow depend on, and the platform capability we can pull in from upstream. When new capability lands in our component library, you are the person who knows the product well enough to say what it unlocks, which customer complaint it closes, and what it takes to get it into the product. That last persona is where the role turns forward-looking. An agent makes a change, then a person arrives to verify it and decide whether to trust it. They need it explained, with the blast radius legible before it lands. You will prototype those patterns and build the good ones into the foundations. Design and product are your closest partners in that, alongside the Enterprise and Foundation Feature Management teams who build on what you own., * Own the consistency and quality of the core flag surfaces across teams. Set the direction for how shared interactions work, review what teams build on these surfaces, and be accountable for whether the experience hangs together. ## Related Videos - [Microfrontends at Scale](https://www.wearedevelopers.com/videos/236-microfrontends-at-scale) - [Do TypeScript without TypeScript](https://www.wearedevelopers.com/videos/327-do-typescript-without-typescript) - [Watch Tests Go Brrrr! : Getting Started with Cypress in ReactJS](https://www.wearedevelopers.com/videos/282-watch-tests-go-brrrr-getting-started-with-cypress-in-reactjs) - [Developing the Backend with Stefan Lingler, CTO at Shpock](https://www.wearedevelopers.com/videos/100360-developing-the-backend-with-stefan-lingler-cto-at-shpock) - [Meet Your New BFF: Backend to Frontend without the Duct Tape](https://www.wearedevelopers.com/videos/682-meet-your-new-bff-backend-to-frontend-without-the-duct-tape) - [Nest.js - TypeScript in the backend can also be clean](https://www.wearedevelopers.com/videos/1033-nest-js-typescript-in-the-backend-can-also-be-clean) ## Related Articles - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [Never delegate the understanding](https://www.wearedevelopers.com/magazine/749-never-delegate-the-understanding) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Dev Digest 133 - Back to Front](https://www.wearedevelopers.com/magazine/474-dev-digest-133-back-to-front) - [Dev Digest 118 - not a total recall](https://www.wearedevelopers.com/magazine/452-dev-digest-118-not-a-total-recall)