Engineering Work Worth Owning
Fastly runs on one documented engineering standard, not a different bar for different projects. This page explains how we work and how hiring will happen once roles open — read our About for the fuller picture of who we are.
Why Join Fastly
Engineering Excellence
One documented standard applied to every project — the same discipline this site itself was built under, not a different bar for internal work.
Learning
Working across AI, web, mobile, and enterprise systems means continuously learning — by necessity, not as a program bolted on top.
Innovation
AI is treated as a first-class part of the architecture, not a feature added after the fact — the kind of work that stays technically interesting.
Ownership
A shipped system stays your responsibility after launch. Engineers here own outcomes, not just tickets.
Long-Term Growth
Built as a long-lived engineering practice, not a project shop — the kind of place a career can compound in.
Engineering Principles
The same standard applied to client work is applied internally — see it in practice on our Engineering Blog.
Scalability
Every demonstration is built to handle more data, more usage, and more complexity without a rewrite at the next order of magnitude.
Security
Security is treated as an architectural constraint from the first decision, not a review pass added before launch.
Performance
Core Web Vitals and real-world responsiveness are requirements considered at the architecture stage, not tuned in afterward.
Accessibility
WCAG 2.2 AA is the floor for every demonstration, not a target aimed at eventually.
Maintainability
Every architecture is documented clearly enough that another engineer could pick it up without reverse-engineering it.
Standard
The Same Standard, Whoever Joins
As Fastly grows, whoever joins works to the same engineering standard documented on this site today — it isn't a set of values written down and set aside.
Future Opportunities
The categories we expect to hire across as the team grows. We're not actively hiring for all roles today — this is a preview, not a job board.
- Backend Engineering
- Frontend Engineering
- Mobile
- AI Engineering
- UI/UX Design
- DevOps
- QA
Hiring Process
The flow we'll follow once a role is open — illustrative, not a sign that we're actively interviewing right now.
- 01
Application
You share your background and what you want to work on.
Initial Review
- 02
Review
We review fit against open needs and prior work.
Technical Discussion
- 03
Technical Discussion
A real conversation about engineering problems, not a trivia quiz.
Project Discussion
- 04
Project Discussion
Walking through how you approach an actual problem, together.
Offer Consideration
- 05
Offer
If it is a mutual fit, we make an offer and discuss next steps.
Next Steps
Frequently Asked Questions
Is Fastly currently hiring?
Not for most roles today — Fastly is pre-launch. We're not actively hiring across the board, but we welcome expressions of interest for when hiring opens.
How can I express interest in future opportunities?
Reach out through Contact or WhatsApp with your background and what you'd want to work on — there is no application system yet, so a direct message is the right path.
What roles will Fastly hire for first?
Likely across the categories listed above — backend, frontend, mobile, AI engineering, design, DevOps, and QA — but timing depends on real project needs, not a fixed schedule.
Does Fastly hire remotely?
Our engagements are run remotely, and we expect hiring to follow the same model — though specifics will be confirmed once roles actually open.
What does the hiring process look like?
A straightforward flow once roles are open: application, review, a technical discussion, a project discussion, and an offer — detailed in the Hiring Process section above.
Interested in Working With Us?
There's no application system yet — reach out directly and we'll keep you in mind as roles open.