> Markdown version of [/jobs/ext/259431-senior-software-engineer-rails-next-js-aws-govcloud](https://www.wearedevelopers.com/jobs/ext/259431-senior-software-engineer-rails-next-js-aws-govcloud). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Software Engineer (Rails / Next.js / AWS GovCloud) - **Company:** Continuous Compliance, LLC - **Location:** Baltimore, MD, United States (Remote available) - **Experience:** Expert - **Salary:** $125,000.0 - $175,000.0 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Amazon Web Services, Amazon S3, Software as a Service, Databases, Software Debugging, Identity and Access Management, Network Layer, PostgreSQL, Ruby on Rails, Redis, Next.js, Systems Integration, Web Applications, ReactJS, Large Language Models, Indexer, Backend, Microsoft InTune, Production Code, Front End Software Development, Functional Programming, Amazon Simple Queue Service (SQS) - **Published:** May 19, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=0f97ea9b02ddd849 ## About the Role Do you have experience in Web applications?, * 8+ years building production web applications, with at least 3 years in Ruby on Rails. Strong frontend experience in React, Next.js, or both. At this level we expect deep expertise in your primary part of the stack - you don't have to know every layer, but the layers you own, you should own thoroughly. * Real database fluency: query plans, indexing, transactions, migrations on live systems * AWS production experience (any region; GovCloud is a plus, not a prerequisite) * Ability to debug across the stack - frontend network errors, backend N+1s, container networking, IAM * Comfort working with AI coding tools as a force multiplier and explaining every decision they help you make * Strong written communication - async-first team, decisions live in tickets and PRs Nice to have * Microsoft Graph integrations (Intune, Defender, Entra) - much of our compliance evidence collection runs through Graph * AWS GovCloud, ECS, Bedrock production experience * Background in compliance, security, or regulated SaaS * Familiarity with CMMC, NIST 800-171, or FedRAMP ## Description We're hiring a senior engineer to build features end-to-end across our Rails/PostgreSQL backend, our React and Next.js frontends, and our AWS GovCloud infrastructure. This is a hands-on role: you'll work directly with a small, senior team, write production code daily, and contribute meaningfully to architecture, tooling, and how we ship. Our stack * Ruby on Rails + PostgreSQL (with pgvector) * React and Next.js on the frontend * AWS GovCloud: ECS, Lambda, S3, SQS, Bedrock, Redis * Microsoft Graph integrations (Intune, Defender, Entra) for evidence collection * Compliance frameworks: CMMC, NIST SP 800-171, FedRAMP How we work with AI tools We use AI tools heavily - across our development workflow, in our product, and in our recruiting pipeline. We expect engineers to be fluent with these tools and faster because of them. Our take-home exercise is built around AI-assisted work: use whatever tooling you'd use on a normal day. We don't allow AI tools during interviews, though, and the reason isn't that we distrust them - we use them every day. It's that interviews are where we meet you. We've sat across the table from candidates whose every answer was piped through a chatbot, and at the end of the hour we couldn't tell who we'd been talking to. We don't want an augmented personality - we want the real person. How you think. How you respond when you don't know something. How you handle being stuck. So during interviews, AI tools are off. Vibe coding doesn't ship at FutureFeed either. If an AI tool writes code you can't explain, can't debug, and can't reason about, that code doesn't go in. We want engineers who understand: * Why a Rails query is slow and how to actually fix it * What's happening at the network layer when an ECS task can't reach RDS * When a Lambda cold start matters and when it doesn't * Why an LLM output drifted and how to catch it next time If "I asked the AI and it worked" is a complete answer for you, this isn't the right role. If "the AI proposed this, I checked it against the indexes, the EXPLAIN plan, and the existing query patterns, here's why I'm shipping it" is how you talk about your work - read on. ## Related Videos - [Great DevEx and Regulatory Compliance - Possible?](https://www.wearedevelopers.com/videos/1426-great-devex-and-regulatory-compliance-possible) - [Reducing LLM Calls with Vector Search Patterns - Raphael De Lio (Redis)](https://www.wearedevelopers.com/videos/1714-reducing-llm-calls-with-vector-search-patterns-raphael-de-lio-redis) - [Developing the Backend with Stefan Lingler, CTO at Shpock](https://www.wearedevelopers.com/videos/100360-developing-the-backend-with-stefan-lingler-cto-at-shpock) - [Optimizing Discovery: PostgreSQL's Role in Transforming GetYourGuide's Search](https://www.wearedevelopers.com/videos/1647-optimizing-discovery-postgresql-s-role-in-transforming-getyourguide-s-search) - [Shipping Faster with Less: Render on Cloud Hosting, AI Workloads, and the Future of DevOps](https://www.wearedevelopers.com/videos/1894-shipping-faster-with-less-render-on-cloud-hosting-ai-workloads-and-the-future-of-devops) - [Accelerating Authentication Architecture: Taking Passwordless to the Next Level](https://www.wearedevelopers.com/videos/733-accelerating-authentication-architecture-taking-passwordless-to-the-next-level) ## Related Articles - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Dev Digest 119 - ❤️ === ❤️](https://www.wearedevelopers.com/magazine/454-dev-digest-119) - [Dev Digest 137 - AI'm not sure about this](https://www.wearedevelopers.com/magazine/485-dev-digest-137-ai-m-not-sure-about-this) - [Dev Digest 131 - AI'm not sure about OSS](https://www.wearedevelopers.com/magazine/472-dev-digest-131-ai-m-not-sure-about-oss) - [WeAreDevelopers Dev Digest Issue 116 - The new search wars…](https://www.wearedevelopers.com/magazine/445-wearedevelopers-dev-digest-issue-116-the-new-search-wars)