You will build the internal tools, shared libraries, and product-supporting infrastructure the rest of the company runs on.
You reach for Python, Rust, C++, or the browser depending on the problem.
You drop into an unfamiliar domain and form strong architectural opinions within a week.
You’d rather understand a problem deeply than be handed a spec.
You embed with the team you’re building for.
You ship them something early and then keep working next to them as it evolves and as you discover the shape of the final solution jointly.
The empathy you earn on the ground is what lets you build the right thing, fast.
Software Generalists build the tool the team didn’t know how to ask for.
Requirements
- You own outcomes. You don’t throw software over a wall. You talk to the people who’ll use what you build, most often colleagues down the hall, sometimes the users of our products. You sit with them, watch where they stumble, and find usability friction. "Done" means someone’s job got easier.
- You orient fast in unfamiliar territory. Dropped onto an arbitrary problem, you build an accurate mental model quickly of two things: the unfamiliar codebase or domain, and the unfamiliar human workflow underneath it.
- You architect for use and for change. Your software is well-built in the ordinary sense and shaped around how it will be used and how it will need to grow. You tend to pre-build the next feature request, because you know the user well enough to see it.
- Language-agnostic. You’ve shipped real software in more than one of Python, Rust, C++, and modern web stacks, and you treat languages as tools you pick up as needed rather than as an identity. You don’t need mastery of all of them on day one, you need to be someone who becomes competent in a new one fast.
- Strong systems and performance instinct. Some of our work lives or dies on performance. You have a felt sense for where the time and bytes go, and you reach for a profiler by reflex. A computer graphics or game-development background is a real plus. Other work barely touches any of it, and you can tell the difference and right-size your effort accordingly.
- Nice-to-haves
- Background in graphics, game dev, or real-time systems.
- Networking depth — you understand what happens when topologies get ugly.
- Rust and/or modern C++ in production.
- Experience owning internal tooling or developer-experience work.
- Comfort with hardware-in-the-loop or field-deployed systems.
- You’ve built the in-house version of something other teams usually buy.
Core Competencies
Demonstrates strong software development capabilities across multiple languages including Python, Rust, and C++, with a focus on building internal tools and product-supporting infrastructure. Exhibits a deep understanding of user needs and workflows to create efficient, adaptable solutions.
Highest-signal resume keywords
- Python Development
- Rust Development
- C++ Development
- Systems Performance Optimization
- Internal Tooling Ownership
ATS Optimization Keywords
Hard Skills
- Software Architecture
- Language-Agnostic Development
- Usability Testing
- Codebase Familiarization
- Performance Profiling
Soft Skills
- Empathy
- Collaboration
- Adaptability
- Problem-Solving
Industry Keywords
- Internal Tools
- Developer Experience
- Real-Time Systems
- Networking Topologies
Tools & Technologies
- Modern Web Stacks
- Profilers
- Graphics Development Tools
- Game Development Frameworks