OXARUS :: CAREERS
Careers: Open roles at Oxarus
Open roles across Hub, Studio, Quant and Agent AI, and how hiring works. On-site and hybrid roles in Ankara or Istanbul; remote roles from anywhere.
- page
- unit
Oxarus
- path
- markdown
Interface data marked as representative is illustrative; it is not a real client, result or measurement.
OPEN ROLES
CAREERS
We're hiring across Hub, Studio, Quant and Agent AI. On-site and hybrid roles are based in Ankara or Istanbul; remote roles have no city requirement.
- locations
Offices
REPRESENTATIVE INTERFACE DATA
oxarus / workspace
- review
Code review
- design
Design review
- release
Release
- lanes
Units
- hub
Order sync
- studio
Pals attendance
- quant
L.I.T. news feed
- agent
Invoice agent evaluation
- online
Online
feat(sync): incremental order cursor
-
0
- author
Burak Ş.
- text
On the first sync store.cursor is null, so since isn't sent and the API returns only the last 50 orders. Older orders never arrive.
-
1
- author
Deniz A.
- text
You're right, I missed that. With no cursor it now falls back to a full sync, and there's a test for it.
- approve
Burak approved
- lint
- typecheck
- test
Pals / Attendance screen
- status
Resolved
- before
Before
After
-
0
- author
Elif K.
- text
Brought the row height down from 56 to 48. You now see 13 students on screen instead of 11.
-
1
- author
Mert A.
- text
True, but the “Absent” button shrank too. I tapped the student below twice on my phone. Keep rows at 48 and make the button 44?
-
2
- author
Elif K.
- text
OK, the button is 44 now. Also, a class with no students showed a blank screen, so I added a short line there.
- decision
Decision: rows 48, button 44. The empty-class text goes out in this week's release.
L.I.T. / news feed service
- badge
Live
-
#219 merged to main
-
Ran overnight on staging, no missed headlines
-
Rollback command tried on staging
-
Deployed to production
-
Watching latency and error rate
- chart
p95 latency · last hour
- deploy
release
- status
185 ms before the release, 180 ms now. No new errors logged.
- pause
Pause autoplay
- play
Start autoplay
- review
Code
- design
Design
- release
Release
Offices
- Ankara
Engineering & R&D
- Istanbul
Operations & Architecture
ALL ROLES
ROLES
Filter by unit, city or work model. To apply, upload your CV as a PDF.
- role column
Role
-
Senior Frontend Engineer
Build fast, accessible corporate websites, AI search interfaces and e-commerce storefronts.
- Unit
Hub
- City
Ankara
- Work model
Hybrid
- Level
Senior
The application form asks for your name, email and CV as a PDF (up to 4 MB).
-
Backend Engineer
Write and run the APIs, integrations and order flows behind client systems.
- Unit
Hub
- City
Istanbul
- Work model
Hybrid
- Level
Mid-level
The application form asks for your name, email and CV as a PDF (up to 4 MB).
-
Mobile Engineer (React Native)
Build Pals and client apps for iOS and Android, including offline use.
- Unit
Studio
- City
Anywhere
- Work model
Remote
- Level
Mid-level
The application form asks for your name, email and CV as a PDF (up to 4 MB).
-
Product Designer
Design screen flows for Pals and client apps, from research to prototype.
- Unit
Studio
- City
Istanbul
- Work model
Hybrid
- Level
Senior
The application form asks for your name, email and CV as a PDF (up to 4 MB).
-
Quant Developer (MQL5 / Python)
Build the research tools behind the L.I.T. terminal and custom MT5 robots for clients.
- Unit
Quant
- City
Istanbul
- Work model
On-site
- Level
Senior
The application form asks for your name, email and CV as a PDF (up to 4 MB).
-
Data Engineer
Build the market data pipelines behind Quant research and keep the data queryable.
- Unit
Quant
- City
Ankara
- Work model
Hybrid
- Level
Mid-level
The application form asks for your name, email and CV as a PDF (up to 4 MB).
-
AI Agent Engineer
Build agents that handle documents, invoices and support work for Agent AI clients, with human approval.
- Unit
Agent AI
- City
Anywhere
- Work model
Remote
- Level
Senior
The application form asks for your name, email and CV as a PDF (up to 4 MB).
-
Engineering Internship
Work with a mentor at our Istanbul office on changes that ship to production.
- Unit
Oxarus
- City
Istanbul
- Work model
On-site
- Level
Intern
The application form asks for your name, email and CV as a PDF (up to 4 MB).
FROM APPLICATION TO OFFER
HIRING PROCESS
Five steps, and we tell you up front what we expect at each one.
Timings are estimates and may vary with the role's scope and scheduling. Whatever the outcome, we reply in writing at the end of every step.
-
Application
Upload your CV as a PDF through the application form and add links to code or design work if you have them. HR and the relevant team review your application together.
A short note: why this role, and which piece of work you owned the most.
HR and the role's team review your application together, and we reply in writing.
Sample candidate journey
- Form: PDF CV and GitHub link sent
- HR and the Hub team reviewed the application together
- Times proposed for an intro call
-
Intro call
A video call with someone from the team. We talk through the role, the team and how we work, and leave time for your questions.
Being open about your expectations and your preferred work model.
We explain the role's actual scope, the team and the next steps.
Sample candidate journey
- Video call invite accepted
- Role scope and work model discussed
- Candidate chose the take-home as the technical format
-
Technical exercise
We offer two options: a scoped take-home you do on your own time, or a live pairing session with someone from the team.
Choosing the format you prefer and explaining your decisions.
We keep the scope clear and state the expected time for the take-home up front.
Sample candidate journey
- Take-home scope and expected time shared in writing
- Candidate submitted the solution with a short decision note
- Two engineers reviewed the solution
-
Team interview
We go through your technical exercise with the team you'd join and talk through how real work moves forward.
Discussing the trade-offs and alternatives in your work.
We show you the team's day-to-day work and how review and release run.
Sample candidate journey
- Trade-offs in the take-home discussed
- Team walked through its review and release routine
- Team shared its feedback in writing
-
Offer
Once we've decided, we send the offer in writing and agree on the role, work model and start date together.
Sharing your questions and your preferred start date.
We set out every part of the offer clearly and in writing.
Sample candidate journey
- Offer sent with role, work model and start date
- Candidate's questions answered
- Start date agreed together
- Sample candidate journey
Backend Engineer application
FOR EVERYONE ON THE TEAM
WORKING CONDITIONS
Whatever the unit, city or work model.
-
Live products
You work on Pals, L.I.T. and client projects that are live.
-
Equipment
The company provides a computer, a monitor and the test devices your role needs.
-
Time to learn
Reading and trying out a new tool count as working time.
-
Flexible hours
The work model depends on the role; outside the team's shared hours, you set your own schedule.
-
Pairing
You work on the same tasks as senior teammates and review each other's work.
-
Written scope
The role's scope and how it is evaluated are shared in writing before you start.
REPRESENTATIVE INTERFACE DATA
- clientWork
Client projects
- workTime
Working hours
- Project work
- Code review
- Reading and trying
- coreHours
Shared hours
Role scope
- Area of ownership
- Evaluation criteria
- Work model
- Start date
- Computer
- Monitor
- Test devices
DON'T SEE YOUR ROLE LISTED?
OPEN APPLICATION
Share your CV and what you'd like to work on. HR and the relevant team review it together, and we'll contact you when a matching role opens.
ACTIONS
DOCUMENTS
- markdown
- jsonld
- llms.txt
- agents.md
Every page is also served as Markdown: add .md to the address or request it with Accept: text/markdown.