Production systems, not prototypes
The platforms you work on run in factories, depots, workshops and finance teams. They are measured on uptime and correctness, so the engineering standard is set by what happens when something breaks at 2am.
Careers
Build the systems enterprises depend on.
FictiveBox engineers ERP platforms, IoT systems, SaaS products and railway software for operators that cannot afford downtime. The work is production software with real users and real consequences, built by small senior pods that own what they ship.
Presence in Noida · Chennai · Kolkata · Lucknow · Hyderabad, India
Why FictiveBox
Engineering, not ticket queues.
What the job actually looks like here, stated plainly. Everything below is how the company already describes its delivery model to the clients paying for it.
Ownership end to end
Pods are scoped around an outcome rather than a set of tickets. You take a problem from architecture through delivery to the telemetry that tells you whether it worked.
Depth in hard domains
Rail, manufacturing, logistics, energy and regulated SaaS. These are domains where you have to understand the operation before you can usefully change the software.
Engineering culture
Build it. Own it. Operate it.
How teams are actually structured and what is expected of the code that leaves them.
Architects write code
Every pod has an architect who is still in the codebase and an engineering lead who works inside the client's standups. Design and implementation are not handed between two different people.
You stay with what you design
The engineer who designs a system is the engineer who stays with it. You see your own decisions play out in production instead of handing them to someone else to operate.
Production from the first sprint
Work runs in two-week sprints with continuous delivery and production telemetry from sprint one, so you are reading real behaviour rather than demoing a staging environment.
Outcome pods, not staff augmentation
Engagements are scoped as outcomes rather than seats. Teams are small and senior, and the pod owns the result rather than a ticket queue.
The client owns everything you build
Source code, infrastructure definitions, runbooks and documentation are handed over cleanly. That standard is why the work has to be readable by someone who was not in the room.
Systems that cannot quietly fail
Much of the work runs in regulated and industrial settings, engineered to standards such as SOC 2, ISO 27001, GDPR, HIPAA and TS 50701. Correctness and auditability are requirements, not preferences.
Career areas
Where engineers work here.
Each area is a practice the company runs today. Follow any of them to read what that team actually builds.
ERP Engineering
Modular, API-first ERP platforms. Finance, supply chain and manufacturing modules with clean boundaries, plus migrations off monoliths that can no longer be changed safely.
See the workIoT and Connected Systems
Edge-to-cloud telemetry at fleet scale. Device firmware, ingestion pipelines, digital twins and the fleet tooling that keeps them observable.
See the workSaaS Product Engineering
Multi-tenant product foundations: tenancy models, usage-based billing, enterprise identity and the observability that makes an SLA defensible.
See the workData, AI and ML
Applied machine learning in production rather than in notebooks. Retrieval systems, forecasting, computer vision and the MLOps around them.
See the workCloud and DevOps
Landing zones, Kubernetes platforms and cost engineering across AWS, Azure and GCP, built so delivery teams can ship without filing tickets.
See the workWeb and Mobile Engineering
React, iOS and Android work for operators in the field: offline-first apps, operator consoles and design systems that survive contact with real users.
See the workCybersecurity and Compliance
Engineering to SOC 2, ISO 27001, GDPR, HIPAA and TS 50701. Compliance automation, rail cybersecurity and incident response.
See the workRailway Systems
Applied railway research and delivery: rolling stock telematics, depot and MRO platforms, permit and overhaul planning systems for rail operators.
See the work
Open positions
Find your role.
Every open position is listed here. We do not post roles we are not actively hiring for.
No open roles right now.
There are no positions open at the moment. We still read every profile that comes in, and we go back to them first when a team starts hiring. Tell us what you build and which area interests you.
Share your profileLife at FictiveBox
Where the work happens.
Presence in five cities across India. Noida is the headquarters and runs core platform engineering, with 24/7 site reliability cover for enterprise customers.
- Headquarters
Noida
- Presence
Chennai
- Presence
Kolkata
- Presence
Lucknow
- Presence
Hyderabad
A normal fortnight
Work runs in two-week sprints with continuous delivery. Your pod sits inside the client's standups rather than reporting across a wall, and production telemetry is live from the first sprint, so review conversations are about measured behaviour instead of opinions.
What good looks like
Clients receive the source, the infrastructure definitions, the runbooks and the documentation, and can walk away with all of it at any time. Writing for the engineer who was not in the room is the baseline, not a nice-to-have.
Growth
Grow with the problems you solve.
There is no separate ladder to climb here. Scope grows with what you have proven you can carry.
Architecture in reach
Pods are led by an architect who is still writing code. Design decisions are made next to you and explained, rather than arriving as a diagram from another floor.
Breadth across domains
The company works across rail, manufacturing, logistics, retail, education and energy. Engineers see more than one operating model, which is what makes the next system easier to design.
Consequences you can see
Staying with a system through production means you find out whether your decisions were right. That feedback loop is the fastest way anyone gets better at this.
How applying works
What happens after you hit send.
Three steps, described exactly as they work. We will walk you through the rest of the process when we contact you.
- 01
Share your profile
Send your details through the form on this page. Tell us what you have built and what you want to work on next. If a specific role is open, apply to it directly.
- 02
We read it
Applications go to info@fictivebox.com, where a person reads them. We look at what you have actually shipped and where it ran, not at how the resume is formatted.
- 03
We get in touch
If there is a fit with current or upcoming work, we contact you to talk about the role in detail and walk you through the rest of the process from there.
FAQ
Questions candidates ask
If your question is not here, ask it in the form below or email us directly.
- How do I apply for a job at FictiveBox?
- Use the form on the careers page to share your profile. It reaches info@fictivebox.com directly, where a person reads it. If a specific role is listed as open, apply to that role so your application is matched to it.
- What kind of engineers does FictiveBox hire?
- FictiveBox is an enterprise software engineering company, so hiring follows the practices it runs: ERP engineering, IoT and connected systems, SaaS product engineering, data and machine learning, cloud and DevOps, web and mobile engineering, cybersecurity and compliance, and railway systems.
- Where are FictiveBox roles located?
- FictiveBox has presence in five cities across India: Noida, Chennai, Kolkata, Lucknow, Hyderabad. Noida is the headquarters. The location of any individual role is stated on that role's listing.
- Can I apply if no role matches my experience?
- Yes. The form accepts a general application and lets you name the area you are interested in rather than a specific vacancy. Profiles are kept on file and revisited when relevant work comes up.
- What happens after I apply?
- A person reviews your application and contacts you if there is a fit with current or upcoming work. You will be told what the rest of the process involves at that point.
- Does FictiveBox hire experienced engineers?
- Yes. Teams are small and senior, and pods are led by an architect who writes code alongside the team. Experience levels for any specific opening are stated on that role's listing.
- What will I work on?
- Production systems for enterprise and public sector operators, including ERP platforms, IoT and telemetry systems, multi-tenant SaaS products and railway software. Work runs in two-week sprints with production telemetry from the first sprint.
General application
Tell us what you can build.
Send your profile even when nothing matching is open. Applications reach a person, not a keyword filter, and we go back to them when a team starts hiring.
Prefer email? Write to info@fictivebox.com.