Engineering Intern: Testing, Automation & Development

• Location: Bangalore (On-site, HSR Layout)
• Duration: 4–6 months, full-time
• Potential outcome: Full-time offer for exceptional performance
• Reports to: Tech Lead

You will join a small team and make sure what we ship works the way it should. Half the job is finding what is broken. The other half is writing code: tests that catch it next time, and fixes and features of your own.

---

About FrontPage

• FrontPage is a financial markets community platform with ~1.5L DAU / 6L MAU, profitable with real subscription + ad revenue.
• The stack spans community systems, real-time market data ingestion, trading simulation, mobile + web clients, and cloud infra under live market load.
• It's stable, revenue-backed, and battle-tested. And we're now increasing our build pace.

---

What You'll Work On

Testing and test automation for the FrontPage apps, and the tooling behind them. You'll also write product code.

1. Test the apps. New features and releases. Find what's broken before users do, and report it so a developer can fix it in one go.
2. Write automation. Turn the flows that matter into tests that run on their own, on simulators and in CI. Keep them from going flaky.
3. Help build the testing pipeline. The tooling that plans, runs and reports tests: test accounts, simulators, builds, the checks around them. You'll contribute to that code.
4. Ship development work. Bug fixes you found yourself, small features, tooling. We expect you to write real code in the apps and the backend, not only tests.
5. Work heavily with AI tools. Claude Code, Cursor, Codex or similar will be part of your daily workflow: for writing tests, reading unfamiliar code, drafting fixes and building tooling. You'll be expected to use them well, check what they produce, and know when not to trust them.

---

What We Look For

1. You like breaking things and finding out why. You notice when an app does something slightly wrong, and you can write down the exact steps to make it happen again.
2. You have built software. Projects, internships, open source, anything you shipped and can walk us through. Our stack is Kotlin, Swift, Node.js, Python, MySQL and Redis.
3. You're already AI-native. You build with Claude Code, Cursor, Codex or similar, and you've started developing judgment about it: when to trust it, how to check its output, when to reason it out yourself. Here the AI is a tool you work with, not the subject.
4. You can read unfamiliar code. To test a screen well, you'll often read how it's built. You don't wait for a ticket: understand → investigate → try → report → fix.

---

This Role Is Probably Not For You If

1. You prefer to stay at the surface. Testing here means going down the layers: reading the code behind a screen, tracing a bug to its cause, and implementing the fix when asked. If you'd rather report what you see and hand it over, this will feel uncomfortable.
2. The developer who thinks testing is beneath them. You'll write product code, but you'll also spend days finding bugs on a simulator. If that sounds like a demotion, you'll be unhappy.
3. The intern who trusts the green check. If an automated check says PASS and you move on, you'll miss the bug it missed. We want you to doubt it and prove it right or wrong.
4. The specialist who wants one app and one language. You'll touch Android, iOS, the backend's API and the pipeline's Python in the same week.
5. The spec-waiter. If you need a detailed spec before you start, you'll be stuck often. A ticket and the code are usually all you get.

---

Why This Could Be Interesting

Unusually broad exposure, early: mobile apps, backend, test automation and the testing pipeline, all inside a live platform at scale, working directly with the people making the calls rather than several layers removed. Steep learning curve, real ownership.

---