Explore 83 open design systems jobs at fast-growing tech, startup, and AI companies hiring right now. Own the component library and design tokens every other frontend team reuses.
Open Positions83 Design Systems jobs
The engineering career ladder
Most software engineering careers begin the same way. You start in an internship or new-grad role, get promoted to Software Engineer, then to Software Engineer II as you begin owning features on your own. This shared early track is where the fundamentals get built: shipping code, reviewing pull requests, and learning how a real production system behaves under load.
Around the senior level the ladder splits. You can keep going deeper on the technical side as an individual contributor, or move toward leading people on the management side. One is not a promotion over the other. Most companies pay a Staff Engineer and an Engineering Manager the same, so the real question is which work you want to do all day.
The pivot point: Senior Engineer
Senior is where most engineers choose. If you like mentoring, planning, and getting more out of a team, the Tech Lead and Manager path fits. If you would rather stay close to the code and own the hardest problems, the Staff and Principal path is yours. You can start down one and cross over later.
What changes as you climb
- Pay bands overlap across the two tracks at every matching level. A Staff Engineer (L5) and an Engineering Manager (L5) are peers.
- The IC track narrows fast near the top. There are far more Senior roles open than Principal or Distinguished ones, which the live counts show.
- Management roles cluster at scale-ups and larger companies. Early-stage startups hire mostly ICs.
- Switching tracks later is common. Plenty of Directors were once Staff Engineers, and the reverse happens too.
Where everyone starts
Individual Contributor
Illustrative titles and pay. Real ladders vary by company. Counts are live open roles matching each level.
IC vs. Management, side by side
| Individual Contributor | Management | |
|---|---|---|
| Core work | Architecture and the hardest technical problems, hands on the code | People, delivery, hiring, and coordinating across teams |
| Judged on | Technical impact and the systems you make possible | Team output, growth, and retention |
| A normal day | Design docs, prototypes, long stretches of focus | 1:1s, planning, unblocking people, reviews |
| Scope grows by | The reach and depth of your technical influence | The size of the org you lead |
Kinds of engineering
Engineering is a wide field. Most people specialize in one area over time, and the day-to-day work looks different in each. Here are the main tracks and what they cover.
Engineering jobs: common questions
What does a software engineer do?
A software engineer designs, writes, and maintains the code behind an application or system. Day to day that means building features, reviewing other engineers work, fixing bugs, and keeping the software running in production. The exact focus depends on the area, from frontend and mobile to backend, infrastructure, and machine learning.
How do I become a software engineer?
Most engineers get in through a computer science degree, a coding bootcamp, or self-study plus a strong portfolio of real projects. Companies care most about what you can build, so shipped projects and a clean GitHub often matter more than the path you took. Internships and open-source contributions are the usual way to land a first full-time role.
What is the difference between the IC and management tracks?
The individual contributor (IC) track keeps you close to the code and the hardest technical problems, growing from Senior to Staff to Principal. The management track shifts you toward leading people, from Tech Lead to Engineering Manager to Director. Most companies pay the two tracks the same at each level, so it is a choice about the work, not a promotion.
Which programming languages should I learn?
Start with one language you can go deep in, then add breadth. TypeScript and Python are the safest first picks because they show up across web, backend, data, and AI work. From there, Go and Rust are strong for systems and infrastructure, Swift and Kotlin for mobile, and SQL is worth knowing no matter what you build.
Do software engineers need a degree?
No. Plenty of working engineers are self-taught or came through a bootcamp. A degree helps with some larger companies and visa cases, but most teams hire on demonstrated skill: your projects, how you reason through a problem, and how you perform in the technical interview.
How much do software engineers make?
Pay ranges widely by level, location, and company. In the US, a mid-level engineer commonly lands in the range shown on this page, senior and staff roles go higher, and total compensation at larger companies includes equity on top of base. The live salary bands above are illustrative; the open roles listed here show real postings.
Explore other roles
Browse open roles in other functions across tech, startup, and AI companies.
Find the buyers, run the deals, and grow revenue.
Turn raw data into models, metrics, and decisions.
Keep the company running and the trains on time.
Decide what to build and why, then get it shipped.
Get the right people to hear about the product.
Build the physical thing: chips, robots, spacecraft, and the machines that run them.
Engineering jobs by location
View all locations →See where engineering roles are concentrated, by state and city.
San Francisco, Los Angeles, Costa Mesa hiring.
New York, New York City, Brooklyn hiring.
London, Manchester, Bristol hiring.