Senior Full Stack Developer

Position: Senior Full-Stack Developer/AI SecurityLevel: Senior / Mid-SeniorLocation: Remote, with required onsite deep dives in Dallas, TexasHQ 2xmonthCompensation:Contract rate Market, potential contract to perm hireReports to: Engineering leadership / CTOCitizenship requirement: US CitizenEngaged through: SherlockTalent, on behalf of a SherlockTalent client (AI-driven cybersecurity startup, post-seed stage). 12 monthcontract, remote and onsite Dallas HQ

Overview

You're building integrations and product flows for a startup shipping human-in-the-loop AI security tools. The stack is chosen: TypeScript/Node on the backend, React frontend, Postgres, AWS + Kubernetes, and you're not rearchitecting it. What you own is shipping: integrating third-party security tools (Shop Defender, CrowdStrike, et al.), wiring those signals into product workflows, and keeping the whole thing coherent while the product still ships fast. You'll move at startup pace, make judgment calls with incomplete information, and distinguish between \"this is a security boundary and we're not moving it\" and \"this is a framework preference and it can wait.\"

What You'll Build

• Integration surface: APIs and data pipelines connecting Shop Defender, CrowdStrike, and third-party security data sources into the product layer — this is daily work, not occasional
• Product workflows: Wiring those integrations into customer-facing flows (triage, alerting, response loops) where the human-in-the-loop model is the core product, not a nice-to-have
• Backend services: TypeScript/Node services against a Postgres data store, deployed on AWS with Kubernetes orchestration
• Frontend logic: React layer for those workflows — integration data visualization and interaction, not heavy design work
• Operational resilience: Working with the team to ship observability, error handling, and retry logic that doesn't silently drop security alerts or create data inconsistency across integrations

Must Have

• 6+ years full-stack, with real hands-on depth in TypeScript/Node and React — not \"I know both,\" but shipping production systems on both sides regularly
• 2+ years building integrations or systems that depend on third-party APIs — not API consumption (hitting a single endpoint), but actual integration work: handling auth flows, data normalization across vendor differences, retry logic, versioning friction
• Production Postgres and AWS experience — you've optimized queries, you know RDS operational tradeoffs, you've debugged production database behavior, not just written DDL once and moved on
• Kubernetes deployment and troubleshooting in production — orchestration isn't theoretical; you've had to debug a container crash in prod or figured out why a deployment hung
• US Citizen (hard requirement — compliance/data handling constraint with this specific client)
• Judgment in ambiguity: You can move fast on a non-critical path and move cautiously on a security boundary without needing someone to tell you which is which

Note on AI tooling: You can use Claude, GitHub Copilot, or whatever else accelerates you. What disqualifies you is being good on paper but helpless when the AI link goes down. You've shipped systems this way multiple times before leaning on acceleration tools.

Explicitly Not Looking For

• Architects who want to redesign the stack. We picked it; you execute inside it
• Integration fetishists. You're not building an ETL platform; integrations are the vehicle, not the destination
• Pure product engineers without infrastructure comfort. You own ops visibility into your own code — deployments, observability, debugging in Kubernetes
• Candidates who need deep expertise in Shop Defender or CrowdStrike first. You learn those as you integrate them; the depth you bring is in systems thinking, not pre-existing product knowledge

Nice to Have

• Prior startup experience — you've shipped under time pressure and learned to ship strategically, not just fast
• Basic security registry or SOC-level familiarity — you understand alert triage, threat context, or what a detection rule looks like. Not required, but speeds time-to-useful in integrations
• Limited Python experience — not a primary language here, but useful for ops scripting or data pipeline work
• Texas residency or willingness to travel to Dallas regularly — the quarterly deep dives are real collaboration moments; timezone/travel proximity matters