Build serious cloud infrastructure. Skip the bureaucracy.
Talogen brings senior AWS, Azure, Google Cloud and DevOps engineers onto well-scoped client builds. The architecture is settled before you start, the work is pure infrastructure as code, and nobody asks you for status reports.
Senior engineers who’ve built the thing, not just used it
Cloud and platform engineers
who've built landing zones, not just deployed into them
Terraform specialists
who write modules other people want to reuse
DevOps and DevSecOps engineers
fluent in GitHub Actions, policy-as-code and keyless deployment
Data migration engineers
who've cut over production databases and slept fine afterwards
AI data-layer engineers
who've built retrieval pipelines on pgvector, Pinecone, Bedrock, Azure AI Search or Vertex AI
Depth on one cloud is essential. Working knowledge of a second is a strong plus.
Six things we actually commit to
Blueprints before tickets.
You start with a target-state architecture, ADRs and a sequenced backlog with acceptance criteria. You won't spend week one working out what the client wants; that was done in Steps 1 and 2.
Infrastructure is code. Full stop.
Every resource lives in Terraform and every change goes through a pull request. You won't be asked to “just fix it in the console.”
AI handles the boilerplate. You handle the judgment.
We expect you to use AI coding assistants for scaffolding, repetitive modules, test stubs and documentation drafts. That frees your hours for architecture calls, edge cases and code review, the work that needs a senior engineer.
No micromanagement.
Communication is asynchronous and in writing, against milestone dates. Your hours aren't tracked by the minute, nobody watches your screen and there's no daily stand-up. Ship reviewable work, flag blockers early and plan your own week.
Zero administrative bloat.
Work is remote, on a contract or C2C basis. Each engagement has one statement of work with defined deliverables and a rate agreed up front. There are no timesheet portals, no compliance-training carousel and no five layers of approval.
One point of contact.
Strategy, client communication and scope belong to the engagement lead. You deal with one person, and that person protects your time from scope creep.
Recent and typical workstreams
- Zero-trust landing zones on AWS Control Tower, Azure Landing Zones and Google Cloud resource hierarchies
- Keyless GitHub Actions pipelines with OIDC and workload identity federation
- Data-center exits: database replication, rehearsed cutovers, rollback plans
- Vector data layers that make a company's documents searchable by AI, with permissions enforced
- SOC 2 and HIPAA control mapping and evidence automation
- Cost-optimization sprints that find the money and implement the savings
Three steps, no recruiter theatre
Send your profile.
Email your résumé or LinkedIn and GitHub, plus a few lines on the hardest infrastructure problem you’ve solved, to [email protected] with the subject line “Bench.”
Have a technical conversation.
It’s 45 minutes with our engagement lead, focused on architecture and trade-offs. No whiteboard puzzles and no trick questions.
Join the bench.
When a workstream matches your stack and availability, you get the brief, the scope and the rate before you commit to anything.
Being on the bench doesn’t guarantee hours. It means you’re first call when work matches your skills, and we’ll be straight with you about timing.
Talogen Systems LLC is an equal opportunity company. We evaluate engineers on their skills and their work, nothing else. If you need an accommodation at any stage, tell us. See our Equal Opportunity Statement and how we handle candidate data in our Privacy Policy.