life at elva

What it's actually like here

01 · who

Who we are and where to find us

Elva is an AWS consultancy. We help companies build new things on AWS and fix the things they already built, with a focus on serverless and cloud-native architecture. Elva Stockholm is [n] engineers, working with [types of clients]. If you explained us to a friend: we're the people a team calls when they want their AWS setup to be boring in the good way.

Address: [Stockholm address]
Getting there: [nearest station]
Map: [map link]

02 · what we build

What we build

case 01 · [n] engineers · [n] months

[Project story 1: short title]

The problem: [The client's problem, in one or two sentences]
What we built: [The AWS approach: what we built and why]
What happened: [The result, with a number if there is one]

[AWS services]

case 02 · [n] engineers · [n] months

[Project story 2: short title]

The problem: [The client's problem]
What we built: [The AWS approach]
What happened: [The result]

[AWS services]

case 03 · [n] engineers · [n] months

[Project story 3: short title]

The problem: [The client's problem]
What we built: [The AWS approach]
What happened: [The result]

[AWS services]

03 · people

The people

[name]

[role]

[what they work on, and what they like about it]

[name]

[role]

[what they work on, and what they like about it]

[name]

[role]

[what they work on, and what they like about it]

04 · how we work

How we work

Hours: [hours and flexibility]
Office and remote: [hybrid / on-site policy]
Staffing: [how projects are staffed: alone, in pairs, in teams]
Client contact: [a daily part of the job / weekly / depends on project]
Decisions: [draft: The people doing the work make the technical calls. Bigger ones get written down and argued about kindly.]

The rhythm

[draft: Office day, everyone in][draft: weekly]
[draft: Demo: show what you built, broken bits included][draft: monthly]
[draft: Learning afternoon][draft: every other week]
[draft: Company trip][draft: yearly]

05 · honestly

Consulting, honestly

Consulting has trade-offs. People who leave it usually leave for the same few reasons, so here they are up front.

Typical assignment: [draft: Three to twelve months with one client, often part-time alongside a second.]
Utilisation target: [utilisation target]
Between assignments: [draft: Internal work, certifications and helping on sales scoping. Nobody sits on a bench refreshing their inbox.]
Travel: [draft: Mostly Stockholm. Occasional client visits elsewhere, agreed with you in advance.]
Saying no to a client: [draft: Yes. If an assignment is a bad fit for you, say so before it starts. We'd rather lose a deal than an engineer.]

Who this is not for

[draft: You want to work on one product for five years.]
[draft: You'd rather not talk to clients, ever.]
[draft: You need every requirement written down before you start.]

Things you might not love

[draft: Context switching. New client, new codebase, new acronyms, every few months.]
[draft: Sometimes the best architecture loses to the client's deadline or budget.]
[draft: We're small, so some things are still being figured out. Like this page.]

06 · grow

How we grow

Career ladder: Three levels, written down, v1. See Growing here.
Learning budget: [learning budget per year]
Certifications: [exam fees paid, study time per month]
Internal sessions: [how often, what format]
Conferences: [conferences per year, budget]

Read the career ladder →

07 · perks

Perks

Vacation: [vacation days beyond statutory]
Pension: [pension details]
Insurance: [insurance details]
Laptop and setup: [laptop, setup budget]
[other perks]: [details]
Learning budget: [learning budget per year]

Pay bands for every level are on the pay page.

08 · values

Values, in behaviour

The best idea in the room wins.[a real time a newer or more junior person's idea beat the senior one]
No managers, no politics.[how a real decision got made without a manager: who decided, and how]
We care more about our clients' business than about our contracts.[a real time we advised a client to do less, or something cheaper, than they asked for]

09 · hiring

How we hire

Three conversations: a 30-minute intro, a 60-minute technical chat about a small AWS architecture, and a final conversation with [name or role]. We reply within [5] working days at every step.

The full process and FAQ →

10 · apply

Apply

Write to [contact name]

[contact role]. [draft: A real person reads every email.] We reply within [5] working days.

Email [contact name]

or copy: stockholm.hiring@elva-group.com