Software Engineer, Full Stack
Email us your résumé and links to your LinkedIn, GitHub, portfolio, or anything else you think we should see
WaveCX is looking for full-stack software engineers who can take product work from requirements through production.
You’ll work from a mix of PRDs, designs, existing product patterns, and sometimes functional low-code front-end prototypes. From there, you’ll work out what needs to be built, identify gaps or questions, and turn the idea into production-ready software.
We don’t expect every requirement to prescribe exactly how something should be built. We want engineers who are comfortable understanding the problem, exploring the existing product and codebase, asking good questions, and making thoughtful technical decisions.
You’ll work within the engineering standards, architecture, and development processes established by our Director of Software Engineering and CTO, with plenty of room to own your work and how you approach it.
Our technology
WaveCX is a multi-tenant SaaS platform used by financial institutions. Our product spans a web application, backend services, databases, cloud infrastructure, and client SDKs that run inside our customers’ own web and mobile applications.
Our core technology includes TypeScript, Node.js, React, C#, PostgreSQL, Google Cloud Platform, and Microsoft Azure. We also maintain SDKs for the web, native iOS, native Android, and React Native.
You do not need prior experience with every technology in our stack. Experience with some of them is useful, but we care more about strong software engineering fundamentals, the ability to learn an existing system, and experience building and shipping production software.
Because our product crosses application and platform boundaries, engineers sometimes need to think beyond a single layer of the stack. A feature may involve changes to a React interface, an API or service, a relational data model, permissions or authentication behavior, cloud infrastructure, or one of our SDKs.
Our development process includes GitHub-based workflows, code review, automated testing, and CI/CD pipelines used to move changes safely from development through production. Engineers should be comfortable working within those processes and helping improve them as the product and team evolve.
We value engineers who are comfortable understanding how these pieces fit together, identifying technical implications that may not be explicitly called out in a requirement, and choosing an implementation that works well within the broader system.
What you'll do
- Own features from requirements through production.
- Turn PRDs, designs, prototypes, and product concepts into working software.
- Build across the front end, APIs, services, and supporting infrastructure as needed.
- Design relational data models and work directly with SQL when appropriate.
- Take prototypes and low-code implementations and turn them into maintainable production software.
- Work closely with product and design to work through questions, gaps, and technical considerations.
- Make technical decisions within your area while knowing when to bring in engineering leadership.
- Think through edge cases, permissions, validation, error handling, performance, security, and how new work fits with the existing product.
- Work within our GitHub workflows, including branches, pull requests, code reviews, automated testing, and CI/CD processes.
- Write code that other engineers can understand, maintain, and extend.
- Test your own work and get it into good shape before it reaches QA.
- Work with QA to make sure expected behavior is understood and issues are resolved.
- Stay involved through release and address problems that come up along the way.
- Participate in code reviews, architecture discussions, estimation, planning, and improvements to how we build software.
- Work within the engineering processes and technical direction established by the Director of Software Engineering and CTO.
How we work
We want engineers to have real ownership of their work and the trust to make decisions.
If you’re responsible for a feature, we want you involved throughout its life: understanding the problem, figuring out the approach, building it, testing it, working through QA, and helping get it safely into production.
Ownership doesn’t mean working alone. Asking questions early is encouraged. So is disagreeing with a requirement, design, or technical approach when you see a problem. Product, design, engineering, and QA should be working together rather than throwing work over the wall to one another.
Some problems will be well defined. Others will require investigation and judgment. You’ll have support from the Director of Software Engineering, CTO, product, design, and the rest of the engineering team, but you’ll also have the space to work through problems yourself.
We’re a relatively small team, so we try to avoid unnecessary handoffs. The goal is for everyone to have enough context to understand what they’re building, why it matters, and how their work fits into the larger product.
Who we're looking for
- Strong professional experience building modern web applications.
- Comfortable working across both front-end and back-end systems.
- Experience taking meaningful features from concept through production.
- Strong understanding of APIs, application architecture, relational data models, SQL, authentication, and modern front-end development.
- Experience working with Git-based development workflows, pull requests, code review, automated testing, and CI/CD.
- Ability to translate designs and prototypes into polished, responsive interfaces.
- Comfortable starting with a PRD, Figma design, prototype, or existing product pattern rather than a fully prescribed technical solution.
- Good judgment about when to make a decision and when to bring others into it.
- Comfortable learning and working within an existing codebase.
- Able to break larger requirements into sensible technical work.
- Strong debugging and problem-solving skills.
- Thoughtful about quality, maintainability, security, and production behavior.
- Clear, collaborative communication with engineers, designers, product, and QA.
- Comfortable occasionally working directly with customers, partners, or their development teams to understand requirements, troubleshoot integrations, and work through technical questions.
The kind of engineer who tends to enjoy working here
You like understanding the problem behind what you’re building.
You’re comfortable being given context and a desired outcome, then working through how to get there. You notice things that weren’t explicitly called out in the requirements and bring them up. When you’re unsure, you ask. When you have enough information to make a reasonable decision, you make it.
You care about the experience beyond your own code. If something isn’t working correctly in QA or production, the question is less about whose part it was and more about how the team gets it right.
You also like working with people from different disciplines. Some of the best solutions come from an engineer, designer, product person, or QA person noticing something the rest of us missed.
The team
You’ll work with our Director of Software Engineering and CTO, along with other engineers, product, design, and QA.
Engineering leadership sets technical direction, architecture, standards, and development processes. Within that structure, engineers have room to make decisions, suggest better approaches, and take responsibility for the areas they’re working in.
We’re building software for financial institutions, so reliability, security, accessibility, and quality matter. But we also want the process of getting there to be collaborative, practical, and enjoyable.
The basic expectation is simple: understand what we’re trying to build, care about getting it right, and work with the rest of the team to get it there.