Life at SomeTech.work

Small team. Accountability by design.

We do not hire to grow headcount. We hire when the work demands someone whose name goes on the outcome. Here is what we look for, and what it actually looks like to be on the team.

Life at SomeTech.work
5
People on the team
100%
Named lead on every engagement
8+
Years as the same small team on every project
How we work

Accountability by design. Your name on the file.

We run small and senior. Every engagement has a named lead: one person who scoped it, ships it, and answers for it when it drifts. When you join a project here, you are that person.

One named lead per engagement. The person who scoped it ships it. You work directly with clients who have real decisions to make, and you have the latitude to make calls, not just implement them.

Engagements run short and specific. You will move across strategy, build, and support depending on the project shape. If you prefer a long, single-track role, that is not the wrong answer. It is just the wrong company.

Day at SomeTech.work

Three snapshots, same bar for quality

No slide decks about culture. This is what the week tends to look like when you own delivery end to end.

Developer focused at a laptop in a calm workspace
Deep work

Quiet blocks, real depth

Long stretches without standing meetings. You protect focus because the client expects judgment, not activity.

Team collaborating around a laptop
Collaboration

Async first, sync when it earns

Decisions land in writing. Calls exist when ambiguity would cost a day. Whiteboards are for alignment, not theatre.

Interview or hiring discussion in an office setting
Hiring

Paid reads, no free work

Assessments mirror the job. Short loops. If it is not a fit, we say so early so neither side burns runway.

Working pattern

Async-first, named lead, EU time.

Core overlap sits in European working hours. Written updates beat status calls. When we need sync, it is short and decision-shaped.

Comp and contract: We hire into scoped roles with clear ownership. Engagements start with contracts so both sides can exit cleanly if reality does not match the conversation. Technical hiring uses one paid assessment, reviewed by the person you would ship beside.

What we look for

Three things we will not compromise on

01

Own the outcome, not the ticket

The brief ends at shipped and working, not at merged or reviewed. The gap between "done" and "actually done" is your problem, not the next person in the chain.

02

Write your thinking clearly

Async-first team. If you cannot write a tight paragraph that explains a trade-off, the quality of your code does not compensate. We make decisions in writing before we make them in calls.

03

One owner. Full context.

The person who scopes the work ships the work. You will talk directly to clients when it matters. That is not a burden: it is the only way to know whether the work actually solved the problem.

Wrong fit

Honest about who we are not

We would rather lose a strong candidate early than waste both sides' time on a three-month engagement that ends badly.

  • You want a single long track and do not like context-switching between strategy, build, and support
  • You need a manager to unblock you and are not comfortable making calls independently
  • You prefer to deliver the artefact and move on. Outcome is someone else's concern.
  • You want a firm that promotes you into a lead title over time; we hire people who already own delivery end-to-end.
Open roles

What we are hiring for now

Contract · Part-time

Senior Full-Stack Engineer

India · Remote

Next.js, React, TypeScript, and Supabase. You own features from the architecture call to the production deploy. We read the codebase before kickoff; you should too.

Contract · Project-based

WordPress Engineer

India · Remote

Performance-first builds, ACF, Gutenberg blocks, WooCommerce. You understand why WordPress has a reputation and how to make it undeserved. Strong opinion on what ships versus what waits.

How we hire

Short, specific, zero surprises

We do not run multi-stage panels or ask you to work for free. If the application looks like a fit, the first call is 30 minutes: us explaining the project shape, you explaining how you work.

For technical roles there is one scoped assessment: paid, relevant to the actual work, and reviewed by the person you would work alongside. A paid assessment, relevant to the actual work. Zero whiteboard sessions.

If it is a fit, we move to a short engagement. Contracts first, always, so both sides have a clean exit if the reality does not match the conversation.

Concrete solution

Bring the operational risk.You get a clear diagnosis and a concrete next step.

Book a 15-minute operator call

We are the right fit if you want a team that pushes back when it matters.

Reviewing first?

Company evidenceon the site.

Engagements with commercial outcomes on Work. Team bios and operating model on About. Nothing to download. Review it before you commit to a call. Open to review. Commit when ready.