Summary
✨ AI‑Generated
Join a small, fast-moving engineering team as a full-stack developer with ownership across the entire application stack. You will build user-facing interfaces, APIs, and database systems while taking product ideas from concept through launch and iteration.
Highlights
High-ownership role at a small, fast-moving team where engineers work across the entire stack, own product problems end to end, and collaborate closely with technical leadership.
Description
Boulder, CO | Remote or Hybrid
Jawa is the marketplace for gamers - we sell gaming PCs, GPUs, consoles, and the like.
We've been operating since 2021, we're a small team with a big business, and we're looking for an engineer who is excited about real ownership over the future of the product.
What you'll do
This is a full-stack engineering role at the center of how Jawa works.
You'll build and ship across the entire stack: from the TypeScript components and pages gamers use to browse and buy, to the API controllers and Postgres layer that power listings, payments, and inventory underneath.
You'll work closely with the CTO and own product problems end to end: understanding what needs to be built, turning general direction into a real feature, shipping it, and iterating once it's in users' hands.
The exact surface area will shift with the business - one stretch you might be deep in marketplace and payments flows, the next you're improving search, inventory management, or on-call tooling.
Write Typescript components and pages for a Next.js marketplace websiteMaintain and extend a Typescript API controllers and work with PostgresReview code and deploy changesProvide on-call support and address system outagesTake general direction and turn it into real product features, flagging better ideas and edge cases along the way instead of just executing tickets
Compensation is up to $135,000, depending on experience.
We'd prefer someone with 4+ years experience in a similar role, but we care more about demonstrated ownership and a real history of building things that people use.
Required skills
Self-directed - you can take a feature from spec to shipped without hand-holding.Some experience deploying and debugging TypeScript code in a production setting.Familiarity with Next.js, Postgres, Git, and CI/CD workflows.
Comfort with the command line and experience with networking / operations strongly preferred.
Bonus points for experience configuring production environments (Docker, configuration management tools / platforms), handling system outages, and using observability platforms like Grafana.Extra points for familiarity with ecommerce / marketplaces, payments (Stripe), search, and/or inventory management systems.Excellent written communication and a proactive, product-minded streak.
We’re fully remote and mostly work asynchronously.
It’s a start up and things move fast, so a curious (and chatty) personality will find a lot of ways to make a big impact.Familiarity using AI coding tools (Claude Code, Codex, Cursor, etc.) to multiply your output, and strong judgment about where AI adds real value and where a simpler solution is better.Bonus points if you’re a gamer, tinkerer, or PC builder
Why Jawa
We're a small, scrappy team building something gamers actually use and love.
You'll have outsized ownership here: your code ships fast, your product instincts matter, and you'll see the impact of your work immediately.
As a startup there’s a lot that needs doing and things can move fast, but we’re typically flexible with time and work autonomously.
How we hire
The best signal is real work, so this process ends with a paid trial: you'll take on a real, scoped ticket or feature from our backlog and ship it, so we both know how it'll actually feel to work together before either of us commits.
Before that, we'll have a couple of conversations to talk through your background and the impact you've had at past companies.
How to Apply
Email andrew@jawa.gg with subject line JAWA DEV and include your resume / github (?) and answers to the following questions:
Share two or three products you personally owned from problem framing through shipped impact or tested prototype.
Include links where possible.Describe a feature you built.
What did you own, what technical choices did you make, and what was the result?Explain a bug you debugged.
What made it tricky, how did you track it down, and what did you learn?Take a quick look at Jawa and one or two relevant competitors.
Where’s the biggest product opportunity to improve versus the market?