Important Note: These jobs are posted in real-time and might expire. Please apply promptly.
The job market for AI professionals is buzzing with opportunities this week. There’s a critical need for skilled architects, and remote work options are looking strong. It’s a good time to explore both traditional and flexible roles.
This Week’s Jobs
Principal Architect - AI
Company: Boston Consulting Group (BCG Platinion) | Location: Denver, CO
If you’ve got the knack for designing AI platforms at scale, this role is calling your name. BCG is looking for someone ready to tackle complex challenges and drive innovation. Apply Here
Principal Architect - AI
Company: Boston Consulting Group (BCG Platinion) | Location: Denver, CO
Another chance to join BCG as a Principal Architect focusing on AI. If you’re passionate about enhancing AI capabilities in a consulting setting, this could be your next move. Apply Here
Principal Architect - AI
Company: Boston Consulting Group (BCG Platinion) | Location: Denver, CO
Here’s yet another opportunity with BCG, focusing on large-scale AI platform architecture. Ideal for those ready to lead transformative projects. Apply Here
Work From Anywhere (100% Verified)
Remote work is thriving, and there are some exciting roles that offer flexibility.
AI Data Engineers
Company: Projekt 253 | Location: New York, NY
Dive into the infrastructure that could define the future of AI. This role is perfect for data engineers ready to make a significant impact. Apply Here
Remote Generative AI Engineer
Company: Scopic | Location: All Cities
Join Scopic in harnessing Generative AI to create cutting-edge applications. Work closely with engineering teams to bring AI solutions to life. Apply Here
But i’ve had the best luck applying within 24 hours and attaching a one-page diagram of how I’d scale inference and guardrails for their stack — recruiters reference it (kind of like speed dating for resumes). If attachments get stripped, I paste a short ‘architecture blurb’ in the cover letter with concrete SLOs and cost bounds. Remote or not, that specificity beats generic bullets.
Quick example: for Principal Architect postings, I send a 90‑second Loom walking through a vLLM + Ray Serve on EKS design with HPA and a rough $/token calc; because these are ‘real-time’ postings, it tends to get a same‑day response. If links are frowned on, I swap in a tiny Terraform gist instead.
Since these are ‘real-time’ postings, I apply within 6–8 hours and attach a one-pager with a minimal KServe + Triton rollout and a 15-min GPU cost table (L4 vs A10 spot) tied to their traffic; it’s gotten me same-day screens twice. Caveat: if the JD leans AWS, I swap to a SageMaker endpoint plan and drop this so they know I’ll use their tooling: Amazon SageMaker Inference Recommender - Amazon SageMaker AI.
‘Apply promptly’ is right, but for Principal Architect roles I get more callbacks when I attach a 1-page ADR with clear p95 latency/SLOs and a phased rollout for distributed teams. Small caveat: some orgs block Loom, so a plain-text ADR plus a link to an ADR template like https://adr.github.io/ has worked better.