Senior Software Engineer

Taxually; United States; Remote; USD 140,000 - 190,000; Full time

Job summary

Taxually is seeking a (Senior) Full-Stack Engineer to design and shape our tax-domain systems using .NET/C# backend and Angular UI on Azure. This architecture-heavy role emphasizes domain understanding and scalable design over routine coding, with AI-assisted development.

You'll work remotely across Europe time zones, owning major initiatives end-to-end and collaborating with tax experts to ensure robust, auditable outputs. Strong communication and architectural clarity are essential.

Qualifications

• Strong understanding of full-stack design in .NET/C# and Angular.
• Ability to design scalable architectures for tax-domain workflows.
• Clear communication with engineers and tax experts.

Responsibilities

• Architect the system across the .NET backend and Angular UI.
• Own one major initiative from design to production and beyond.

Skills

.NET/C#

Angular

Azure

Architecture

Communication

Tools

AI coding assistants

Azure DevOps

Job description

About the role(Senior) Full-Stack Engineer · .NET/C# + Angular on Azure · Remote (Europe time zones) · Full-time

We're hiring a senior engineer. Strong mid-level engineers are welcome to apply too: we judge the work, not the job title.

Taxually automates tax compliance across 117 countries. We don't stop at generating returns: we support clients through the whole flow, from data clean-up to submission.

How we work

One Big Thing. Every engineer owns one major initiative end-to-end instead of juggling features.

DigOps handles the noise. A dedicated team absorbs operational disruptions so you can stay focused.

Artifacts over tickets. Meeting notes, sketches and design docs beat detailed ticketing.

Minimal ceremonies. Monday standup, Wednesday async check-in.

Tax experts own the domain logic; engineers build the system that lets them.

No layers of approval, no waiting for permission.

What you'll do

This is an architecture role. You'll spend more time understanding the domain and shaping the system than typing code: AI writes most of that. Our best work happens when the people who know tax can change the system without waiting for an engineer, and your job is to design the ground that lets them, across the .NET backend and the Angular admin UI.

Go deep into the tax domain: learn how returns, templates, periods and corrections actually work, from the tax experts who own them.

Design architectures that follow the domain cleanly, so the code says what the business means and doesn't need workarounds.

Own one major initiative from design to production.

Make design calls on a live system that files real returns with tax offices. Filed output must never change by accident.

Write your designs down clearly, so engineers, tax experts and management can all follow and challenge them.

Use AI coding assistants as your main way of building, and review their output with an architect's eye.

What we're looking for

We hire for three things: clear communication, deep understanding of the domain, and the ability to design systems that fit that domain cleanly. We like simple solutions to simple problems, and we'd rather fix the model than add a plugin architecture.

You communicate clearly. You can explain a design in plain words to an engineer and to a tax expert, in writing and out loud.

You go deep on the domain. You ask why a rule exists before you decide where it lives, and you don't stop at the first plausible model.

You design clean architectures. Boundaries follow the domain, each responsibility sits in one place, and the design doesn't bend the domain to fit the code.

You've done it on real systems. You've designed and shipped changes to production systems that other people depend on, and you can walk us through why they're shaped the way they are.

Hiring process

There's no CV screen. We email you a short design task taken from a real problem we're working on now. We reply by email with the task. Do the task at home. AI use is allowed and expected. We review your answers. You'll hear back either way, with feedback. 60-minute discussion. We go through your answers together with two engineers from the team.

The task

The task isn't a coding exercise. It's a high-level architecture and systems design question, based on a real problem we're working on now. You'll get a short description of how part of our system works today, a goal, a hard constraint, and a few questions about how you'd design the solution.

There's no single right answer. We want to see how you think about problems: how well you understand the domain, where you put each piece and why, and how clearly you explain it. Everything you need is in the task itself.