Build Merak with us
A personal AI learning system. Help us make it teach better.
Merak Intelligence, Inc. is a Delaware company building a personal AI learning system intended to expand what people can understand, question and do throughout their lives. Our founder built Educator 1, the first iPhone version. We’re meeting people who could help build the next teaching formats.
Our direction combines teaching models and learning companions, a shared learning engine and personal learning history, so learning can continue across goals, subjects, formats and interfaces. These are the foundations we intend to develop; the first implementation does not establish that the whole direction is already available.
We’re starting with adult consumer learning. Workplace, school and partner products are future opportunities. Each would need its own evidence, permissions and safeguards. The founder built the first app and AI backend and has worked full-time on Merak since June 2026.
Our current hiring situation
We have not completed the financing needed to fund the hires described here. Every role on this page is a planned, funding-dependent role. We are accepting expressions of interest, not announcing currently funded vacancies or offering immediate employment.
Completing financing would not automatically activate every role. Each hire would also require an approved role budget, an agreed remit, a lawful employment arrangement and written terms. We may change, postpone or cancel planned roles. There is no confirmed fundraising-close date or employment-start date.
Please do not resign, relocate, buy equipment or incur costs in reliance on this page or a preliminary conversation. We do not charge candidates recruitment fees or ask prospective employees to work unpaid before financing is completed.
What the timeline means
- Now, before financing: we can review expressions of interest and hold limited exploratory conversations. No immediate job or selection outcome is promised.
- First hiring-status review, planned for 4 December 2026: we will review financing and role priorities and update this page if the status changes. This is a review checkpoint, not an assurance that financing will close by then.
- Further hiring-status review, planned for 1 February 2027: we plan to reassess financing and role priorities. The roles may still be unfunded, deferred or cancelled at that point. Neither review date is a deadline or promise for financing, a hiring decision or an employment start.
- After financing is completed: we will activate only roles with an approved budget and employment arrangement, publish or share the applicable pay information, and confirm whether to begin or continue a formal process.
- Before an employment start: the employing entity, location, duties, pay, any equity terms, remaining conditions and start date must be agreed in writing. Notice periods and relocation needs would be discussed individually.
Earlier January–December 2027 start months were planning assumptions and have been withdrawn from these descriptions. The first-90-day outcomes below run from an agreed employment start, not from today or from an application. No application closing date is currently set.
What exists and what is planned
Today's first version is the Educator 1 iPhone learning experience. A working journey has been demonstrated locally, and an internal TestFlight build has been processed. This does not establish that every described journey is available to external testers. Wider access and the complete installed experience require separate release verification.
Educator 1 is a teaching system built on foundation models. Tutor, Explainer, broader adaptive learning, additional clients and organizational products are planned expansions, subject to evidence, capacity and funding. We have not established claims of learning improvement, consumer traction or revenue.
Planned role families
Founding engineer, systems
Own the reliability, recovery and economics of the learning service.
Read the planned role
This is a potential future role, not a currently funded vacancy. Its creation, final remit, employment location, compensation and start date depend on completed financing and an approved hiring decision.
The planned remit
This planned hands-on technical leadership role would own how Merak is built, released and operated. You would work directly with the founder. Collaboration with future specialists depends on which roles are funded and filled; an existing engineering team or staffed on-call rota is not being promised.
Proposed responsibilities
- Stateful services: API gateway, workers, Postgres, queues, storage, backups and recovery.
- Monitoring, incident coordination, deploy and rollback procedures, and a sustainable coverage plan agreed with the founder.
- Security controls, permission boundaries, provider failure handling, capacity and full service cost.
- Practical CI, code review and technical decisions; specialist security work would be scoped with qualified providers when funded.
Relevant evidence
- An operated system you can explain, including a consequential failure and your own recovery decisions.
- Evidence of judgment about data integrity, security, cost and latency.
- Hands-on engineering and constructive leadership of other engineers.
Not required: an SRE title, a particular number of years, machine-learning experience or an education background.
Illustrative first 90 days after an agreed start
Map critical learner journeys, establish reliability and cost baselines, and agree release criteria. By day 90, demonstrate the agreed journey and representative recovery cases, with monitoring and usable runbooks.
These are proposed outcomes, not a promise of resources, launch dates or business results. The funded scope and available collaborators would be agreed before employment.
Compensation: no approved role-specific offer or grant is announced here. See the pay and equity disclosures below. Planned employment: full-time if activated; country eligibility and remote or hybrid arrangements must first be confirmed.
Founding LLM research scientist
Build evaluated teaching systems on foundation models.
Read the planned role
This is a potential future role, not a currently funded vacancy. Its creation, final remit, employment location, compensation and start date depend on completed financing and an approved hiring decision.
The planned remit
This planned applied research and engineering role would own generation quality, evaluation and model-provider trade-offs. Merak builds on foundation models; this is not a foundation-model pretraining role. You would work with the founder and any learning or engineering specialists subsequently engaged.
Proposed responsibilities
- Generation and checking pipelines for structured learning material.
- Evaluation sets, failure analysis, regression checks and comparison with expert judgment.
- Quality, latency, provider limits and full generation cost, including failures and retries.
- Controlled model releases and recovery; Tutor, Explainer, voice and avatar work would be separately prioritized and funded.
Relevant evidence
- An LLM feature you shipped and personally evaluated.
- An example where an evaluation missed a real failure and how you changed it.
- A measured model, cost or latency decision, including its limitations.
Not required: a PhD, publications or pretraining experience.
Illustrative first 90 days after an agreed start
Establish a repeatable quality and cost baseline, identify consequential failure categories, and deliver one measured improvement or a documented decision not to ship. By day 90, own an evaluation and release process for the agreed scope.
These are proposed outcomes, not a promise of resources, launch dates or business results. The funded scope and available collaborators would be agreed before employment.
Compensation: no approved role-specific offer or grant is announced here. See the pay and equity disclosures below. Planned employment: full-time if activated; country eligibility and remote or hybrid arrangements must first be confirmed.
Founding iOS engineer
Own a trustworthy learning journey on iPhone.
Read the planned role
This is a potential future role, not a currently funded vacancy. Its creation, final remit, employment location, compensation and start date depend on completed financing and an approved hiring decision.
The planned remit
This planned role would own the SwiftUI product surface and its release process. A learning journey has been demonstrated locally and an internal TestFlight build has been processed. Complete installed acceptance and wider testing remain separate work. You would work directly with the founder; other hires are planned, not assumed to be in place.
Proposed responsibilities
- The agreed Home, path, lesson, practice and review journeys.
- Loading, empty, error, offline and interrupted states, accessibility and client instrumentation.
- TestFlight and App Store preparation, release evidence and current platform requirements.
- Clear consent and AI disclosures, account lifecycle integration, and StoreKit only when paid-offer work is activated.
Relevant evidence
- A consumer iOS app you shipped and can walk through.
- A diagnosed lifecycle, interruption or state-recovery problem.
- Evidence that accessibility and release verification were part of your work.
Not required: AI or education experience.
Illustrative first 90 days after an agreed start
Baseline the agreed journey on supported devices and resolve the most consequential interruption and accessibility issues. By day 90, own a verified installed journey and repeatable release process for the funded scope.
These are proposed outcomes, not a promise of resources, launch dates or business results. The funded scope and available collaborators would be agreed before employment.
Compensation: no approved role-specific offer or grant is announced here. See the pay and equity disclosures below. Planned employment: full-time if activated; country eligibility and remote or hybrid arrangements must first be confirmed.
Founding engineer, learner platform
Make accounts, permissions and learning history dependable.
Read the planned role
This is a potential future role, not a currently funded vacancy. Its creation, final remit, employment location, compensation and start date depend on completed financing and an approved hiring decision.
The planned remit
This planned role would own account and learning-history foundations. You would agree the actual data contract and priorities with the founder and the engineers then engaged; future messaging, web and Android integrations are conditional roadmap work.
Proposed responsibilities
- Account authority, data models, permissions and client APIs.
- Entitlements and history correctness under retries, interruptions and concurrent work.
- Export, correction, deletion, consent records and data minimization.
- Reliable events and data definitions; additional messaging channels only where technically, commercially and legally supportable.
Relevant evidence
- An auth or permission design you owned, including a failure case.
- A migration or stateful workflow with tested recovery.
- A clear account lifecycle, including deletion and export.
Not required: machine-learning experience.
Illustrative first 90 days after an agreed start
Agree and test the account/history contract and critical invariants. By day 90, demonstrate owner-bound state and the agreed permission, retry and lifecycle cases end to end.
These are proposed outcomes, not a promise of resources, launch dates or business results. The funded scope and available collaborators would be agreed before employment.
Compensation: no approved role-specific offer or grant is announced here. See the pay and equity disclosures below. Planned employment: full-time if activated; country eligibility and remote or hybrid arrangements must first be confirmed.
Chief of staff, operations
Build reliable company operations as the team forms.
Read the planned role
This is a potential future role, not a currently funded vacancy. Its creation, final remit, employment location, compensation and start date depend on completed financing and an approved hiring decision.
The planned remit
Merak is founder-led today. This planned role would coordinate company operations, professional providers and hiring administration as financing and hiring permit. It does not assume an existing international team, employer-of-record contract, adopted equity plan or approved vendor budget.
Proposed responsibilities
- The company calendar, named filing owners and coordination with qualified legal and tax advisers.
- Commitment records, bookkeeping coordination, monthly reporting and budget control.
- Employment setup, IP documentation and onboarding with counsel and approved providers.
- Recruiting logistics, investor-update preparation, vendor administration and diligence records.
Relevant evidence
- An operating process you owned through a real exception.
- Reliable financial and deadline tracking.
- Clear collaboration with founders, accountants, lawyers and team members.
Not required: a finance or law degree; this role does not replace regulated professional advice.
Illustrative first 90 days after an agreed start
Establish the actual obligations and commitments, then assign owners and resolve priority gaps. By day 90, operate an agreed reporting cycle and any funded onboarding, with a documented escalation process.
These are proposed outcomes, not a promise of resources, launch dates or business results. The funded scope and available collaborators would be agreed before employment.
Compensation: no approved role-specific offer or grant is announced here. See the pay and equity disclosures below. Planned employment: full-time if activated; country eligibility and remote or hybrid arrangements must first be confirmed.
Design engineer
Turn clear learning interactions into production interfaces.
Read the planned role
This is a potential future role, not a currently funded vacancy. Its creation, final remit, employment location, compensation and start date depend on completed financing and an approved hiring decision.
The planned remit
This planned role would bring interaction design and implementation together, initially on the funded consumer journey. You would work with the founder and engineers engaged at the time. Product and release decisions would have explicit owners; the role does not promise unilateral authority over every release.
Proposed responsibilities
- An accessible interaction and visual design system, including usable components.
- Coded prototypes and production implementation for agreed surfaces.
- Empty, loading, error, interrupted and consent states.
- Learner-facing clarity and, when prioritized, App Store creative and prototypes for later teaching formats.
Relevant evidence
- Shipped design and implementation you can explain.
- A specific user problem that changed your design.
- Evidence of accessibility, state coverage and collaboration.
Not required: a design degree or AI experience.
Illustrative first 90 days after an agreed start
Improve one important learning interaction and document its components and states. By day 90, verify the agreed flow with representative users or accessibility checks and establish reusable implementation patterns.
These are proposed outcomes, not a promise of resources, launch dates or business results. The funded scope and available collaborators would be agreed before employment.
Compensation: no approved role-specific offer or grant is announced here. See the pay and equity disclosures below. Planned employment: full-time if activated; country eligibility and remote or hybrid arrangements must first be confirmed.
Growth lead
Find relevant learners and measure useful return.
Read the planned role
This is a potential future role, not a currently funded vacancy. Its creation, final remit, employment location, compensation and start date depend on completed financing and an approved hiring decision.
The planned remit
This planned role would own bounded consumer distribution experiments after the product, audience and budget are approved. No acquisition budget, agency engagement or outside growth team is currently promised by this description. The founder would approve commitments before spending.
Proposed responsibilities
- A defined learner audience, channel hypotheses and proportionate acquisition tests.
- Attribution, activation, return and cost metrics with explicit denominators.
- Creative and store-listing experiments with the people responsible for design and iOS.
- Evidence-based stop, continue and expand decisions; paid campaigns, creators and partnerships only within approved scope.
Relevant evidence
- An attributable growth experiment, including spend and an unsuccessful result.
- Hands-on creative or analytical work.
- Evidence that you distinguish installs, useful engagement and paid demand.
Not required: equal depth on every channel or an education background.
Illustrative first 90 days after an agreed start
Define the initial audience and measurement plan. By day 90, complete a bounded approved experiment, report its result and recommend the next decision; a positive growth result is not guaranteed.
These are proposed outcomes, not a promise of resources, launch dates or business results. The funded scope and available collaborators would be agreed before employment.
Compensation: no approved role-specific offer or grant is announced here. See the pay and equity disclosures below. Planned employment: full-time if activated; country eligibility and remote or hybrid arrangements must first be confirmed.
Learner operations lead
Turn learner problems into verified improvements.
Read the planned role
This is a potential future role, not a currently funded vacancy. Its creation, final remit, employment location, compensation and start date depend on completed financing and an approved hiring decision.
The planned remit
This planned role would own support processes and the issue-to-fix loop for the agreed testing or release audience. Coverage, service levels and any external support would be explicitly funded and agreed. This description does not promise an existing overflow team or round-the-clock staffing.
Proposed responsibilities
- Support triage, clear responses and reliable escalation.
- Content-problem records and verification that important fixes address the reported issue.
- Trust and safety reports and appeals under an approved policy.
- Learner feedback summaries, release checks and payment-related support only when those services are active.
Relevant evidence
- A difficult support or escalation case handled with judgment.
- A recurring issue you traced to a system or product improvement.
- Clear communication and careful handling of personal information.
Not required: a technical degree.
Illustrative first 90 days after an agreed start
Define queues, escalation rules and coverage. By day 90, operate a repeatable process for priority issues and demonstrate verified closure on representative cases.
These are proposed outcomes, not a promise of resources, launch dates or business results. The funded scope and available collaborators would be agreed before employment.
Some trust and safety work can involve distressing content. Any such duties, exposure limits and available support would be discussed before accepting the role; an undefined support program is not being promised.
Compensation: no approved role-specific offer or grant is announced here. See the pay and equity disclosures below. Planned employment: full-time if activated; country eligibility and remote or hybrid arrangements must first be confirmed.
Learning scientist
Measure what learners can recall and apply without help.
Read the planned role
This is a potential future role, not a currently funded vacancy. Its creation, final remit, employment location, compensation and start date depend on completed financing and an approved hiring decision.
The planned remit
This planned role would define learning outcomes and study methods for Merak Lab, our planned learning-research program. We have not established a learning-improvement claim. The remit includes challenging unsupported claims, including claims preferred by the founder.
Proposed responsibilities
- Definitions of learning outcomes and appropriate delayed, unaided tasks.
- Rubrics, expert comparison sets and human-rater calibration.
- Feasible study design, consent, research ethics and interpretation of uncertainty.
- Review of public learning claims; participant recruitment, raters and specialist methods would require approved scope and resources.
Relevant evidence
- A learning study you designed and interpreted, including limitations or null results.
- Deep relevant methods knowledge through research, professional work or equivalent experience.
- An example of translating a measurement problem into a practical product decision.
Not required: AI product experience or a particular university credential.
Illustrative first 90 days after an agreed start
Create an outcome dictionary, initial rubric and feasible pilot protocol. By day 90, establish the agreed calibration method and, if participant and resource conditions are met, a first pilot with an honest analysis. No positive effect or arbitrary agreement threshold is promised.
These are proposed outcomes, not a promise of resources, launch dates or business results. The funded scope and available collaborators would be agreed before employment.
Compensation: no approved role-specific offer or grant is announced here. See the pay and equity disclosures below. Planned employment: full-time if activated; country eligibility and remote or hybrid arrangements must first be confirmed.
Learning engineer
Translate learning principles into testable product behavior.
Read the planned role
This is a potential future role, not a currently funded vacancy. Its creation, final remit, employment location, compensation and start date depend on completed financing and an approved hiring decision.
The planned remit
This planned role would specify practice, feedback and review interactions with the founder and available scientific and engineering specialists. Further personalization remains conditional roadmap work; no preceding hire or curriculum system is assumed to exist.
Proposed responsibilities
- Implementable specifications for practice, examples, feedback and review.
- Learning-event definitions and checks for intended behavior.
- Reusable teaching standards and correction workflows.
- Adaptive practice experiments or subject reviewers when separately prioritized and resourced.
Relevant evidence
- A learning interaction that shipped in software.
- A specification and test that connect a teaching principle to observable behavior.
- Evidence of measurement, revision and collaboration with technical colleagues.
Not required: a PhD or LLM experience.
Illustrative first 90 days after an agreed start
Specify and help implement one bounded practice/feedback interaction. By day 90, verify its behavior and telemetry, and use observed problems to improve the reusable specification.
These are proposed outcomes, not a promise of resources, launch dates or business results. The funded scope and available collaborators would be agreed before employment.
Compensation: no approved role-specific offer or grant is announced here. See the pay and equity disclosures below. Planned employment: full-time if activated; country eligibility and remote or hybrid arrangements must first be confirmed.
Growth engineer, web
Build useful public learning pages and measurable app handoffs.
Read the planned role
This is a potential future role, not a currently funded vacancy. Its creation, final remit, employment location, compensation and start date depend on completed financing and an approved hiring decision.
The planned remit
This planned role would own an agreed web-discovery and conversion scope when funded. Public path pages, web learning and their traffic are not claimed as an already established acquisition engine. No outside growth team or prior platform implementation is guaranteed.
Proposed responsibilities
- Useful public pages built from approved learning content.
- Performance, accessibility, indexing and appropriate search structure.
- Web-to-app handoffs and consistent analytics.
- Predefined experiments and reliable interpretation; a broader web learning product would require a separate funded decision.
Relevant evidence
- A shipped consumer web funnel or discovery surface.
- A measured performance, accessibility or conversion improvement.
- An experiment you would trust even when the result was unfavorable.
Not required: AI or education experience.
Illustrative first 90 days after an agreed start
Agree the measurement contract and one useful page-to-app journey. By day 90, deliver the funded surface, verify its performance and attribution, and report the first approved experiment without promising traffic or conversion gains.
These are proposed outcomes, not a promise of resources, launch dates or business results. The funded scope and available collaborators would be agreed before employment.
Compensation: no approved role-specific offer or grant is announced here. See the pay and equity disclosures below. Planned employment: full-time if activated; country eligibility and remote or hybrid arrangements must first be confirmed.
Other relevant work
If your expertise could help Merak but does not match a role above, you can send a short expression of interest about our mission, a challenge you see ahead and the contribution you would want to make. A CV, portfolio, speculative business plan or new Merak project is not required to begin the conversation. We cannot promise that a role will be created.
We welcome job-relevant knowledge of learners, languages and markets. We do not infer capability, work authorization or suitability from nationality, name, accent or university.
Pay, equity and employment
Pay: there is no approved role-specific offer announced on this page. When a role is activated, we will give the applicable good-faith base salary or hourly range, currency, working hours and employment arrangement before a formal interview, and in the advertisement wherever required. We will not ask for your salary history. An early conversation does not establish pay or an offer.
Equity: we intend to consider equity as part of employee compensation. The employee reserve and historical role allocations are management proposals, not adopted awards or guaranteed percentages. No grant is made by this page. Any equity arrangement requires applicable company approvals, a legally available instrument and individual documentation. Terms would specify the number of shares or options, capitalization basis, vesting, exercise terms and relevant conditions. Future financing can dilute ownership, and equity may have no realizable value.
Location and employment: eligible countries, work authorization requirements, any sponsorship, the employing entity and remote or hybrid arrangements must be confirmed for each activated role. We do not currently promise employment everywhere in North America or Europe, a particular employer-of-record arrangement, benefits package, travel program or relocation support. We would explain applicable benefits, equipment and travel terms before agreement.
Founding is a description of an intended early role. It does not by itself confer founder status, board rights, ownership, equal grants, a guaranteed reporting relationship or a management appointment. Nothing on this page limits rights under applicable law or an agreed contract.
How we assess interest
We begin with one open question about how you understand Merak's mission, the challenge you see in your area of expertise and how you would want to contribute as an early teammate. We are interested in your thinking about the learning app and its future. The founder makes every progression, rejection and hiring decision.
We use AI tools to help summarize recruiting material, identify job-relevant evidence and gaps, compare evidence with the role remit, and prepare questions. These tools can make mistakes. A person checks their output against the original material. We do not infer protected characteristics, analyze emotions, or use automated rejections. You can request a fresh human-only review by emailing erhan@usemerak.com, without disadvantage. Our earlier statement that AI was not used in screening or assessment no longer describes our process and is replaced by this disclosure.
A brief initial reply is enough. Further discussions focus on actual Merak problems, priorities and working together. We do not ask for a speculative plan or unpaid production work. Any substantive collaboration would require an agreed scope and appropriate compensation. Disclosed AI use by candidates is welcome, with an explanation and verification of the result.
We do not request confidential former-employer code, patient or customer data, identity documents, bank details or sensitive personal information at the expression-of-interest stage. References are contacted only with your permission; we will not contact a current employer without explicit consent.
Tell us about accessibility needs or reasonable adjustments at any stage. We can discuss an alternative assessment format. We consider candidates without unlawful discrimination and do not treat prestige, protected traits or a fixed tenure requirement as substitutes for relevant ability.
If we begin a discussion, we will state whether it is exploratory or part of an activated hiring process and agree the next step or status checkpoint. If you interview, you will receive an outcome or a clear notice that the role is on hold.
Recruiting information and your choices
Controller and contact: Merak Intelligence, Inc. determines how recruiting information is used. For privacy questions, corrections, access requests, deletion requests, objections or a human-only review, email erhan@usemerak.com with Recruiting privacy in the subject. You can express interest with a short note about Merak's mission and your potential contribution; a CV is not required to begin the conversation.
Information and purpose: we use the contact and professional information you supply, relevant public work you link, correspondence and assessment notes to evaluate prospective role fit, communicate with you and keep necessary recruiting records. We seek permission before references. We do not use recruiting information for consumer-product marketing or publish candidate records.
Service providers and AI: email, document-storage and AI service providers, including OpenAI tools, may process selected recruiting material. We limit assessment material to what is relevant to the role. Do not send confidential or sensitive third-party information. The founder and people authorized for the recruiting purpose may access the material; outside advisers or providers receive access only for their relevant service or a legal requirement.
Legal grounds: where applicable data-protection law requires a legal basis, ordinary prospective recruiting relies on our legitimate interest in evaluating potential working relationships, subject to your rights and an assessment of the balance of interests. Steps towards an employment contract may also be taken at your request; mandatory recordkeeping relies on legal obligations. Optional retention for unrelated future opportunities requires a separate choice. Sending an expression of interest is not blanket consent to every use of your data.
Locations and safeguards: the founder operates from Türkiye, and service providers may process information in the United States or other countries. International processing requires the applicable transfer mechanism and safeguards; the fact that you emailed us does not replace those requirements. Contact us for information relevant to your situation. We will provide any additional jurisdiction-specific notice or choices required before the relevant assessment.
Retention: ordinary recruiting records are reviewed for deletion or anonymization 12 months after the later of the last substantive recruiting contact or the relevant recruiting decision. Applicable mandatory recordkeeping, an unresolved claim or a legal hold can require longer retention. A legal exception does not authorize continued talent marketing. We ask separately before retaining your details to contact you about unrelated future roles, for up to 12 months unless renewed. Withdrawal of that permission stops optional future-role use; it does not override required legal records.
Your choices and rights: you may withdraw your expression of interest, correct inaccurate information or request a fresh human-only review. Access, erasure, restriction, objection, portability and complaint rights depend on applicable law; you may contact the relevant data-protection authority. A human-only request does not require an explanation and will not count against you. We may need to retain a limited record to meet a legal obligation or resolve a claim, and will explain that if relevant.
There is no solely automated employment decision in this process. This does not remove any further obligations that may apply to the tools or assessment in your jurisdiction. The general product Privacy Policy does not replace this recruiting notice.
Express interest
Email erhan@usemerak.com with the planned role in the subject and a brief note about how you understand our mission and where your expertise could help. Our first conversation will center on one open question about the learning app and your potential contribution. Please read the current hiring status, pay and equity disclosures, AI-assistance disclosure and recruiting privacy information above before sending material.
Last revised: 4 November 2026. All roles remain funding-dependent as of this revision.