Of the ten postings, Interos is the one that actually tells you something. A company hiring Haskell engineers onsite in Arlington, VA — a stone's throw from the Pentagon — is broadcasting its strategy louder than any press release could.

The stack tells the story. Haskell is a deliberate choice, not a default. Companies pick it when correctness matters more than hiring velocity: financial systems, compilers, and — increasingly — risk modeling. Interos does supply chain risk intelligence, which means graph traversal across millions of corporate entities, provenance tracking, and answering "if supplier X goes down, what breaks?" That's a domain where Maybe types and immutable data structures earn their keep. The parallel hiring for Data Science, Python, DevOps, TypeScript, and Designers suggests a classic bifurcation: Haskell for the analytical core, Python/TS for the customer-facing surface.

Stage and direction. Arlington + Haskell + hiring across ten function areas simultaneously = a Series B/C company scaling into federal contracts. The .ai domain and dedicated Data Science hiring signals they're positioning the risk graph as an ML product, not a consulting deliverable. The breadth of open roles (Product, Marketing, Design) means they're building the go-to-market motion in parallel with engineering — that's a company with runway and a board pushing for growth.

Trends this highlights:

• Supply chain risk as a category was already heating up pre-COVID; this posting (March 2020) is early positioning for what became a boom.
• Typed functional languages in enterprise — Haskell/Scala/OCaml shops are quietly proliferating in fintech and gov-tech where bug costs are asymmetric.
• Onsite-mandated roles with COVID exceptions — the "ultimately onsite" caveat reveals a clearance-adjacent business model. You don't insist on Arlington unless you need SCIF proximity.

Green flags: Direct contact email from what appears to be a hiring manager ([email protected]), specific technology commitment, transparent about the remote-during-COVID / onsite-long-term reality. Red flags: The posting is thin on team size, comp band, and what the Haskell codebase actually does. Serious Haskell candidates are picky — a job description that doesn't sell the technical problem will lose to Standard Chartered or Mercury. Also: "and more" as a category of open roles suggests reactive hiring rather than a workforce plan.