FutureFeed — Compliance SaaS for the Defense Industrial Base
Please only apply if you’re a U.S. citizen or lawful permanent resident currently residing in the U.S.
Final round in-person in Baltimore, MD (all travel covered) — required
Proceed only if you are willing to supply a prototype. Read the rest of the application for details.
About FutureFeed
FutureFeed (built by Continuous Compliance LLC) is the compliance platform organizations use to safeguard U.S. government–sensitive information. Founded in 2019, we serve over 1,200 clients ranging from Fortune 100 companies to top IT and cybersecurity service providers and small-to-medium businesses across regulated industries. We run on AWS GovCloud, and our customers — engineers, security officers, and CISOs at organizations whose contracts depend on accurate, defensible compliance evidence — rely on us to get it right.
The role
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.
PolicyMe
Veeva Systems
Veeva Systems
Veeva Systems
Veeva Systems
FutureFeed
