Blitzy Jobs Hiring Now
Blitzy is hiring for 14 open roles on Migrate Mate as of July 16, 2026, concentrated in AI (Artificial Intelligence) and account management, with listed salaries up to about $500,000. Migrate Mate updates Blitzy's live openings daily. Blitzy is an AI-powered software development platform that helps engineering teams build and ship code faster through automated workflows and intelligent developer tooling.
Find Blitzy JobsOverview
Blitzy hiring data on Migrate Mate, as of July 16, 2026.
- Open jobs
- 14
- Top team
- AI (Artificial Intelligence)
- Seniority
- Mid to senior level
- Work type
- 14% remote or hybrid
- Top location
- Cambridge
- Salary range
- $2,000–$500,000
Listed salaries for Blitzy roles on Migrate Mate range from about $2,000 to $500,000 per year across 14 open roles, as of July 16, 2026.
Open Roles at Blitzy
Showing 14 of 14+ Blitzy jobs
About Blitzy
Blitzy is a Cambridge, MA based AI software development platform on a mission to revolutionize the software development life cycle by autonomously building custom software to unlock the next industrial revolution. We're transforming how enterprises build software, turning enterprise requirements into production-ready code with an agentic software development platform that can autonomously execute 80% of the quantum of software development work. We're backed by multiple tier 1 investors, and have proven success as founders of previous start-ups.
Location: Cambridge, MA (On-site)
Compensation: $100,000 - $140,000 salary + equity
The Role
The role is to support our clients and ensure a stable environment across the full lifecycle: installation, ongoing upgrades, and day-to-day operation. The L2 Support Engineer works alongside L1 to triage and resolve issues, and escalates unresolved defects to engineering. It operates across Kubernetes, Docker, and the major cloud providers.
What Success Looks Like
Customers' issues are resolved faster and escalated cleaner.
Recurring problems turn into runbooks, dashboards, and alerts, not repeat tickets.
Engineering trusts your escalations because they come with proof, not guesses.
Customers trust your communication because it's clear, honest, and on time.
Areas of Ownership
Deploy and install the platform into customer environments, and troubleshoot installation issues.
Support ongoing upgrades and day-to-day operation, keeping customer environments stable.
Work alongside L1 to triage and resolve customer-reported issues, driving them to resolution or escalation.
Diagnose failures across the stack: compute, networking, storage, and the services running on it.
Reproduce issues safely against live (often multi-tenant) environments using read-only diagnostics first.
Build and maintain dashboards, monitors, and runbooks so recurring issues get faster to fix: or stop recurring.
Write up clear, evidence-backed escalations and post-incident notes.
Communicate status and resolution to customers clearly and on time.
Required Experience
Distributed-systems debugging. Reason about a request crossing multiple services, queues, and network hops, and isolate which hop failed. You debug by forming a hypothesis and confirming it with evidence (logs, pod state, queue depth, DB rows), not by guessing.
Kubernetes & Docker.
Major cloud providers: GCP, AWS, and Azure. Hands-on with at least one deeply and able to work across the others: managed Kubernetes (GKE/AKS), cloud logging, IAM/auth basics, and cloud disk/storage behavior.
Strong monitoring & observability practice. Fluent with an APM/observability stack (Datadog or equivalent): log queries, correlating across services by request/trace IDs, reading traces, and building dashboards and alerts. You reach for the data before theorizing.
Additional Skills & Experience
Python and Redis literacy.
Basic message queueing. Command transport runs over a message queue (Redis/rq). Comfort inspecting queue depth, backlogs, and stuck/failed jobs; concepts transfer from any broker.
Networking & WebSockets. Many of our hardest issues are connection problems: WebSocket/Socket.IO drops, NAT/idle/LB timeouts, half-open sockets, DNS-vs-routing, TLS. Tell a transport fault from an application fault.
SQL / PostgreSQL. Query operational tables to confirm what the system recorded.
Source-control platforms. GitHub (incl. GitHub Enterprise Server), Azure DevOps, and/or GitLab, clone/push/pull, access tokens, app credentials, and their failure modes.
CI/CD, Helm & deploy integrity. Many "sudden regressions" are a bad or partial deploy: check what version is actually running before chasing architecture theories. Helm and container deploy pipelines expected. ArgoCD is a plus.
Secrets management. Comfort handling secrets, credentials, and certificates safely, ideally with Vault (strongly preferred).
Linux and Windows. Workloads run on both; comfort triaging on each OS (process inspection, filesystem, basic networking).
Methodical, evidence-first temperament. Hold several candidate causes at once, run the cheapest disconfirming check first, and never claim a root cause or fix you haven't proven.
Multi-tenant safety mindset. Environments are shared and customer-owned: default to read-only diagnostics and understand blast radius before changing anything.
Incident management & ticketing workflows: Jira or similar (a plus).
Prior customer-facing support or SRE/on-call experience (a plus).
Hours & On-Call: please read
This is a customer support role, and the hours can be unconventional. Customers operate primarily in US time zones, so coverage is anchored to US business hours (roughly ET–PT). If you're based outside the US, expect your working day to shift accordingly.
Incidents don't keep office hours. Expect a rotating on-call schedule and occasional evening, early-morning, or weekend escalations outside a standard 9–5. We structure for it: rotations are shared fairly, on-call is compensated/time-off-in-lieu per policy, and we protect recovery time after heavy incidents.
If you're not comfortable with US-aligned hours and periodic off-hours on-call, this likely isn't the right role, and that's completely fine.
Our Culture
Who we are:
Led by two pioneering co-founders we are one of the fastest growing companies in the U.S., creating our own category of enterprise autonomous software development. We automate thousands of hours of software development for our customers, which includes strong representation within the Fortune 500.
How we work:
We move Blitzy Fast: Time is both our company's and our clients' most precious asset. We move quickly and decisively to innovate internally and deliver exceptional software externally.
Championship Mindset: We operate like a professional sports team. We win as a team by holding ourselves and each other to high standards, collaborating in-person, and remaining focused on the mission.
Passion for Invention: We're pushing the frontier of what's possible, requiring constant innovation and iteration.
We Work for the Customer: We focus on delivering outsized value to the customers we work with and expanding those relationships into deep, meaningful partnerships.
We believe in being 'everyday athletes'—taking care of ourselves so we can bring our best minds to work. We promote great sleep, movement, and restorative activities for optimal mental performance. It makes for a happier and more productive team.
Blitzy is an equal opportunity employer committed to building a diverse and inclusive team. We believe different perspectives make us stronger.
About Blitzy
Blitzy is a Cambridge, MA based AI software development platform on a mission to revolutionize the software development life cycle by autonomously building custom software to unlock the next industrial revolution. We're transforming how enterprises build software, turning enterprise requirements into production-ready code with an agentic software development platform that can autonomously execute 80% of the quantum of software development work. We're backed by multiple tier 1 investors, and have proven success as founders of previous start-ups.
Location: Cambridge, MA (On-site)
Compensation: $100,000 - $140,000 salary + equity
The Role
The role is to support our clients and ensure a stable environment across the full lifecycle: installation, ongoing upgrades, and day-to-day operation. The L2 Support Engineer works alongside L1 to triage and resolve issues, and escalates unresolved defects to engineering. It operates across Kubernetes, Docker, and the major cloud providers.
What Success Looks Like
Customers' issues are resolved faster and escalated cleaner.
Recurring problems turn into runbooks, dashboards, and alerts, not repeat tickets.
Engineering trusts your escalations because they come with proof, not guesses.
Customers trust your communication because it's clear, honest, and on time.
Areas of Ownership
Deploy and install the platform into customer environments, and troubleshoot installation issues.
Support ongoing upgrades and day-to-day operation, keeping customer environments stable.
Work alongside L1 to triage and resolve customer-reported issues, driving them to resolution or escalation.
Diagnose failures across the stack: compute, networking, storage, and the services running on it.
Reproduce issues safely against live (often multi-tenant) environments using read-only diagnostics first.
Build and maintain dashboards, monitors, and runbooks so recurring issues get faster to fix: or stop recurring.
Write up clear, evidence-backed escalations and post-incident notes.
Communicate status and resolution to customers clearly and on time.
Required Experience
Distributed-systems debugging. Reason about a request crossing multiple services, queues, and network hops, and isolate which hop failed. You debug by forming a hypothesis and confirming it with evidence (logs, pod state, queue depth, DB rows), not by guessing.
Kubernetes & Docker.
Major cloud providers: GCP, AWS, and Azure. Hands-on with at least one deeply and able to work across the others: managed Kubernetes (GKE/AKS), cloud logging, IAM/auth basics, and cloud disk/storage behavior.
Strong monitoring & observability practice. Fluent with an APM/observability stack (Datadog or equivalent): log queries, correlating across services by request/trace IDs, reading traces, and building dashboards and alerts. You reach for the data before theorizing.
Additional Skills & Experience
Python and Redis literacy.
Basic message queueing. Command transport runs over a message queue (Redis/rq). Comfort inspecting queue depth, backlogs, and stuck/failed jobs; concepts transfer from any broker.
Networking & WebSockets. Many of our hardest issues are connection problems: WebSocket/Socket.IO drops, NAT/idle/LB timeouts, half-open sockets, DNS-vs-routing, TLS. Tell a transport fault from an application fault.
SQL / PostgreSQL. Query operational tables to confirm what the system recorded.
Source-control platforms. GitHub (incl. GitHub Enterprise Server), Azure DevOps, and/or GitLab, clone/push/pull, access tokens, app credentials, and their failure modes.
CI/CD, Helm & deploy integrity. Many "sudden regressions" are a bad or partial deploy: check what version is actually running before chasing architecture theories. Helm and container deploy pipelines expected. ArgoCD is a plus.
Secrets management. Comfort handling secrets, credentials, and certificates safely, ideally with Vault (strongly preferred).
Linux and Windows. Workloads run on both; comfort triaging on each OS (process inspection, filesystem, basic networking).
Methodical, evidence-first temperament. Hold several candidate causes at once, run the cheapest disconfirming check first, and never claim a root cause or fix you haven't proven.
Multi-tenant safety mindset. Environments are shared and customer-owned: default to read-only diagnostics and understand blast radius before changing anything.
Incident management & ticketing workflows: Jira or similar (a plus).
Prior customer-facing support or SRE/on-call experience (a plus).
Hours & On-Call: please read
This is a customer support role, and the hours can be unconventional. Customers operate primarily in US time zones, so coverage is anchored to US business hours (roughly ET–PT). If you're based outside the US, expect your working day to shift accordingly.
Incidents don't keep office hours. Expect a rotating on-call schedule and occasional evening, early-morning, or weekend escalations outside a standard 9–5. We structure for it: rotations are shared fairly, on-call is compensated/time-off-in-lieu per policy, and we protect recovery time after heavy incidents.
If you're not comfortable with US-aligned hours and periodic off-hours on-call, this likely isn't the right role, and that's completely fine.
Our Culture
Who we are:
Led by two pioneering co-founders we are one of the fastest growing companies in the U.S., creating our own category of enterprise autonomous software development. We automate thousands of hours of software development for our customers, which includes strong representation within the Fortune 500.
How we work:
We move Blitzy Fast: Time is both our company's and our clients' most precious asset. We move quickly and decisively to innovate internally and deliver exceptional software externally.
Championship Mindset: We operate like a professional sports team. We win as a team by holding ourselves and each other to high standards, collaborating in-person, and remaining focused on the mission.
Passion for Invention: We're pushing the frontier of what's possible, requiring constant innovation and iteration.
We Work for the Customer: We focus on delivering outsized value to the customers we work with and expanding those relationships into deep, meaningful partnerships.
We believe in being 'everyday athletes'—taking care of ourselves so we can bring our best minds to work. We promote great sleep, movement, and restorative activities for optimal mental performance. It makes for a happier and more productive team.
Blitzy is an equal opportunity employer committed to building a diverse and inclusive team. We believe different perspectives make us stronger.
Job Roles at Blitzy
Working at Blitzy
Blitzy's 14 open roles are mid to senior level, and about 14% are remote or hybrid. The most active teams are AI (Artificial Intelligence), account management, and accounting. Blitzy builds AI-driven software development tools designed to accelerate how engineering teams write, review, and deploy code. The company serves clients navigating digital transformation, with roles spanning software engineering, site reliability, client solutions, and enterprise sales. Most Blitzy roles are based in Cambridge.
Explore more roles by function
Browse thousands of live openings across engineering, sales, product, and more, and apply in just a few clicks.
Browse jobs by roleBlitzy Jobs: Frequently Asked Questions
How many jobs is Blitzy hiring for right now?
Blitzy is hiring for 14 open roles on Migrate Mate as of July 16, 2026, updated daily, concentrated in AI (Artificial Intelligence) and account management. Open positions include software engineering, site reliability, account management, and enterprise sales, covering both technical and go-to-market functions.
What kinds of roles does Blitzy hire for?
The most active teams are AI (Artificial Intelligence), account management, and accounting. Blitzy hires across software engineering disciplines, including backend, frontend, site reliability, and principal engineering, as well as forward deployed and automation engineering. On the business side, the company posts account executive, account manager, and managing director roles. Most postings are mid to senior level.
Are Blitzy jobs remote or in-person?
Mostly on-site. About 14% of Blitzy's open roles on Migrate Mate are remote or hybrid as of July 16, 2026, with the rest based in Cambridge. Each Blitzy listing shows its work location so you can filter before applying.
How do I apply to a job at Blitzy?
Find a Blitzy role on Migrate Mate, then follow the listing through to Blitzy's own careers page to submit your application. Blitzy manages its own hiring process, including any interviews and assessments. Migrate Mate keeps Blitzy's listings current so you can check back for new openings as they are posted.
What do Blitzy jobs pay?
Listed salaries for Blitzy roles on Migrate Mate range from about $2,000 to $500,000 per year as of July 16, 2026, with most postings at mid to senior level. Exact pay is set by Blitzy and shown on each listing.
Does Blitzy hire entry-level?
Most of Blitzy's open roles on Migrate Mate are mid to senior level as of July 16, 2026. Entry-level openings are limited. Check individual Blitzy listings for stated experience requirements.
Where is Blitzy hiring?
Most Blitzy roles are based in Cambridge, and about 14% offer remote or hybrid work as of July 16, 2026. Migrate Mate shows the location on each listing.