Staff Full-Stack Engineer, Forma.ai

• Extensive experience building and running production systems, including leading the design of a product area or platform
• Proficiency in Kotlin, Java, or a similar language, and comfort working across the stack, including a TypeScript and React frontend
• Strong SQL, relational schema design, and data modelling skills, including data models that had to change over many years
• A track record of good technical judgement. You can describe major decisions, what you rejected, and how they held up
• A track record of good product judgement. You have shaped what was built, and you can explain how you weighed customer value, cost, and risk
• Experience talking with customers or customer-facing teams and turning what you learn into product decisions
• Regular and critical use of AI coding tools, and a clear view on how a team should work with them
• Clear, precise writing. You do not expect others to read AI output. Your audience will put in as much effort reading your docs as you do writing them
• We know that applying to a new role takes a lot of effort. You're encouraged to apply even if your experience doesn't precisely match the job description

Desirable

• We build enterprise software that helps organizations optimize sales performance and improve go-to-market agility. Our engineering organization includes multiple product application teams responsible for delivering core customer-facing capabilities
• We are seeking Staff Software Engineers to join our TQM team. You’ll work alongside other staff, senior, and early-career engineers to design, build, and scale backend and frontend systems that power enterprise-grade product workflows. This is an opportunity to work on complex product and data problems while contributing meaningfully to technical decisions, system quality, and team delivery
• We are low on meetings and high on accountability. Most of the team is in the EST time zone, with a few located in AST, PST, and Central as well
• The TQM team builds the planning layer of Forma.ai’s platform. TQM stands for Territory and Quota Management. Sales operations teams use it to plan the deployment of large scale sales organizations: divide their target market among sellers, set and communicate targets, and manage changes during the year. Commissions, crediting, and reporting all depend on our data
• We build with AI tools every day, so writing code is rarely what slows us down. What matters more is how often a person makes the right call. For the staff role at Forma, that means strong product judgement as well strong technical judgement. You will decide what problem to solve, which customer request shows a real pattern and which is a one-off, how to actually build and deliver software at a high velocity in the new AI world, and how to build a system will hold up for years. The team’s direction will depend heavily on how well you make those calls
• Lead the design of TQM’s enterprise features, including permissions, audit history, and approval workflows
• You care about the product experience, working on both frontend and backend towards the goal of delivering strong experiences
• Design these features so that new product areas can use them without rebuilding them
• Learn from customers how planning is governed inside their organizations and turn that into a clear plan for delivery
• Decide what not to build. Cut scope that doesn’t serve a customer, and say so clearly
• Set the technical direction for how these features connect to the rest of the Forma.ai platform
• Write the design documents and decision records that the team builds from, and review others’ with a high bar
• Stay hands-on. Build the hardest parts yourself and make sure the result works in production
• Contribute heavily to product ideation discussions, and bring opinions
• Technologies we use:
• Frontend: TypeScript, React, TanStack Router and Query, Tailwind, shadcn/ui
• Backend: Kotlin, Spring Boot, Postgres
• Infrastructure: AWS, Kubernetes, Docker, OpenTofu
• Development: AI coding agents (Codex/Claude Code), used throughout design, implementation, and review
• What success looks like: 30/60/90 days
• First 30 days
• You’ll learn TQM by working in it, and learn what enterprise customers need from it
• By the end of your first 30 days, you will have:
• Set up your environment and learned your way around the services, web app, and infrastructure
• Shipped several changes to the production system, across more than one area of the product
• Read the team’s domain and design documents and learned the core planning concepts
• Spoken with product owners and customer-facing teams about enterprise requirements
• Shared an initial view of where the current system falls short of those requirements
• First 60 days
• You’ll set the direction for the enterprise features
• By the end of your first 60 days, you will have:
• Led the design of the permission model and the plan for audit history and approvals, from problem statement to an agreed design
• Changed the scope or order of that work based on customer evidence
• Got engineers building on the design, with the first pieces in review or in production
• Improved how the team designs, reviews, or tests its work
• First 90 days
• You’ll be the engineer the team relies on for direction
• By the end of your first 90 days, you will have:
• Delivered the first enterprise features to production, used by customers in their planning
• Made decisions that Product and Engineering both trust without needing to revisit them
• Started contributing to the direction of new product areas