Careers
Build a software career working with US clients from Latin America
Siblings Software is a US-based software outsourcing company headquartered in Miami, Florida, with engineering teams running out of Latin America since 2014. We hire senior engineers, QA automation specialists, and security professionals to ship long-running projects for clients in the US, Canada, and Europe across fintech, healthcare, eCommerce, logistics, and SaaS.
This is a working career page, not a recruiter pitch. If you are a developer who wants to write reviewed pull requests on a two-week cadence, sit in a small squad with senior peers, and own real product code that ships to paying users, this is a real fit. If you want a 200-person platform org, free meals, or a stack-rank ladder, this is not the right shop.
Written and reviewed by Javier Uanini, founder and CEO of Siblings Software, with input from the recruiting team. Updated 14 May 2026.
By the numbers, honestly
Most career pages dodge the actual operating numbers. Here are ours, with caveats where caveats belong.
10+
YEARS
Operating since 2014 out of Miami, with engineering teams across LATAM the whole time.
250+
CLIENT ENGAGEMENTS
Across fintech, healthcare, eCommerce, logistics, travel, payments, and B2B SaaS. About 40 percent venture-backed.
3–8
ENGINEERS PER SQUAD
Including the client's own engineers. Small enough that a standup fits in fifteen minutes.
6–24+
MONTHS PER ENGAGEMENT
Most squads sit on the same client for one to three years. A few have been on the same product longer than that.
6–8 h
EST OVERLAP TYPICAL
From Mexico, Colombia, Peru, and most of Central America. Argentina, Uruguay, and Chile shift the local day a couple of hours later.
1–2 wk
TYPICAL CV-TO-OFFER
CV review in three to five business days, then one or two interviews. We tell you which round is the decision round.
These are operational ranges drawn from how the company actually runs, not audited statistics. The first two are published facts about Siblings Software. The rest are typical of recent engagements and can move on a specific role; the interview is where we give you the number that actually applies to you.
Hiring snapshot — what we are staffing against in mid-2026
The mix shifts with the client roadmap, but the shape has been steady since 2024. This is what a real screening week looks like right now.
ROLE-FAMILY MIX, MID-2026
What recruiting is screening for this quarter
- Backend ~40%. Senior Go and Java with Spring lead the active roster, with Node.js and Python (Django, FastAPI) covering the SaaS surfaces. Most seats require Postgres at meaningful row counts and at least one queue or stream technology in production.
- Front-end ~25%. React and Next.js carry the modern stack; Angular sits behind two long-running engagements that are not migrating. TypeScript is assumed on every seat, not a bonus.
- Mobile ~15%. React Native and Flutter for cross-platform work; native Swift and Kotlin for the surfaces where BLE, AR, or background processing earn the native cost. iOS+Android only — we do not staff Windows mobile.
- DevOps and SRE ~10%. AWS-heavy with Azure on a third of the engagements. Terraform, Kubernetes, GitHub Actions, OpenTelemetry are the table-stakes stack; we screen for production on-call experience, not certificates.
- QA automation and security ~10%. One QA automation engineer per long-running squad, plus a small bench of penetration testers who rotate across short engagements.
Distribution is roughly steady but lumpy week to week: a single new dedicated team can spike one row 10–15 points in a month.
WHAT WE SCREEN FOR IN 2026
The signals that move a CV from review to interview
- Real PR review history. A link to a public repo where you have given non-trivial review on someone else's pull request — not just merged your own — weighs more than another certification.
- One decision you owned and would defend in writing. An ADR, a postmortem you wrote, a design note that made the call between two options. We will ask about it in the first interview.
- Judgment with AI tooling, not raw output. We assume Cursor, Claude Code, or Copilot are in your loop. The screen is whether you reject a model's diff when the trade-off is wrong, and whether you write the test that proves it.
- Production on-call experience. If you have been paged at 3am on a system you wrote, you understand observability differently. That experience is worth more than a Kubernetes certificate.
- One stack we can put you on the bench against. Generalists get hired; we just need to know which engagement to slot you into next quarter, so a clear primary stack helps.
CVs that read like template lists of every framework you have ever touched get a polite no. CVs with two stacks and a story behind each one make the interview shortlist.
If your stack does not appear in the role-family mix this quarter and you still want to talk to us, send the CV anyway. We keep a small bench warm against engagements that close on a two-week horizon, and a senior engineer in an underrepresented stack is exactly the candidate the next sales call is most likely to ask for.
What working here is actually like
Honest about the cadence, the time zones, and the trade-offs — before you spend an interview hour on it.
Most of what we do is project-based delivery: a small squad — usually three to eight engineers including the client's own — working on one product for somewhere between three months and a few years. You will be in the client's Slack, on their PR review thread, and in their Jira. The work that lands on your screen on Monday morning is the work that goes out to their users.
Small squads, two-week sprints
We run two-week sprints with a real sprint goal, daily fifteen-minute standups, a Friday demo, and a retro that closes its action items. Story points stay private to the squad; the headline metric we look at is whether the sprint goal landed.
Time-zone reality
Most of our clients sit on US Eastern Time, with some in the UK and Western Europe. From Argentina, Colombia, Mexico, and most of LATAM that overlaps your normal working day. From the eastern half of South America the start gets pushed a few hours later. This suits some people and not others — ask in the interview if it fits how you work.
Autonomy and ownership
You will own features end to end — from the design note, through review, into staging, and to production. Tech leads keep a veto on premature complexity, but they do not micromanage. You are expected to make your own technical calls and to write down the trade-offs when they matter.
Project variety, real depth
Some engineers stay on a single long-running engagement for years; others rotate as projects wind down. The mix means a senior engineer who joined two years ago has likely shipped on two or three different stacks — React Native one quarter, Go services the next.
The three-question fit check
A short, opinionated framework we ask candidates to run on themselves before the first interview. It saves both sides an hour.
The honest answer to these three questions tells us, and you, whether a Siblings seat will be the best year of your career or the wrong fit by month four. We have run this informally with every senior hire since 2022. None of them are deal-breakers in isolation; two of three pointing the wrong way usually is.
QUESTION 1
Is a US business day a normal day for you?
From Mexico, Colombia, Peru, and most of Central America the answer is yes by default. From Argentina, Uruguay, and Chile you will work roughly 11am to 7pm local. From Brazil it depends on the city. If you would resent the schedule by month two, this is a hard no and we would rather know now.
QUESTION 2
Do you want to make the decision, not just implement it?
The squads are small. Mid and senior engineers are expected to write the design note, surface trade-offs in PR review, and disagree with the tech lead in writing when they think the call is wrong. If you prefer to be handed a Jira ticket with an acceptance criteria, this will be uncomfortable from week one.
QUESTION 3
Can you live on one product for a year or more?
Most of our engagements run six to twenty-four months and many run longer. You will get to know the codebase, the on-call alerts, the head of product, and the legacy decisions you wish someone had documented. Engineers who need a new stack every quarter burn out here. Engineers who like to actually finish things settle in.
We will ask versions of all three in the interview. Honest answers, even "no" answers, score higher than performative ones. We have hired engineers who said no to question three and were the right fit for a six-month engagement; we have turned down people who said yes to all three but could not name a real decision they had owned in their last role.
Roles we hire for
These are the open postings today plus the role families we keep hiring against. If you do not see your exact title, send a CV anyway — we keep a small bench warm for the engagements that close the next week.
Senior Java Developer (Argentina or Uruguay residents)
Long-term seat on a product squad working in Java with Angular on the front end and SQL Server as the system of record. Reasonable test coverage, second-pair PR review, and a steady ticket cadence. The role is scoped so that English proficiency is not required — client communication runs through the tech lead.
Requirements
- More than five years of experience with Java (version 8 and up)
- Experience with Angular (mandatory)
- Experience working with SQL Server databases
- English language proficiency not required
Responsibilities
- Assembly of modules according to client needs
- Error corrections based on change requests
- User reassignments
- Generation of tables, request for opinions, and similar workflow tasks
Location and term: Remote work opportunity only for residents of Argentina and Uruguay. Long-term project.
Apply by sending your CV to camila@siblingssoftware.com.
QA Automation Engineer
Owns a real test pyramid on a client project: unit, integration, and end-to-end coverage that gates the release pipeline. Works alongside the engineering tech lead on flake reduction, fixture data, and CI minutes — not handed a script and asked to click through it.
Requirements
- Minimum five years of experience in the position
- Experience working with Azure DevOps (desirable)
- Advanced level of English
- Exclusive commitment to the project required
Skills we look for
- Autonomous, organized, attention to detail
- Open-minded; comfortable disagreeing with engineers and producing the test plan that resolves the disagreement
- Works independently and as part of a team
- Active communication with developers, PO, and tech lead
Term: Medium to long term. Remote work opportunity, scoped as a six-month engagement extending based on the project.
Apply by sending your CV to camila@siblingssoftware.com.
Senior Software Engineer (Go)
Senior seat on a data-intensive Go service in inventory, supply chain, warehousing, or logistics. You will own one slice of the platform — design, build, ship, monitor, and be on call for what you wrote. PostgreSQL at meaningful scale, Terraform and Helm in the deploy path, and GitHub Actions in CI.
Requirements
- Bachelor degree in Computer Science or a related field
- Five years of production experience
- Proficiency with Go (golang) and SQL
- Solid grasp of data structures, algorithms, and their application in data-intensive applications
- Advanced English (mandatory)
- Experience with PostgreSQL, partitioned tables, and 100M+ row tables
- Experience using Terraform, Helm, and GitHub Actions
- Experience in inventory, supply chain, warehousing, or logistics domains
- Experience with SQL data analysis on Snowflake or BigQuery; some familiarity with data pipelines
- Experience with Temporal or another distributed transaction framework
- Experience with JavaScript and an SPA framework in production (Vue or React)
- Public-cloud experience in a production setting (Azure preferred)
What you will own
- Build, deploy, and maintain your own code
- Implement and monitor analytics so the business process stays correct
- Contribute to team-wide business and technical objectives beyond the goals assigned to you
- Participate in cross-functional projects in an agile environment
- Scope, decompose, and organize projects for multiple teammates
- Delegate tasks and coordinate teammates with minimal oversight
- Generate time estimates with reasonable accuracy
- Support standard development practices: idiomatic syntax, design patterns, test-driven development
Location: Remote work opportunity.
Apply by sending your CV to camila@siblingssoftware.com.
Web Backend Software Engineer (Contentful)
Senior backend engineering seat on a website program that uses Contentful as the headless CMS. You will sit at the senior engineering table during planning, surface technical risk, and back up the project manager on mitigation.
Responsibilities
- Participate as senior engineering representative in website development teams and shape development strategy for website projects
- Identify project risk and plan mitigation alongside the PM at project level
- Participate in the full SDLC — specification, design, implementation, testing, and support
- Be proactive about proposing solutions to unexpected events and explaining your reasoning
- Collaborate to set priorities and evaluate options accurately
- Research technical issues and propose technical solutions
- Work toward higher team productivity and lower waste
- Positively influence team members; lead the conversation when it needs leading
- Share successes and failures with the team
Requirements
- Bachelor's degree in Computer Science or an equivalent combination of education and expertise
- More than two years of solid Contentful CMS development
- More than three years of solid programming experience as a backend developer
- B2+ level of written and spoken English
- eCommerce or low-code certification
- Cloud certification
- Software development certification
- Agile certification
- Knowledge of microservices and/or serverless is a plus
- Understanding of OOP patterns, OO languages, or functional programming
- Proficiency with web-related protocols and architectures
- Programming experience in Node.js, PHP, Python, or Java
- Database knowledge (relational and/or non-relational)
- Understanding of design patterns, design principles, algorithm analysis
- Clean-code experience
- CLI experience
- Source-control management and tools (Git, Source Tree, GitKraken, GitHub)
- Knowledge of API concepts and integrations
- Experience working in an agile environment (Scrum, Kanban)
- Excellent troubleshooting skills
- Excellent knowledge of general software engineering principles
Location: Remote work opportunity.
Apply by sending your CV to camila@siblingssoftware.com.
Web Operations Engineer
Operations seat on a web platform: keep the application available, instrument it so the team can see what is happening, automate the routine work, and run the security upgrades on a calendar instead of in a fire drill.
Responsibilities
- Maintain the health and performance of web infrastructure and services; implement scalability, reliability, and security best practices
- Collaborate with cross-functional teams to identify and resolve infrastructure issues
- Ensure high availability of company web applications and services
- Create, implement, and maintain disaster recovery and business-continuity strategies
- Respond promptly to critical incidents and minimize downtime
- Stay current on technology and plan regular upgrades for security and performance
- Execute regular updates and upgrades to web servers, databases, services, and related components
- Set up and maintain monitoring for web applications
- Generate regular reports on system metrics and performance
- Run regular security audits and address vulnerabilities with the security team
- Implement and manage security measures against common web threats
- Build and maintain automation scripts for routine tasks
- Work toward automated deployment, scaling, and monitoring
- Support the development team during application deployments and updates
Requirements
- Bachelor's degree in Computer Science, Information Technology, or a related field
- More than three years of proven experience as a Web Operations Engineer or similar role
- Strong knowledge of web server technologies, including Apache and Nginx
- Proficiency in scripting languages (Python, Shell) for automation
- Experience with cloud platforms (AWS, Azure) and containerization (Docker, Kubernetes)
- Familiarity with monitoring tools (Nagios, Prometheus)
- Familiarity with version-control systems (Git)
- Solid understanding of security best practices and the ability to implement them
- Excellent problem-solving and communication skills
- B2+ level of written and spoken English
Location: Remote work opportunity.
Apply by sending your CV to camila@siblingssoftware.com.
Penetration Tester
Run manual attack and penetration tests against client infrastructure and applications. Coordinate red team assessments, respond to new threat intelligence, and feed remediation work back into the engineering squads.
Responsibilities
- Perform and coordinate manual attack and penetration (A&P) testing using current tooling
- Run red team assessments
- Respond to new security threats and help implement new requirements
- Work in a team environment while maintaining confidentiality of investigation information
Requirements
- Strong IaaS security skills with a focus on AWS, Azure, and GCP
- Deep knowledge of OWASP concepts across solution types
- Experience with security and penetration tooling: Nessus, Burp Suite, Qualys, Tenable, PowerShell, Electra, Cydia Impactor, Wireshark, ADB, Drozer
- Bug bounty participation is a plus
- Advanced English (mandatory)
Location: Remote work opportunity.
Apply by sending your CV to camila@siblingssoftware.com.
Other role families we keep hiring against: front-end engineers (React, Next.js, Angular, TypeScript), full-stack engineers, mobile engineers (React Native, Flutter, native Swift and Kotlin), DevOps and SRE, data engineers, and product or technical leads. If your stack lines up but no posting matches, send a CV with a one-paragraph note about the kind of work you want next.
How we work day to day
Engineering practices that run on every squad — not aspirational slogans on a wall.
Pull-request review is the default
Nothing merges without a second pair of eyes. Two reviewers on anything that touches a public surface. CI must be green — no override merges — and the description should explain the trade-off, not just the diff. New engineers do their first review on day one, even if it is small.
Tests, observability, and runbooks
Tests live next to the code they cover. Each squad owns its observability slice — structured logs, RED metrics, and traces — and the runbooks for the top alerts. If a system pages someone, that someone is on the squad that wrote it.
Pairing on hard problems
Pair programming is not a daily ritual, but it is the default when the ticket is genuinely hard, when an engineer is new on the codebase, or when a senior is mentoring a mid engineer through a redesign. We block 60 to 90 minutes for it, not five.
Retrospectives that close
Up to three action items per retro, each with a named owner. The next retro opens with the close rate on the previous batch. Retro theater — lots of post-its, zero follow-through — is the failure mode we watch for, on both the squad side and the client side.
Documentation lives in the repo
Architectural decision records, runbooks, and design notes live next to the code, in Markdown. Confluence pages are fine for the client, but the system of record for engineering decisions is the repo. Future-you reads them more than the original reviewer ever did.
Refusal to over-engineer
Tech leads have an explicit veto on premature complexity. We will not start a microservice migration in sprint zero, we will not roll our own queue, and we will not pick a third-party for the resume. If a senior engineer wants to use a new tool, the ADR explains why the simpler thing was rejected.
2025–2026 NOTE
Almost every client repo we work in today has at least one AI coding assistant in the loop, most often Cursor, Claude Code, or GitHub Copilot, plus AI-assisted code review on pull requests. The skill we now interview for has shifted from raw output to judgment under AI assistance — reviewing AI-generated diffs, rejecting them when the trade-off is wrong, and writing the test that proves the model got it wrong. If you have spent the last year using these tools seriously on real code, say so in your CV note; if you have deliberately avoided them, that is also a fair conversation to have on the first call.
A typical first month at Siblings
Drawn from how senior engineering onboardings have actually gone over the last two years. Yours will vary, but the shape is real.
WEEK 1
Accounts, runbooks, first PR
Laptop arrives, accounts and access provisioned, two-factor everywhere. The tech lead walks you through the architecture for half an hour and points you at the runbooks the squad already wrote. By Wednesday or Thursday you open your first pull request — usually a small, real ticket on the simplest open issue. Two reviewers, CI green, merged before Friday.
Goal: prove the loop works end to end, not to ship a feature.
WEEK 2
Shadow the client, take a slice
You join the client's standup, sit in on the next sprint planning, and pick up a real piece of the work. Usually behind a feature flag so the blast radius is small. You read one or two architectural decision records the team already wrote, and you write down questions about decisions that are not documented yet. We expect senior engineers to ask the awkward question.
Goal: own a slice, not just observe.
WEEK 3
First design note, second pair PR
You write the first design note that is yours: trade-offs explicit, alternatives named, the reason the simpler thing was rejected on the page. The tech lead reviews it, sometimes pushes back, and the better version goes into the repo as an ADR. You start reviewing other engineers' pull requests — mid as well as senior — and one of them is now reviewing yours.
Goal: contribute to engineering decisions, not just code.
WEEK 4
Demo your slice, close your first retro item
At the Friday client demo you show what you built behind the flag, and you flip the flag on for an internal cohort if the metrics support it. Your name is on one of the three retro action items, and by the next retro it is closed. You start to know who on the client side decides what, and who is just on the call.
Goal: a senior engineer on the squad, not a new hire being managed.
No floor, no shadowing-for-three-months, no "ramp-up project" that never ships. Engineers who like the deep end say this is the part of the company they would not change.
Where we hire
We are remote-first across Latin America. The core engineering team works out of our office in Córdoba, Argentina at Sipe Sipe 1479, where engineers occasionally collaborate in person. Most engagements run fully remote, with the squad spread across multiple LATAM countries.
Some roles are residency-restricted by the client's legal or compliance setup — the Senior Java Developer role above, for example, is only open to residents of Argentina or Uruguay. Most other roles are open across Argentina, Colombia, Mexico, Uruguay, and other LATAM countries with reliable internet and a working day that overlaps US Eastern Time. Specific country restrictions are stated in each posting and confirmed in the interview before any offer is made.
Because most clients sit on EST or UK and Western European time, you will work US business hours from LATAM. From Mexico City or Bogotá that is a normal day. From Buenos Aires the day starts a couple of hours later than a local 9-to-5 and ends a couple of hours later. We are explicit about this in the interview because it is not for everyone, and pretending it is will burn out a hire by month four.
Working at an outsourcer vs in-house vs as a freelance contractor
For senior engineers in LATAM choosing between the three. We have hired from all three pools and lost engineers back to all three pools. Here is the honest comparison.
SIBLINGS (OUTSOURCER)
One client at a time, long arc
- Sit on one client engagement for 6 to 24+ months
- USD-linked monthly contractor pay
- Senior peers on the same squad and a tech lead
- You stop being on-call when the engagement ends
- Less direct influence on the client's long-term roadmap than an internal hire
- No equity
Best when you want depth on one product and steady monthly USD pay without running your own sales pipeline.
IN-HOUSE EMPLOYEE
One company, long horizon
- Long arcs measured in years, not engagements
- Local salary, often local currency, often equity
- Country-specific employment benefits
- More influence on hiring, on roadmap, on culture
- Single-stack and single-domain risk
- Re-orgs and political weather are yours to absorb
Best when you want to build one company over a long horizon and you accept the local-pay and re-org trade-off.
FREELANCE / MARKETPLACE
Many clients, your own pipeline
- Multiple shorter engagements, more autonomy on hours
- Hourly USD billing on Upwork, Toptal, or direct contracts
- You run sales, contracts, invoicing, and taxes
- No peer review, no shared on-call rotation
- Income variance from quarter to quarter
- Career arc depends on which jobs you accept
Best when you want maximum autonomy, are comfortable running a business, and do not need the mentorship of a senior squad.
None of these is universally better. The senior engineers we keep longest are usually the ones who actively chose option A over option B or C for a clear reason. The ones who treat us as a default because nothing else is open are also the ones who churn fastest. We would rather lose you to the right in-house job than have you spend a year in the wrong outsourced seat.
What we can describe honestly
A US-based company hiring across LATAM has a specific shape of offer. Here is what that shape is.
USD-linked compensation
Compensation is set in USD and reviewed regularly. The exact contract structure depends on your country and on whether the engagement is project-based or a dedicated team seat — we work that out individually with each candidate during the offer stage.
Long-term project visibility
Many engagements run for one to three years. Some engineers have been on a single client engagement for longer than that. We tell you up front what the project is, who the client is, and what the realistic horizon looks like.
English-language work environment
The day-to-day working language is English — PRs, design notes, standups, retros, client calls. Spanish flows on the side for the LATAM teammates. Working in English with US and EU senior engineers is one of the things that grows a career here.
Stack variety
You will work across modern stacks rather than spend three years on a single framework: Go, Java with Spring, Node, Python with Django or FastAPI, React, Next.js, Angular, React Native, Flutter, AWS, Azure. The exact mix follows the client. The shape of our work generally mirrors what senior engineers report on the Stack Overflow Developer Survey — backend Go and Python are growing, Java with Spring is still everywhere, and TypeScript runs both ends of the application for most product squads.
Growth path through tech lead
We hire mostly mid-senior engineers and grow tech leads from inside. Promotion is tied to the scope you actually own on real engagements, not to tenure or to an internal panel. The growth-path diagram above is what that looks like in practice.
Flexible schedule, with a window
Within the client overlap window, your day is yours. We do not require all-day Slack presence, we do not run mandatory after-hours calls, and we will not page you on systems your squad did not build.
What we do not promise
We are honest about what is not on the table by default: stock options, a fixed PTO calendar, healthcare benefits attached to a specific country's payroll, and free meals. Some of those depend on contract structure and country and we work them out individually; some simply are not part of how a US-based outsourcer hiring LATAM contractors operates. If those are critical to you, we should talk about it before either side spends an interview hour.
How to apply
One inbox, one process, no portal to register on. We read every CV that comes in.
What to send
- Your CV or résumé, ideally as a PDF
- A link to GitHub, a portfolio, or a couple of representative repos — even private snippets you can talk through
- A short note about why this role and what kind of work you want next
- Any certifications or credentials relevant to the posting
What happens next
- CV review within three to five business days
- If there is a match, a 45-minute technical interview about the role, your experience, and the project
- For some roles, a small take-home or a live coding exercise
- A second conversation with the tech lead or hiring manager if the squad is already known
- Offer, contract structure, and start date
Send your CV to:
If you would rather start by reading about the company first, take a look at who we are, our leadership team, our founder Javier Uanini, or the client case studies that show the kind of work the squads ship.
If you want to understand the kinds of engagements you would actually sit on, the staff augmentation and dedicated development team pages describe what we sell to clients in those models. You can also browse our LinkedIn page or our GitHub organization to see the public side of the team.
Candidate FAQ
What time zones do candidates actually work?
Most clients run on US Eastern Time. From Mexico City, Bogotá, and Lima the overlap with a 9-to-5 EST day is six to eight hours and matches a normal local day. From Buenos Aires, Montevideo, and Santiago the day starts a couple of hours later and ends a couple of hours later. We also run a smaller number of engagements on UK or Western Europe time. Specifics get confirmed during the interview before anyone signs anything.
What level of English is required?
It depends on the role. Client-facing engineering and QA work needs advanced spoken and written English. A few backend roles — like the Java with Angular position open today — are scoped so that English proficiency is not required because client communication runs through the tech lead. Each posting states the language bar explicitly.
Are these contractor roles or employee positions?
Most engagements run as long-term contractor agreements, which is the common arrangement when a US-based firm hires across LATAM. The exact paperwork depends on your country and on whether the engagement is project-based or a dedicated team seat. We work it out with each candidate before the offer.
What does an offer look like for an LATAM contractor?
Compensation is set in USD and reviewed regularly. Payment cadence is monthly against a contractor invoice in most countries. We help with the paperwork on the first invoice cycle so the engagement starts cleanly. We do not publish public salary bands because seniority, country, and engagement type each move the number; we share a specific range during the first interview once we understand which seat the offer would land in.
How long does the interview process take?
We aim for one to two weeks from CV to offer. CV review takes three to five business days. Selected candidates run one or two technical interviews, sometimes with a small take-home or a live coding exercise depending on the role. We try not to drag it out, and we will tell you which round is the decision round.
Do you use AI coding assistants on real engagements?
Yes. As of 2025 and 2026, almost every client repo has at least one AI coding assistant in the loop, most often Cursor, Claude Code, or GitHub Copilot, plus AI-assisted code review for pull requests. We expect senior engineers to be comfortable reviewing AI-generated diffs, rejecting them when the trade-off is wrong, and writing the test that proves the model got it wrong. The skill we screen for has shifted from raw output to judgment under AI assistance.
What stacks come up most often on real engagements?
Backend in Go, Java with Spring, Node.js, and Python with Django or FastAPI. Front end in React, Next.js, Angular, and TypeScript. Mobile in React Native, Flutter, and native Swift or Kotlin. Cloud and DevOps work on AWS and Azure with Docker, Kubernetes, GitHub Actions, and Terraform. The mix changes engagement to engagement, but those are the stacks the squads pick up most weeks.
Talk to a recruiter
Prefer to send a message rather than an email? Use the form below and we will route it to recruiting. To apply directly with a CV attached, email camila@siblingssoftware.com.