Who we are looking for

We hire for potential and for what you have built. The CV is the part nobody here looks at much: show us your work.

Having built something, and being able to show it. This is the one requirement we do not bend on, and it is the first thing we open. It does not have to be mobile, Flutter, or a published app: a website, a game, a bot, a script, a tool. It does not need to be big either. It needs to be yours and finished.
Genuine creativeness. You have made things nobody asked you for. A bot, a game, an app for your gym crew, a tool that solved a problem only you had. After the portfolio, that is the signal that counts most.
The language does not matter. Python, JavaScript, Java, C#, whatever. If you can build, Flutter and Dart take weeks and we will teach you here. Knowing Flutter or having shipped an app is a plus, but it is not a requirement, and not applying because you lack it would be the mistake.
Alignment with our values. This is the most important filter in the process, ahead of any technical skill. The technical side we can teach in months; how someone works, we cannot. Read how we work before you apply: we are going to ask you about it.
Student or recent graduate. Being at university does not count against you. If you graduated recently, you fit too. What matters is that you have real hours to give and that you are straight with us about them.
You want to be taught. This role is accelerated learning: you will get direct feedback, a lot of it, early. We want someone who reads that as the best part of the job, not the most uncomfortable.
LATAM preferred. We work remotely and a good part of the team is in LATAM: overlapping hours is what makes mentoring actually work. It is not a hard requirement, but it is a real preference.

The role

You will build real mobile product from your first week: screens, flows and fixes that ship to production and get used by millions of people. No pretend tasks, no watching other people work.

What separates this from a normal junior job is that the growth is written down. You get six months with a clear plan, someone on the team reviewing your code and explaining the why, and salary increases within those six months as you hit it. You are not waiting for somebody to remember you at the annual review.

In exchange we expect pace. The bar is the same one everyone else clears, and the only concession this role makes to you starting out is how long we give you to reach it.

Before you read on

A job spec takes ten minutes; who you do it with does not.

We are a small, remote team with a high bar and a real appetite for getting better. If that fits, the specific role matters less.

How we work at Symmetry

What you will do

Build screens and flows in Flutter, from the idea to the store, with a more senior review at every step.
Fix real production bugs: it is the fastest way to understand a large codebase, and it is where the learning actually happens.
Polish the detail. Animations, empty states, edge cases, how it behaves on a low-end phone. In a consumer app, that detail is the product.
Get inside the experiments. You will see how an A/B test is set up, what gets measured and what gets decided from the result.
Use AI as a default tool: Claude, Cursor and agents are part of how the team works. We will teach you to use them well, not to copy and paste.
Ask a lot of questions. It is literally part of the job for the first few months, and not asking is the one mistake that gets expensive here.

Six months of guaranteed growth

This is the part of the role we want to be unambiguous about, because it is what makes it not an internship:

A written six-month plan, with what is expected of you at each stage and how it is measured.
Salary increases within those six months, not at the end of them. Growth gets paid when it happens.
Real, named mentoring: someone on the team is accountable for you learning, with code reviews and standing sessions.
Direct, frequent feedback. You will always know where you stand; nobody here finds out about a problem six months late.
A clear path to Product Engineer. This role is the way into the engineering team, not a temporary contract.

Requirements

Required

0 to 2 years of experience. The role is genuinely junior and it is budgeted as one.
Something built, and reachable. We can open it without asking for permission, and it is finished. Any kind of thing, in any technology. Without this there is no application to assess; with it, even if it is not mobile, there is.
You can program, in any language. We are not asking for Flutter, Dart or mobile experience: that gets learned here, and teaching it is part of the mentoring.
Alignment with our values and how we work. Reading up on who we are before applying is part of the process, not a bonus.
Autonomy and ownership. Junior does not mean waiting for instructions: it means trying, getting it wrong early and saying so.
Direct communication. On a remote team, writing clearly and flagging a blocker fast is half the job.
English you can read. The docs and the code are in English; you do not need to speak it fluently.

What counts most

Flutter or Dart, even if only from a personal project. It is what speeds up ramp-up most, but you can learn it here.
An app of your own shipped to the App Store or Google Play, whatever the download count.
Native iOS or Android (Swift, Kotlin): understanding the platform underneath helps more than you would think.
Git on a shared project: branches, pull requests, resolving a conflict without fear.

Also counts

Open source contributions.
Using Symmetry, or any fitness app, seriously.
Hackathons, game jams, competitive programming.
Having taught someone else to code.

What success looks like here

In the first month: your first change in production, and the dev environment fully under control.
By three months: you take a whole screen end to end without anyone having to break it down for you.
By six months: you pick up product work with no detailed plan and ship it, with one or two salary increases already behind you.
The whole way through: you ask early, you repeat few mistakes, and feedback we give you once does not need giving twice.

This role is not for you if…

You have nothing built that you can show us. (Not knowing Flutter, or not having a published app, is NOT a reason: that is what we teach.)
You are applying without having looked at what Symmetry does: it shows in the first answer on the form.
You want a quiet internship to round out a CV.
Direct feedback does not sit well with you.
You have more than two years of experience and expect the pay to reflect it: that is one of our other roles.
You want to be told exactly what to write on every line.

Compensation and benefits

Salary paid in USD, with increases inside the first six months tied to the growth plan.
100% remote, no fixed hours and almost no meetings. LATAM preferred so your hours overlap with the team.
Compatible with studying. If you are at university we will work the load out with you; what we do not negotiate is what gets delivered.
Mentoring from the team that builds the app, not from an intern programme.
Real impact: what you write in your first week will be used by millions of people.

How to apply

Three questions. No cover letter, no 40-field forms.

Your portfolio. GitHub, your own site, a published app, a folder of videos of what you made. It does not have to be mobile or Flutter: anything, as long as it is yours, it is finished, and we can open it without asking you for access.
Something you made that nobody asked you to make. Not coursework: the thing you built because you wanted it to exist. What it is, where the idea came from and what you would do differently now.
What you found out about Symmetry. We read this one carefully, and it carries weight. Download the app, read how we work, look up what we are building and who is building it, and tell us what you found, what you liked and what you would change. An answer that could be sent to any company tells us everything we need to know.

That third question is not a formality: our culture is the thing we protect hardest, and we need people who are aligned with it.

The process

A review of your portfolio. Before the CV, and sometimes instead of it.
First conversation (20 min): who you are, what you have built and what you expect to learn.
A short technical test: one small, real task from the app. We are looking at how you reason and how you leave the code, not at perfection.
Final interview with the technical team: we go through your test together. Fast decision.

You leave every step knowing what happens next.

Junior Mobile Engineer