Senior Software Developer

Why Calcs Engineering and construction shape the world around us, yet many engineers still rely on outdated tools and time-consuming workflows. This creates inefficiency, risk, and frustration. We exist to fix that. Calcs is relied on by thousands of engineers, and we're building the next generation of engineering design tools — faster, safer, more collaborative, and increasingly powered by AI. When we save engineers hours each week, projects move faster and the industry levels up. This work is impactful and challenging. Standards differ by region, compliance matters, and correctness is non-negotiable. But our team is exceptional, and you'll work with people you trust, admire, and enjoy. We value ownership, autonomy, and outcomes over process. We treat each other like adults. Everyone contributes, whether it's shipping a major feature or taking out the bins. If this role feels a little intimidating, that's intentional. Why This Role Exists We have a strong product in market, new capabilities in active development, and ambitious plans to scale. What we need now is execution capacity: another experienced engineer who can pick up complex work, make good judgment calls, and ship. This hire will: Increase our ability to ship features customers are waiting forTake ownership of workstreams without needing constant directionBring the judgment to know when "good enough" is good enough, and when it isn't When we get this hire right, everything moves faster. The Role We need an engineer who knows when to ship a hack on Friday and when to spend two weeks doing it properly. You'll be a generalist on a small team. Most of your work will be frontend (TypeScript/React), but you’ll touch backend when needed (Ruby/Rails, PDF Exports). You're here to: ship features that customers use, fix things that break, and make judgment calls about trade-offs every day. This is not a management role. It's not a strategy role. It's an execution role with high autonomy and real ownership. What You'll Actually Work On The kind of work you'll do: Build a rich report authoring product. Help us expand the calcs.com report authoring functionality with templating, design layouts, and integrate it with our project calculators.Own a domain. Take charge of a new product surface area. Speak to customers, engage with stakeholders. Work closely with product and design to prioritise accordingly.Feature work across the product. Bug fixes, production support (we rotate on-call), and whatever else needs doing. We're a small team. What We're Looking For 5+ years building software professionally. Not 5 years of tutorials. 5 years of shipping things, breaking things, fixing things at 2am, and learning from it. Judgment You know when to cut corners and when not to. You'd ship a scrappy MVP for a feature 10 users will try, but you'd invest in proper error handling for something that processes customer data at scale.You know the difference between "technical debt we can live with" and "technical debt that will kill us."You've been burned by both over-engineering AND under-engineering, and you've learned from both. Autonomy You're comfortable with ambiguity. Sometimes the spec is "make it work like the old one but better."Sometimes you'll need to talk to a structural engineer to understand what they actually need.You don't need hand-holding, but you also know when to ask for help. Breadth You can learn new stacks. Our stack is Ruby/Rails + TypeScript/React + Python. If you know 2 of those well, you can learn the third. We care more about your judgment than your syntax. Communication You keep people informed without being asked. You raise blockers early, not the day before a deadline.Your PRs are clear. Your questions are specific.You can explain a technical trade-off to someone who isn't technical. Pragmatism You find simple solutions to complex problems and know that perfect is the enemy of good. You value team success over individual credit. Nice to have, not required: Experience in B2B SaaS, especially serving technical usersBackground working on developer tools, workflow platforms, or engineering softwareFamiliarity with data-intensive applications or ML-adjacent systemsExperience working in distributed/async teams What We're NOT Looking For "I only do backend." We're too small for hard specialization."I need detailed specs before I start." You'll often figure out the spec by building."Let's rewrite it in Rust." We ship in boring tech that works.Architecture astronauts. We value pragmatism over purity. Why This Job Is Interesting Your code matters. Engineers use our calculations to design buildings. That's real.Small team, big ownership. No waiting 6 months for a feature to ship. No committees.Interesting domain. Structural engineering is fascinating once you get into it. Steel connections, load paths, building codes. You'll learn things.Greenfield problems. We're actively building new capabilities, not just maintaining what exists.