Ark Residential
Product Engineer

How your CV stacks up
Upload your CV to see how well it fits this job role
?%
Hey! We're Ark 👋
We make software for the places people live - specifically, managed buildings and the people on both sides of them.
Residents and leaseholders get an app: message the people who manage their building, pay their service charge, report maintenance issues and get to know their neighbours. Property managers and the on-site team get a web platform they run the building from: responding to resident queries, handling keys and packages, and staying on top of compliance. It's software with real stakes - when it works, someone's home runs a little more smoothly, and someone's job gets a lot less painful.
Every property management company in the UK is running on email, spreadsheets, and disconnected tools that were never built for the job. We’re replacing that. Ark is becoming the operating layer that property teams and residents can’t imagine working without - a unified platform for communication, compliance, maintenance, and payments.
We’re a small team with a huge impact. Thousands of people use Ark every day and we’re trusted by some of the largest companies in the sector, including the industry body. The companies that we work with manage c.400k homes and we are uniquely positioned to work in partnership with them and use AI to shape the future of property management. We’re growing with purpose and looking to build something meaningful with lasting impact.
How we work
- Engineers own product. Whoever is leading the problem does all of it - you’ll sit on customer calls, work out what’s worth building, designing, shipping and checking whether it made a difference. If it didn’t, that’s yours to fix too. You own the problem. Worth knowing that a decent chunk of your week won't be spent writing code.
- We're in the office together, 4–5 days a week. This is a deliberate choice. We find our best work is done in person: it allows us to shorten feedback loops, decide quickly and brainstorm together.
- You’ll drive your own growth, and we’ll back it. We'll give you real problems with real consequences and point you in the right direction, but the people who do best here go and get good at things rather than wait to get taught.
Reasons to use Rodeo
I’m in my final year doing Economics and I don’t know whether to apply for grad schemes now or do a masters first. What do you think?
Honest answer — it depends on where you want to end up. A lot of top grad schemes (Big 4, civil service, banking) don’t need a masters. Let’s look at the ones you’d be competitive for now, and we can decide if a masters actually adds anything.
Also worth knowing: most autumn 2026 applications are open now. Timing matters more than you think.
Start with a chat, not a search bar
Grad scheme, placement, apprenticeship? Not sure what you want yet — that's fine. Your agent talks it through with you and turns "I have no idea" into a shortlist.
Graduate Consultant — 2026 Scheme
Why you're a good match
StrongYour economics background and your summer at a regional bank line up with what PwC looks for on the consulting scheme. Applications close in four weeks.
See breakdownIt searches the market for you
Every day your agent scans the market matching roles against what actually matters to you, not just keywords on a CV.
Why you're a good match
You’ve got the grades and the economics background, and your bank internship is exactly the experience this scheme looks for. Apply soon — deadlines close within the month.
Experience fit
Your summer at the bank plus your econometrics coursework map directly to the day-one responsibilities on this scheme — client modelling, market briefings, and deal support.
Only hits
No noise. No "maybe this fits." Just roles with a clear explanation of why they're right — and where to focus when applying.
What You’ll Do
- Take problems from unclear to shipped. Discover, architect, build, test and deliver new features across the entire stack.
- Build with users, not just for them. Property managers and residents give us direct, sometimes blunt feedback. You'll be close enough to hear it first-hand and turn it into product the same week.
- Use AI to do the previously-impossible. Turning messy inspection reports into clear action plans, making sense of resident messages, drafting replies a manager can actually trust - the kind of thing that wasn't buildable a couple of years ago.
- Have a real say in what gets built. Your product instincts matter as much as your code. If you think we're building the wrong thing, we want to hear it.
- Share your expertise and experience. Be on hand to help other team members (technical or otherwise!) and help mentor other engineers at Ark.
- Help us operate more efficiently by building, maintaining our developer tooling, CI & CD pipelines and being at the forefront of the latest and greatest AI tools.
Who does well here
We care less about your exact CV than about how you work. The people who thrive at Ark tend to:
- Have a strong bias to action. You spot what's missing and go and do something about it, rather than waiting to be asked.
- Have good product instincts. You have taste for what to build and the discipline to leave the rest out.
- Be comfortable with ambiguity. You can make real progress without a clear spec, and you're happy changing course when the problem turns out to be different than you thought.
- Be kind and low-ego. You're collaborative and pragmatic, you'd rather get it right than be right, and you're easy to build alongside.


Get help with your application
Your very own career expert that helps elevate your application to the next level.
On the engineering side, you'll probably recognise yourself in most of this:
- You've owned and shipped real features across frontend and backend, and you enjoy the whole stack rather than a slice of it.
- You're strong with TypeScript and React, and/or with Python and a modern web framework - and happy to become strong in the other.
- You can make the bigger architectural calls and have them still look right in six months.
- You already build with AI tools and have a genuine view on where they help and where they get in the way.
Bonus, not essential: React Native, AWS, GraphQL, CI/CD, or having shipped LLM features to production. None of this is a checklist - if it sounds like you, even without every box ticked, get in touch.
Why now
This is a chance to build the infrastructure for the most fragmented and most painfully manual industry there is. Ark is at the point where a small, sharp team can shape both the product and the way we build it, right as we step up to a bigger market. You'd join early enough to leave real impact on both, with a genuine path into technical leadership for the right person.
How the process works
- Apply with your CV.
- Intro call (30 mins) with one of the engineering team.
- Take-home task (max 2 hours) - or send us something you've built recently instead.
- Technical interview (1 hour) - half spent on your take-home (or what you sent across), half on a systems design question.
- A half-day working with us in the office - real work, alongside the team. Paid, of course.
- Culture fit - a final conversation with our founder.
We'll always aim to get back to you quickly between stages.
“It took my CV and asked me questions relevant to understanding what kind of jobs to suggest for me. Suggestions were almost perfect. Jobs were exactly what I’ve been looking for.”
Jessica, London
Location