Full-Stack Engineer
Bethesda, Montgomery County, Maryland, 20811, USA
Listed on 2026-08-24
-
Software Development
Full Stack Developer, React.js, Backend Developer
You must be authorized to work in the U.S. for this role. We are unable to offer sponsorship
Brass Tacks- $150K base
- Meaningful equity in an early-stage, venture-backed company
- We pay 100% of the premium for employee only coverage under one of our medical plans and 75% of the premium for dental and vision. Dependent coverage available, too.
- 401(k)
- High accountability + high flexibility culture
Two options:
- DC area: Our team and office are in Bethesda, MD. We work in person Monday, Tuesday, and Thursday. If you’re local or willing to relocate, that’s great but not required.
- Remote. You'll fly to DC for 3 days every quarter, and you'll keep significant overlap with Eastern hours for standups, pairing, and day-to-day communication.
Either way: this is a high-collaboration role. If you’re looking for async-only, heads-down remote work, this won’t be a good fit .
The OpportunityAs a Full-Stack Engineer you’ll report to our newly hired Principal Engineer and ship features and squash bugs with a strong appetite for continuous improvement. You’ll join a small team of 20 with 5 engineers including you. We're at a genuine inflection point: enterprise pilots running with named law firm clients, an AI-native engineering culture we’re actively building, and a platform foundation being rebuilt from the data layer up.
You’ll work day to day with our Principal Engineer and VP of Product, with regular exposure across the company. You’ll write production code every day, own end-to-end delivery on real client features, and pair on the harder problems.
We're looking for someone with genuine curiosity with the foundations to contribute on day one.
Our StackNext.js application (React, Type Script) with Aurora PostgreSQL on AWS. If you haven’t worked in this exact combination, that’s okay! Just having exposure to them and/or parallel technologies and ability to recognize similar patterns, identify opinions and differences between them are really what we value.
What You’ll Own- Features, end to end. Frontend through backend, ticket to production. Clean code, real tests, peer-reviewed PRs.
- Bug-fix work across the platform. Help us drive defect escape rate down quarter over quarter, and build the muscle memory of catching things before they ship.
- The testing and tooling foundation. Playwright suites, CI checks, our internal while having an awareness of alternative tooling.
- Architecture, in partnership. Pair with the Principal Engineer on the harder decisions and learn the stack at depth.
- The team’s bar. Raise it through your own code and through generous, specific code review
We care much more about how you think and how you operate than whether your résumé matches our stack.
- Solid foundations. You understand what your code does: data modeling, HTTP, state, async behavior, why the query is slow. You can debug something you didn’t write. You’ve built enough to have real opinions and enough humility to know where they came from.
- Genuine curiosity. You read source code when the docs are thin. You know why the tool you use works the way it does. You bring back things nobody asked you to look into.
- Drive. You move things forward without being pushed. You’d rather ship something imperfect and iterate than polish in private.
- You take ownership. You close loops: when you own something, the next step is clear without anyone chasing you. You flag and mitigate risk early instead of routing around it. You help people even if you don’t know the answer.
- Ambiguity is the norm. You don’t need fully spec’d out tickets to make progress. If you are stuck, you reach out while choosing a justifiable action over waiting for the next sync.
- Tests are part of writing code. Not a phase afterward, not someone else’s job.
- Dev Ops / Cloud Infrastructure . We are on Vercel & AWS. The more experience the better, knowledge of best practices from security and scaling standpoints are coveted.
- You’re open to an AI-native workflow. We use AI tooling heavily and we’re still figuring out where it belongs. You don’t need to be fluent yet — but you do need to be genuinely willing to work this way and skeptical enough to verify what a model hands…
(If this job is in fact in your jurisdiction, then you may be using a Proxy or VPN to access this site, and to progress further, you should change your connectivity to another mobile device or PC).